collective / collective.hostout

zc.buildout deployment and remote control
22 stars 7 forks source link

Is this project active? #44

Open agb80 opened 8 years ago

agb80 commented 8 years ago

We are looking for a tool to use in combination with our buildout recipes to deploy our python apps. Is this project active, are there anybody using it? Any links that I would review about user experiences?

djay commented 8 years ago

Yes its active. We just added capability to help deploy via docker. We use this tool both with and without docker for all our deployments. You should use the master branch as there hasn't been a release in awhile.

On Wed, 16 Mar 2016 11:14 pm agb80 notifications@github.com wrote:

We are looking for a tool to use in combination with our buildout recipes to deploy our python apps. Is this project active, are there anybody using it? Any links that I would review about user experiences?

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/collective/collective.hostout/issues/44

agb80 commented 8 years ago

Thanks a lot for your answer @djay, do you have any links that I can refer in order to get some insides on how you use it?

Thanks in advance again!

djay commented 8 years ago

What are you trying to do? What is the problem you are encountering?

On Tue, 22 Mar 2016 5:26 am agb80 notifications@github.com wrote:

Thanks a lot for your answer @djay https://github.com/djay, do you have any links that I can refer in order to get some insides on how you use it?

Thanks in advance again!

— You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub https://github.com/collective/collective.hostout/issues/44#issuecomment-199516228

agb80 commented 8 years ago

Honestly, I do't have done any test jet, I'm on a research phase trying to evaluate available tools and reduce to a short list of two or three for testing.

This is how I think my deployments must look like:

  1. Schedule deployment as we need to defer it to a time where no one is using the service, midnight for example.
  2. Stop the service. Supervisor installed on buildout folder.
  3. Make a backup of databases.
  4. Update buildout recipe from remote repository
  5. Run buildout to reflect changes done on recipe.
  6. Clone each of databases and apply schema upgrades
  7. Drop old databases and rename new ones to old names
  8. If anything goes wrong between 5 and 7 get back to original state and send a mail with error.
  9. Restart service

Could you please assist me to know if that is possible to accomplish with houstout? I'm specially interested on the rollback feature as would like to use an existing task instead of create my own.