Skip to content

Deployment strategy #33

@dirn

Description

@dirn

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?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions