Skip to content
This repository has been archived by the owner on Dec 27, 2021. It is now read-only.

Bundles #57

Open
heynemann opened this issue Sep 15, 2012 · 4 comments
Open

Bundles #57

heynemann opened this issue Sep 15, 2012 · 4 comments
Milestone

Comments

@heynemann
Copy link
Contributor

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).

@diogobaeder
Copy link
Contributor

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.

@diogobaeder
Copy link
Contributor

Do you still want to ship this in 0.6.0? I'm asking because I think this will take some time to design and build an initial set of bundles, and we already have some critical features ready to be released which I'd like to release soon. (Specially the security roles.)

So I'd suggest we postpone this for 0.7.0, but if you really want it for 0.6.0 I can focus on it before releasing our next version.

What do you think?

@heynemann
Copy link
Contributor Author

Go ahead ;) Postpone it.

Bernardo Heynemann
Developer @ globo.com

On Sun, Jan 13, 2013 at 4:21 AM, Diogo Baeder notifications@github.comwrote:

Do you still want to ship this in 0.6.0? I'm asking because I think this
will take some time to design and build an initial set of bundles, and we
already have some critical features ready to be released which I'd like to
release soon. (Specially the security roles.)

So I'd suggest we postpone this for 0.7.0, but if you really want it for
0.6.0 I can focus on it before releasing our next version.

What do you think?


Reply to this email directly or view it on GitHubhttps://github.com/heynemann/provy/issues/57#issuecomment-12190179.

@diogobaeder
Copy link
Contributor

Nice. I'll do a few more fixes, then, before launching - our API docs are a bit out-of-date and some parts are incorrect -, maybe wait for Fernando do release PostgreSQLRole for CentOS (I don't know how close he is to have something working, yet) and release 0.6.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants