Gitee repository migration to intranet: synchronizing code, permissions, and how to build after network disconnection
This article explains how to migrate a Gitee repository into the intranet AngusGit and continue building after disconnecting from the external network. After reading this, you can choose to import or git clone --bare and then push based on whether the repository is public or private. Go to Settings → Access and reauthorize with read-only, read-write, or administrator permissions. Prepare the runner image, build image, and dependency proxy in the intranet. First, log in to AngusGit. The following push uses SSH. If you don't have ~/.ssh/id_ed25519.pub on your local machine, run ssh-keygen -t ed25519 -C "you@example.com". Press Enter directly for the path. Copy the line starting with ssh-ed25519 from cat ~/.ssh/id_ed25519.pub and register it to My → SSH Key, then click Add Key. The address is in the format ssh://git@host:2222/owner/repository.git, and the username is git. If you switch to HTTPS, go to My → Access Token, click Generate New Token, and follow the password verification…
The article provides a guide on how to migrate a Gitee repository to AngusGit, a Git repository management platform, and continue building after disconnecting from the internet. It outlines a three-step process: synchronizing code, allocating permissions, and building without internet access. The guide explains how to import or clone and push repositories, set permissions, and prepare runner images, build images, and dependency agents for offline building. It also addresses common issues that may arise during the migration process.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
