Deploy from a GitHub repository

App Space can build a container from a repository on GitHub. It reads the Dockerfile in the repository, builds the image, and runs it.

What the repository needs

• It is on GitHub and public. Private repositories are not supported yet.
• It has a Dockerfile at its root. App Space does not guess how to build your code: the Dockerfile says it.
• The program listens on a port, and you know which one. You need it to publish the container.

No repository at hand? Fork the Node.js sample. It listens on port 3000.

Add it

1. Open your App Space and select Add container.

2. Select Git Repository.

3. Paste the repository address, followed by # and the branch or tag to build:

   https://github.com/your-name/your-repo.git#main

   The dialog checks four things and shows each result: the address format, the branch or tag, that the repository is public, and that it has a Dockerfile at its root.

4. Keep the suggested Container Name or type your own, then select Add Container.

The other containers restart

To build the new container, App Space stops and starts the whole App Space. Containers that were running are down while the new one is built and started: about half a minute with the small sample, longer for a bigger build. Add a repository container at a moment when that is acceptable.

When the App Space shows all its containers running again, your code is built and running. With the sample repository that took under a minute.

Publish it

The container is not public until you expose its port. Select it, open Ports, select Expose port, and type the port your program listens on (3000 for the sample). See Deploy your first app.

If the container does not stay up

A program that exits right after it starts is shown as a container that keeps crashing. Select the container and open Logs: what the program printed before it stopped is there.