Next steps

[ehmatthes]

There's currently a Djangonaut Space cohort focusing on django-simple-deploy, which has brought some focus back to this plugin. It's really helpful to have a small group of people to build consensus with around the many questions that need to be answered when implementing a vps-based plugin. #27 cleans up the bad behavior of modifying the user's sshconfig file. There are some next steps that will bring this plugin to a state where others can start to meaningfully contribute:

• Make sure username/ password workflow is not broken by changes made to support ssh-based workflow.
• Finish writing e2e test.
• Refactoring first-pass. This is a bloated mess of repetitive, exploratory code. Clean up all the obvious things, including removing commented out code.
• Document handling of ssh keys, and the overall process in general.
• Audit handling of ssh keys. This is where additional, experienced eyes are really helpful.
• Update --platform -> --vps-host. A new contributor can do this.
• Isolate host-specific code.
• Define boundaries around --automate-all and configuration-only workflows.
• Make a roadmap. Does a docker based workflow belong in this plugin, or in a separate one? SQLite support? Support multiple deployments?