We have created the basic content for our website and adapted several templates to match the Clean Blog theme. The final step to the "Basic" part is to push these changes to your test environment and ultimately deploy a live instance.
Go back to the Divio App and click on the "Upload code" button.
A prompt opens where you have to define your "Commit message" to upload your work to the Divio Cloud. Add a meaningful message and press "Commit":
This will add the commit to your local Git and pushes it to the test server. You can check the status by going to your project on Divio Cloud and inspecting the "Test Server" column on the "Dashboard". A message should appear, informing you that you have one or more undeployed commits (it could be several):
Next go back to the Divio App and click on the arrow pointing down right of the "Upload code" button and choose "Upload media":
A message will appear informing you about the process:
The upload might take some time, the status will be shown on the upper right of the Divio App:
Do the same procedure for "Database Upload".
Once the deployment has finished, inspect your site to verify that everything is in order. You can do this by hitting the "Open site" link for the Test Server.
Next click on the arrow pointing down right of the "Deploy" button on the "Live Server" and choose "Copy Data from Test and Deploy":
This will ensure that your live server is set up with the initial data provided from the test server. You can later do this again to copy data from test to live or vice-versa. But be warned, this will override the entire database and media files for the target destination.
You can change your subscription on the Subscription menu on the left. Press on the "Edit" button and you'd be able to change the region, RAM, instances, disk space, transfer volume and much more.
Further information is available on our pricing website.
Hit "Deploy" on the live server and wait for the deployment to finish. The initial deployment might take some time as everything has to be set up anew. Subsequent deployments will be faster again.
You now have a live server setup that can be visited by your future customer.