As a developer I can add container-hosting to an *existing* repo

[chrisjsimpson]

Is your feature request related to a problem? Please describe.

Some people start with the end in mind (production) others start without the end in mind (code first, address deployment later). This creates at least two starting points:

• Those that start without a repo, use container hosting from the begining. This is easy, we control state of the world ✔️
• Those that star with an existing existing repo with existing code. This is more tricky but nothing is insurmountable (optimism required)
  • See also Explore: As a developer I can use django-simple-deploy to deploy an *existing* django app #27

Describe the solution you'd like

As a developer I can add container-hosting to an existing repo

Describe alternatives you've considered

Additional context

This has potentially more paths to collide with existing repo data since, by definition repos will not be blank from the start.

• Explore: As a developer I can use django-simple-deploy to deploy an *existing* django app #27
• There are (many) framework specific attempts to do this such as Clarify platform host use case django-simple-deploy/django-simple-deploy#144