Skip to content

Deployment strategy #33

dirn opened this Issue Feb 17, 2014 · 0 comments

1 participant

NYC Python member
dirn commented Feb 17, 2014

We need a deployment strategy. Using SSH to connect to the server and pulling down the changes by hand will be less than ideal.

The current options I can think of are:

  • Manual SSH
  • Fabric SSH
  • Manual Chef/Puppet/Salt/Ansible
  • Fabric Chef/Puppet/Salt/Ansible

To make things a bit more interesting, we could introduce Jenkins as the CI server. If we decide to do this, should Jenkins also serve as a CD server?

@dirn dirn added the deployment label Feb 17, 2014
@dirn dirn referenced this issue Feb 17, 2014

Meetup API key #9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.