Deployment about huginn HOT 7 CLOSED

Or making a deployments directory with different configurations?

On Thu, Mar 28, 2013 at 4:22 PM, Bob Whitney [email protected]:

What do you think about removing the deployment-specific files and
configuration from master?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/28
.

from huginn.

Maybe... I feel like everyone should just manage their own deployment configuration though, and then we don't have to spend time maintaining that stuff. Less code = less headaches for you. Anyone could have a deploy branch that only dealt with deployment, and then just always rebase master to keep it up to date?

from huginn.

Perhaps. My only thought is that I want Huginn to be very easy to deploy, so having a directory full of ready-to-go deployment examples to choose from might help adoption. Something like

/deployment-examples
  /heroku
    README.md
    ...
  /open-stack
  /unicorn

What do you guys think?

We should definitely standardize on the .env setup for customization.

from huginn.

Yeah I agree with that... but I see ease of deployment as a matter of de-coupling the application from any deployment implementation. Maintaining a bunch of deployment scripts seems like opening pandora's box to me.

from huginn.

Then maybe we document different deployment strategies in the wiki and just try to keep the app very flexible and decoupled? Thanks for helping think this through, I appreciate your involvement!

from huginn.

Hey @robertjwhitney, please see #35 and let me know if it looks good.

from huginn.

@cantino 👍

from huginn.