Docs / GitRelax

GitRelax: the platform’s own Git, a project without GitHub

GitRelax is the platform’s own Git: the project repository lives on git.relaxdev.ru. Create a project with the “GitRelax” tab, upload an archive or a folder or run git push — the site is built and deployed. No GitHub, tokens or webhooks needed.

Below: creating a project, code from an archive, your Git login and password, moving code from GitHub, team access and working over MCP.

Contents

How it works

  • A private team repository is created together with the project: https://git.relaxdev.ru/team/project.git, branch main.
  • While the repository is empty, the project waits for the first push — the card on the project page shows the commands.
  • Every push to main starts a build with the same builder as projects from GitHub: your own Dockerfile or any stack the platform supports.
  • Team owners and editors can write to the repository. Everyone has their own Git login and password.

Create a project

  1. 1

    “New Project” → the “GitRelax” tab

    No GitHub repository list needed — you see a short description of GitRelax and an “Upload code” field instead.
  2. 2

    Name and stack

    The name uses Latin letters, digits and hyphens and starts with a letter. The stack works as usual: Docker for your own Dockerfile or a ready-made builder (Next.js, Vite, Node.js, Python and others).
  3. 3

    Create

    The platform sets up the project and the repository. If you attached an archive or a folder, the code lands as one commit and the build starts right away; otherwise after the first push.

Push your code

The project page has a “GitRelax” card. Click “Get Git login and password”: a login like u… and a password are shown once — save the password. Then, in your code folder:

bash
git init -b main
git remote add relaxdev https://git.relaxdev.ru/my-team/my-site.git
git add . && git commit -m "first"
git push -u relaxdev main

Git asks for a login and password — use the ones from the card. After that, a plain git push is enough.

To avoid typing the password every time

Turn on the Git credential store: git config --global credential.helper store (or your system’s password manager). A new password from the card replaces the old one.

Code from an archive or a folder

No git or terminal: attach an archive or a folder on the “GitRelax” tab of “New Project”; an existing project has an “Upload archive/folder” button in the GitRelax card and in the code studio. Drag and drop works too.

  • Formats: zip, tar, tar.gz / tgz, a folder or a set of files. For 7z and RAR, re-save as zip.
  • Up to 150 MB (up to 100 MB unpacked) and 5000 files; the common top folder of an archive is stripped. node_modules, .git, .next and files over 20 MB are skipped.
  • .env is not committed: new variables from it are added to the project variables.
  • Everything lands as one “Import: …” commit: files are added and overwritten, nothing is deleted. Autodeploy starts the build.
  • A project created from an archive runs on the isolated server — safer for unknown code.

Code studio

The “Open code studio” button on the project page opens an editor right in the dashboard: the branch file tree, syntax highlighting, new files and deletion. No git or terminal needed.

  • “Save” or Ctrl+S — all changes as one commit to main; the build starts by itself. You can describe the change next to the button.
  • If a file was changed with git push or the web UI while you had it open, the studio won’t overwrite that change: it offers to take the repository version or write yours on top.
  • Binary files (images, archives) and files over 1 MB aren’t edited in the studio — change them with git push.
  • Team viewers get the studio in read-only mode.

Moving from GitHub and back

Into GitRelax in one click. On the “GitRelax” tab of “New Project”, choose “Move a repository”: the repositories of the GitHub, GitLab, GitVerse or GitFlic account connected in your profile — or a link to any https Git (with a token for a private one). An existing project from GitHub and others has a “Move to GitRelax” button in the source settings: the project starts building from GitRelax and autodeploy from the old repository stops. All branches and history are copied; the source repository stays as is.

From GitRelax to any Git. The GitRelax card has “Send to another Git”: a new private repository named after the project is created in a connected account and the code goes there; or give the URL of an empty repository and a token. “Keep in sync” leaves a mirror — every GitRelax commit goes there too; without it the code is sent once. The token is kept only in the Git mirror, not in the dashboard.

You can also do it by hand — the whole commit history comes along. In the folder with your existing repository:

bash
git remote add relaxdev https://git.relaxdev.ru/my-team/my-site.git
git push -u relaxdev main

The origin remote on GitHub stays — you can push to both. Only a push to relaxdev starts a build on the platform.

Autodeploy

EventWhat happens
push to mainThe new commit is built and deployed
push to another branchThe code is stored, no build
tag, branch deletionNothing
autodeploy turned offThe code is stored; build it with the “Redeploy” button

The deployment history shows the commit, its message and who started the build.

Team access

  • Team owners and editors can write to all of the team’s repositories; viewers get no access to the code.
  • Every team member has their own Git login and password, issued on the page of any team project.
  • Lower someone’s role or remove them from the team, and their access to the code is closed right away.

Web UI

The “Files in the web UI” link on the project page opens the repository on git.relaxdev.ru: files, commit history, branches. Sign in with the same Git login and password. Editing a file in the browser is a commit too, and it starts a build the same way.

AI agents and MCP

The platform’s MCP server works with its own Git end to end — the agent needs neither GitHub nor git in a terminal:

  • create_project with own_git: true — a project with a new repository; with git_import_url — a repository moved from another Git, with archive_base64 — code from an archive;
  • list_files, read_file — files in the project branch;
  • write_files — changes as a single commit, the build starts by itself; then get_deployment and get_build_logs.

Connecting MCP is covered in the AI agents section.

FAQ

Git asks for a password and I don’t remember it+

The password is not stored and is shown only once. On the project page, click “New Git password” — the old one stops working and the new one appears on screen.

The push went through, but no build started+

Only a push to the project branch (main) with autodeploy turned on starts a build. Pushes to other branches and tags are stored in the repository but not built. Check the branch with git branch and the autodeploy setting of the project.

Can I connect GitHub to an own Git project as well?+

A project has one source. If you need GitHub, create a project from a GitHub repository; you can send the code from your own Git there with a regular git push.

Where is the code stored?+

On the platform’s servers, in your team’s private repository on git.relaxdev.ru. A backup is made every night.

How do I take my code with me?+

Run git clone with the URL from the project page and your Git login and password. You get all the code with the full commit history.