Explain how to deploy an already existing application

[ipeychev]

We have to add to the docs information about how to deploy an already existing application.

At the moment, when reading the documentation about the hosting service, the developer gets the impression that the recommended (or the only) way of deploying the app is to fork a boilerplate and commit its content to WeDeploy's Git server.

Although this is a valid scenario, in many cases this would be an extra step, which the developers would prefer to avoid. In most of the cases the developer works on his project and at some point he decides to deploy it. The recommended way of forking a boilerplate gives the impression to the developer that he should have two repositories - one where he develops and another one (the forked boilerplate) where he has to put the content which will be deployed.

Obviously this is an incorrect assumption and that's why project.json and container.json exist. They are documented here, but there is no relation between them and the documentation of the services, so the developer cannot figure out how to use project.json and container.json in his own project.

Apart from adding a relation between these and the documentation of the different services, it would be good to have a separate section in the docs, where we take an existing project and explain how to add to it the different services. From these e can create videos on YouTube and embed them to the docs.

[zenorocha]

Documentation has moved to a new repository (https://github.com/wedeploy/wedeploy.com), if this issue is still valid would you mind moving it over there? Thanks!