Long-term Platform.sh support tasks

[ehmatthes]

This is a supplement to #89, which I'm hoping to close in the current scope of work. This issue will be lower priority, and will likely be open for a longer time.

[ehmatthes]

Tasks

• [ ] Set a more specific ALLOWED_HOSTS entry; currently using '*'.
• [ ] Consider breaking requirements into requirements.txt and requirements_remote.txt.
  • For now I'll use existing approach to adding requirements, but this approach makes more sense for any platform that supports it.
• [ ] Build support for the nested version of startproject.
  • [ ] Target deployment of the polls project!
• [ ] Rich would make this output so much more meaningful to most people.
• [ ] Write up a blog post using dsd and platform.sh to deploy the completed polls project easily.
  • [ ] Consider showing that the deployment process works whether using startproject flat or nested.
• [ ] Requires that user has platformshconfig installed; try to remove local dependence on this package.
  • pip install platformshconfig.
  • This requirement could probably be removed locally. The only thing it's needed for is to determine if settings are being evaluated in the platform.sh environment. This could probably be done with an os.environ check, and then platformshconfig could be imported inside the platform.sh-specific settings block.
  • For now, require it locally to match what their template shows.
  • platformshconfig is_valid_platform() source
• [ ] Support Pipenv.
• [ ] Look at default region in test script. May want to build a CLI arg for --platform_sh-region in the platform create call.

[ehmatthes]

Consolidated to #92.