diogobaeder
commented
12 years ago Wow, this is tasty! I agree, this seems like a very nice way to quickly install an application, indeed. Let's go for it!
Some ideas for it:
- Document this and make it explicit that provy is an opinionated software, so, for example, for the DjangoBundle (as the first case to build a bundle) we provision gunicorn and set it up as well;
- Document the difference between a bundle and a role;
- Have sensible defaults for the bundle settings, but provide the templating capabilities to override them - we can use update_file's options to make this work, and, in the DjangoBundle example, we could have a settings optional parameter that would be a dict with items to replace the default configuration -;
- Make sure we use the bundles through instance methods and not class/static methods, so that we allow the developers to extend from the core provy bundles.
heynemann
What I envision as recipe is like a bundled parametric provyfile.
What I mean is to have higher level bundles that configure a server.
A good example:
DjangoBundle.configure_site( name="my-web-app", git_repo="my.git", workers=10 )
And then my django application is configured. We would find the settings.py file or specify one, like settings_provy.py. Any convention works for me, as long as I can get a django app up and running in minutes, instead of hours.
This ticket is NOT about creating a django bundle, though. It's about creating the infrastructure for bundles. Not sure what that is, so it might be a good idea to just choose one example (django sounds good since it's useful to so many people).