So, I think that your proposal has some merit. However, I think that there are two things that need to be addressed (perhaps as separate bugs):
1) (this bug) Separating paste-deploy stuff from the regular configuration option files
2) Making it easier for newbies to understand the different ways to set up filters and middleware
I think fixing #1 would be a good first step. For the second, I could see using your solution here (using configuration option to driver the picking of a deployment pipeline), or instead having multiple well-commented paste.ini files in /etc that showed examples of configuring the pipelines for different needs.
Hi Eoghan!
So, I think that your proposal has some merit. However, I think that there are two things that need to be addressed (perhaps as separate bugs):
1) (this bug) Separating paste-deploy stuff from the regular configuration option files
2) Making it easier for newbies to understand the different ways to set up filters and middleware
I think fixing #1 would be a good first step. For the second, I could see using your solution here (using configuration option to driver the picking of a deployment pipeline), or instead having multiple well-commented paste.ini files in /etc that showed examples of configuring the pipelines for different needs.
For instance, etc/paste/ could contain:
etc/paste/ glance- api-minimal- paste.ini glance- api-auth- no-cache- paste.ini glance- api-auth- cache-paste. ini
etc/paste/
etc/paste/
Each showing examples of how to configure the filter and middleware pipelines?
-jay