003 - What's new

Published: 2026-09-17

Four weeks of change: git over SSH, passkeys, profile visibility, a light theme and a rebuilt documentation site - plus the platform work that brings the first production instance closer.

New beta server: beta3.git.eu

Beta testing moves to beta3.git.eu.

Create a new account there - nothing carries over from the previous beta server.
It is still a crash-test server: never put production data on it. Just try everything and give us your honest feedback.

Create your beta3 account

One platform, several instances

Git.eu will not be one server.

What this is going to be in the future:

Part	Address	What it is
Main public server	`git.eu`	The public front door: account registration, sign-in
Docs	`docs.git.eu`	The documentation platform
Country instance	`fr.git.eu`	Where your repositories live and your `git` commands go, first production instance, in France - coming next probably Warsaw

What beta3 look like:

Part	Address	What it is
Main public server	`beta3.git.eu`	The public front door
Instance	`fr.beta3.git.eu`	Where your account and repositories live

One account for the whole platform. Your account name and email are reserved platform-wide, not per server. Sign in from git.eu and it takes you to the instance that holds your account.
Instances host repositories. Each instance owns its repositories and serves its own web interface and git access.
First country instances come next. The first production instance is France (fr.git.eu). More country instances follow, on the same account system.

Git over SSH

Clone, pull and push over SSH with your own key pair - no token in the URL, nothing typed on each call.

Add your public key once in Settings → SSH Keys. Give it a device name, so you can revoke a single lost machine without touching the others.
Ed25519 (recommended) or RSA of 2048 bits and above. ECDSA, DSA and smaller RSA keys are rejected.
Works with the git client you already have - no extra helper to install.

git clone git@fr.beta3.git.eu:<USERNAME>/<REPO_NAME>.git

Full walkthrough, including key generation and troubleshooting: Access over SSH

Passkeys, and one page for all your security settings

Passkeys (WebAuthn) join the existing second factors: sign in with your fingerprint, face or device PIN, or use a passkey as a second factor after your password.
One security page for every method - authenticator app (TOTP), passkey, email code and recovery codes. Enable, review and disable each one separately.
Second factor on sensitive changes. Password, email and username changes ask for a second factor when you have one enabled.
Email alerts on security events, so a change you did not make does not go unnoticed.

Guide: Account Security

Profile visibility

You now choose what your profile shows to others:

Public - everything, as before.
Anonymous - your public repositories stay listed, your name and join date are hidden.
Private - your profile looks like it does not exist.

Set it in Settings → Profile → Profile Visibility.

Guide: Account Settings

A light theme and a refreshed interface

Light and dark themes, switchable from the header.
Tables, statistics, cards, status messages and breadcrumbs now use one shared component set, so every page behaves the same way.

Documentation rebuilt

The docs site is reorganised around what you want to do: get started, then guides, then news.

New guides: Access over SSH,

Clone and push over HTTPS, Git client setup, Account settings.

A rewritten quick start.
Copy button on every code block.
Long guides fold into sections and open as you need them.

Progress in brief

✅ git over SSH - clone, pull, push with a key pair
✅ Passkeys and a unified security page
✅ Profile visibility - public, anonymous, private
✅ Light theme and refreshed components
✅ Documentation rebuilt around guides
🔧 In progress: first production instance, Paris (fr.git.eu)
🗺️ Next: support with ticket system, board, issues, organisations, pull requests

Where we stand

git.eu is in beta • not production-ready yet. beta3.git.eu is a crash-test server: push, break, experiment - but keep production data elsewhere.

Under the hood this period was mostly plumbing. The platform was split into a main server plus instances, account names and emails became unique across the whole platform, a repository now accepts only one push at a time so concurrent pushes cannot corrupt it, and the deployment chain was rebuilt and re-verified on clean hosts more than twenty times. Nothing to see on screen - it is what the country instances will run on.

Previous news: 002 - What's new