From git push to a running app: what happens in a REM CloudHub deploy
A walk through one deploy: how the build is chosen, what the new release starts with, and where to look when something fails.
1 min readREM CloudHub team
deploysguides
When you connect a repository to REM CloudHub and pick a branch, every push to that branch starts a deploy. This post follows one deploy from start to finish.
1. The build
The repository's Dockerfile, or the project type you picked when you created the project, decides how the
image is built. The build log streams to the project page while it runs, step by step.
2. The release
The new image starts behind the project's address. The address stays the same from one deploy to the next, so links and DNS records never change.
3. Environment and resources
Environment values and secrets are injected when the container starts. If the project has a database or a cache, its connection details are already in the environment, under the names shown on the Resources page.
4. When something fails
- Build failed: the build log shows the step and the last lines of output.
- Started, then stopped: the runtime log of the new release says why.
- Running, but wrong: deploy the previous commit from the project page while you fix it.
That is the whole path. The docs cover each step in more detail.
Was this useful?