Getting started

This tutorial takes you from a brand-new account to a live deployment on SdV Cloud. You’ll create an organization, a project, and a service container connected to a GitLab repository, then trigger and follow your first deployment.

It assumes you already have an SdV Cloud account and are signed in.

Create an organization

Every resource on SdV Cloud belongs to an organization. If your account isn’t a member of one yet, you’re prompted to create one the first time you sign in.

1. On the Create a new organization screen, enter an Organization name.
2. Click Create organization.

You land on the Projects page for your new organization.

Create a project

Projects group the service containers you deploy together.

1. Click Create Project.
2. Enter a Project name.
3. Optionally, describe the project under Project description.
4. Click Create Project.

Create a service container

A service container is what actually gets deployed. Right now, every service container is built from a GitLab repository — connecting GitHub or deploying a plain Docker image isn’t supported yet.

1. Open your new project and click New Service.
2. Under Select a Git Provider, choose GitLab.
3. If you haven’t connected GitLab yet, click Connect to GitLab and authorize SdV Cloud on the GitLab OAuth screen. You’re redirected back to this form once authorized.
4. Under Select a Repository, pick the repository you want to deploy. The Service Name field is pre-filled from the repository name — edit it if you want a different name.
5. Under Select Service Type, choose HTTP Service. Worker and scheduled job services aren’t available yet.
6. Click Create Service.

See Connect a GitLab repository to a project for more detail on this step.

Configure your service

Creating a service container drops you into a setup wizard — Deployment, Resources, Environment, Storage, Autoscaling, Hibernation, Security, and Review — that walks through everything needed before it can be deployed. The defaults work for a first deployment; only the deployment branch is required.

1. On the Deployment step, pick the branch to deploy under Select the branch you want to deploy from. Leave Choose how your application is built set to Dockerfile — Buildpacks aren’t available yet — and make sure your repository has a Dockerfile at the root, or set its path and the port your app listens on under Advanced options.
2. Click Next through Resources, Environment, Storage, Autoscaling, Hibernation, and Security, accepting the defaults.
3. On the Review step, check the summary of your configuration.
4. Click Deploy Service.

Note

Deploy Service takes you to the service overview — it doesn’t trigger a deployment by itself. You still need to start the first deployment from there, in the next step.

Trigger and follow your first deployment

1. From the service overview, click Deploy.
2. Confirm the branch shown in the dialog and click Deploy again.
3. A Deployment in progress banner appears — click it to open the deployment, where each stage (build, deploy) streams its logs live as it runs.

Once the deployment reaches Success, your service is live at the URL shown on its overview page.

See Read and follow deployment and service logs for more on following build/deploy logs and streaming live service logs.

Next steps

• Scale a service — configure autoscaling and resource allocation.
• Set up two-factor authentication
• Invite members to an organization
• Use the MCP server from a client