Deploy your first project
Connect your git host, run the five-step New project wizard and follow the build log until your code answers at its own address.
A project is one git repository and branch that REM CloudHub builds and runs for you. You never write a Dockerfile unless you want to: the project type says how the code is built and run.
1. Connect your git host
Click Connect git on Home (or open Connectors and its git sign-in). The Git panel opens: "Sign in to your git host so projects can use your repositories. We clone with your own account, never someone else's."
Under Sign in, click the button next to GitHub, GitLab or Bitbucket. You approve REM CloudHub at your git host and come back connected; the connection shows under Your connections. A host marked "Not set up by a Super Admin yet." cannot be used for sign-in on this platform: use a token instead.
If you prefer a token: under Personal tokens pick the Host, paste a Personal access token with read access to your repositories (for Bitbucket also your Bitbucket username, not your e-mail) and click Save token. The token is checked with your git host before it is saved, kept in the Vault, and used only for your own clones.
2. Run the New project wizard
Click New project (Projects page, Home or the Create menu). The wizard has five steps; nothing is created until the last one.
Step | What to do |
|---|---|
Repository | Pick a repository from your connected Git account, or paste its URL. Add a token opens the token form if the repository is private and not connected yet. |
Branch | Pick the branch, or type its name. This branch is built now and on every new commit you deploy. |
Name, type and size | Project name: letters, numbers and dashes. It becomes the address: the field shows "Its address ends in /your-name". Pick the Type and the Size. |
Environment and secrets (optional) | Settings your code reads at start, as name and value rows. Values you mark as secret go to the Vault and are never shown again. |
Review | A plain summary: repository, branch, type and size, environment. Click Create and deploy. |
Project types
Type | For |
|---|---|
R Shiny Web Application | Interactive R dashboards built with Shiny |
R Plumber API | HTTP APIs written in R with plumber |
Python Fast API | Python APIs served by FastAPI |
Python Flask API | Python APIs served by Flask |
React App | Static React single-page apps |
Vue+Quasar App | Vue apps built with Quasar |
Next.js App | Next.js apps, served under their base path |
Full-Stack App (Monorepo) | A frontend plus an API from one repository, configured by a |
MCP Server | Your own MCP server, run as a project |
Custom App with Dockerfile | Builds your repository's own Dockerfile; use it only when no other type fits |
The list you see is the one your platform has switched on.
Sizes
Sizes go from Extra small to Extra large; Medium is the default. A size is the CPU and memory cap of the running container. If your organisation decides sizes for you, the choice is fixed and the wizard says so.
3. Follow the first build
After Create and deploy a message says "your-project is building" and the deployment page opens. It shows:
Build steps: clone, build, provision, start, each ticking as it finishes;
Build log: every line, live;
Source: the commit hash and the image tag.
When the status turns running, the project answers at remcloudhub.com/your-project (or the address your organisation's domain gives it). Open it from the project's page.
4. What REM CloudHub did for you
Built an image (or reused an identical earlier one: same commit, dependencies and base image means no rebuild).
Attached what the code needs: before it starts, REM CloudHub reads the code and binds the secrets, database and storage it asks for. You can see and change this on the project's Settings > Resources.
Started the container with a router rule for its address, and kept the build as a version you can roll back to.
Next: Invite your team, or learn the project page in Projects.