Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deployment strategy #33

Open
dirn opened this issue Feb 17, 2014 · 0 comments
Open

Deployment strategy #33

dirn opened this issue Feb 17, 2014 · 0 comments
Labels
deployment

Comments

@dirn
Copy link
Contributor

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deployment
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dirn