Last updated 11th May 2021
Moving an already-built site to Web PaaS is generally straightforward. For the most part, the only part that will vary from one framework to another is the details of the Web PaaS configuration files.
First, assemble your Git repository as appropriate, on your master branch. Be sure to include the Web PaaS configuration files, as you will not be able to push the repository to Web PaaS otherwise!
For some applications, such as Drupal you will need to dump configuration to files before proceeding. You will also need to provide appropriate configuration to read the credentials for your services at runtime and integrate them into your application's configuration. The details of that integration will vary between systems. Be sure to see the appropriate project templates for our recommended configuration.
In the management console, click
+ Add project to create a new Web PaaS project. When asked to select a template pick "Create a blank project".
Push your code
When creating a new project, the management console will provide two commands to copy and paste similar to the following:
git remote add webpaas email@example.com:nodzrdripcyh6.git git push -u webpaas master
The first will add a Git remote for the Web PaaS repository named
webpaas. The name is significant as the Web PaaS CLI will look for either
origin to be the Web PaaS repository, and some commands may not function correctly otherwise. The second will push your repository's master branch to the Web PaaS master branch. Note that a project must always start with a master branch, or deploys to any other environment will fail.
When you push, a new environment will be created using your code and the provided configuration files. The system will flag any errors with the configuration if it can. If so, correct the error and try again.
Import your database
You will need to have a dump or backup of the database you wish to start from. The process is essentially the same for each type of persistent data service. See the MySQL, PostgreSQL documentation as appropriate.
Import your files
Content files (that is, files that are not intended as part of your code base so are not in Git) can be uploaded to your mounts using the Web PaaS CLI or by using
rsync. You will need to upload each directory's files separately. Suppose for instance you have the following file mounts defined:
mounts: 'web/uploads': source: local source_path: uploads 'private': source: local source_path: private
While using the CLI and rsync are the most common solutions for uploading files to mounts, you can also use SCP.
Web PaaS CLI
The easiest way to import files to your project mounts is by using the Web PaaS CLI
mount:upload command. To upload to each of directories above, we can use the following commands.
webpaas mount:upload --mount web/uploads --source ./uploads webpaas mount:upload --mount private --source ./private
You can also use
rsync to upload each directory. The
webpaas ssh --pipe command will return the SSH URL for the current environment as an inline string that
rsync can recognize. To use a non-default environment, use the
-e switch after
--pipe. Note that the trailing slash on the remote path means
rsync will copy just the files inside the specified directory, not the directory itself.
rsync -az ./private `webpaas ssh --pipe`:/app/private/ rsync -az ./web/uploads `webpaas ssh --pipe`:/app/web/uploads
If you're running
rsync on MacOS, you should add
--iconv=utf-8-mac,utf-8 to your
rsync documentation for more details on how to adjust the upload process.
Did you find this guide useful?
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.