iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Store Gitea repositories on another disk, mount, NAS share, or Docker volume by setting [repository] ROOT in app.ini to an absolute path, then placing repositories beneath that path in Gitea’s required layout: <REPO_ROOT>/<user>/<repo>.git. With Docker, mount the host storage into the container first and use the container-visible path in ROOT. Stop or quiesce Gitea, preserve ownership and executable permissions, copy the data, and test browsing, cloning, pushing, hooks, and Git LFS before deleting the original.
This guide explains the path rules, what data may need to move, procedures for installed and containerized deployments, NAS caveats, verification, and rollback.
How Gitea chooses the repository directory
Gitea reads the repository location from the [repository] section of app.ini. The setting is named ROOT and is the root path for all repository data.
Use an absolute path for a separate volume
An absolute value such as /srv/gitea-repositories points directly to the mounted filesystem. It does not depend on Gitea’s application work directory. This is the safest form when the target is a separately mounted block device, a host directory passed into a container, or a NAS mount.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
If ROOT is relative, Gitea resolves it below AppWorkPath. The effective default is beneath APP_DATA_PATH, so a relative value can continue using the original volume even when you believe storage has moved.
Keep Gitea’s repository hierarchy
Gitea expects each bare repository at:
<REPO_ROOT>/<user>/<repo>.gitFor example, a repository owned by the account alice and named website belongs at /srv/gitea-repositories/alice/website.git. Do not flatten the directories, rename the .git suffix, or copy only selected files from inside a repository. The hierarchy lets Gitea associate the on-disk repository with its application record.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteROOT value |
How Gitea resolves it | Use when relocating storage |
|---|---|---|
/srv/gitea-repositories |
Uses that exact directory | Recommended for a mounted volume or container mount |
repositories |
Resolves below AppWorkPath |
Suitable only when the work path itself is intentionally on the target volume |
| Omitted or defaulted | Uses the configured application-data layout | Not sufficient by itself to move repositories to another filesystem |
Decide what should move with the repositories
Changing repository.ROOT moves the Git repositories, not every file Gitea may write. Inventory each dataset before choosing the size and backup plan for the new volume.
| Dataset | Typical configuration or location | Move decision |
|---|---|---|
| Git repositories | [repository] ROOT |
Must be copied to the new root in the user/repository hierarchy |
| Git LFS objects | The official Docker template uses /data/git/lfs for local LFS storage |
Move or remount it separately if LFS objects should leave the original volume |
| Application data | APP_DATA_PATH |
May contain other runtime data; changing repository storage does not relocate it |
| Database | Configured independently of repository.ROOT |
Keep it where it is or migrate it with a database-specific procedure |
| Search indexer data | Indexer configuration and paths | Assess separately; indexes can have different rebuild and backup characteristics |
| Uploads and attachments | Upload and attachment locations | Move only if those files are part of your storage objective |
A repository migration that omits LFS can appear successful for ordinary Git operations while large-file checkout or download fails later. Include every dataset your users rely on in the capacity calculation and backup schedule.
Compare storage targets before migrating
| Target | Persistence and administration | Permissions and filesystem concerns | Performance and backup factors |
|---|---|---|---|
| Directory on the existing host disk | Simple and persistent; no container remapping is needed for a native install | Uses the host filesystem’s ownership and mount options | Usually the simplest latency profile; use the host’s snapshot or backup tooling |
| Separate block device | Survives application restarts when mounted persistently; requires reliable boot-time mounting | Confirm the mount is present before Gitea starts and that its owner can read and write | Capacity, latency, and snapshots depend on the device and filesystem |
| NAS share | Requires a persistent network mount and network availability before startup | The share must permit executable files because Git hooks and related operations can require execution | Latency, throughput, locking, failover, and snapshot behavior are environment-dependent |
| Docker bind mount | Persists outside the container and survives container recreation when the host path is retained | Container UID/GID must own or be allowed to write the mounted path | Host filesystem and mount options determine performance and backup methods |
| Docker named volume | Managed by Docker and independent of the container lifecycle | Inspect and set ownership inside the volume for the selected image | Backups require exporting or snapshotting the volume; behavior varies by Docker storage driver |
No universal capacity or performance number applies. Repository size, clone patterns, LFS use, network latency, filesystem, and backup design determine the right target.
Prepare a safe migration
Do the preparation while the current instance still works. The goal is to produce a consistent copy and a way back if the new mount or permissions are wrong.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Identify the installation type. Record whether Gitea runs directly on the host, in a rootful Docker image, or in a rootless Docker image. Rootful and rootless image families use different volume mappings and layouts and are not interchangeable.
- Read the active configuration. Locate the instance’s
app.iniand record the current[repository]ROOT,APP_DATA_PATH, LFS path, database settings, upload paths, and attachment paths. Confirm which path actually contains the repositories. - Check the target filesystem. Mount the new disk or share persistently, then verify that it is present after a reboot. For a NAS, confirm the protocol and mount options allow file execution, normal Git file operations, and the locking behavior required by your environment.
- Quiesce Gitea. Stop the service or place it in a maintenance window so no push, repository maintenance task, hook, or LFS transfer changes files while they are being copied.
- Back up before copying. Take a filesystem backup or an application-consistent backup of repositories and the database. Keep the original directory intact until the new location has passed verification.
- Check ownership and free space. Record the current owner and group of repository files, and confirm the target has room for repositories, Git LFS objects, temporary copy overhead, and future growth.
Move repositories on a native Gitea installation
1. Create and mount the destination
For example, create a dedicated directory on a mounted filesystem:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
sudo mkdir -p /srv/gitea-repositories
sudo mount /dev/sdb1 /srv/gitea-repositoriesThe device name and mount command are examples; use the filesystem and persistent mount entry appropriate for your server. Do not start Gitea until the mount is present, or it could write into an empty directory on the boot volume.
2. Copy the complete repository tree
With Gitea stopped, copy the existing root’s contents, preserving hidden files, modes, ownership, timestamps, and links where your backup policy requires them:
sudo rsync -aHAX /old/gitea-repositories/ /srv/gitea-repositories/Replace the source with the directory currently used by Gitea. The trailing slash copies the contents into the destination. Afterward, check that paths such as /srv/gitea-repositories/alice/website.git exist and that repository files were not nested one directory too deep.
Recommended Free Tools
3. Set the repository root
Edit app.ini and set an absolute value:
[repository]
ROOT = /srv/gitea-repositoriesKeep unrelated settings unchanged. If the file has a duplicate [repository] section or duplicate ROOT keys, remove the ambiguity and retain one effective setting.
4. Correct ownership and start Gitea
Assign the destination to the same operating-system account that runs Gitea. For example:
sudo chown -R gitea:gitea /srv/gitea-repositoriesUse your service account’s actual name rather than assuming it is gitea. Start Gitea only after verifying that the mount is active and the service account can create a temporary file, read objects, and execute repository hooks.
5. Keep the old root during verification
Do not rename or delete the old directory immediately. It is your fastest rollback source if Gitea starts with an empty path, users cannot push, or LFS requests fail.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Move repositories with Docker
Docker adds one rule that causes many failed migrations: ROOT must name the path inside the container, not the host path. A host directory such as /srv/gitea-repositories can be mounted at /data/git/repositories; Gitea must then use /data/git/repositories.
1. Stop or quiesce the container
Stop the Gitea container or use an operational maintenance window that prevents writes. Back up the repository data and the database before changing the compose file, run command, or volume attachment.
2. Create a persistent host directory
sudo mkdir -p /srv/gitea/repositories
sudo mkdir -p /srv/gitea/lfsUse separate directories when you want repository data and LFS objects to have independent capacity or backup policies. The official Docker template places repositories at /data/git/repositories and local LFS data at /data/git/lfs inside that image layout.
3. Add the volume mapping
Map the host directory to the path Gitea will see. A bind-mount example is:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →volumes:
- /srv/gitea/repositories:/data/git/repositories
- /srv/gitea/lfs:/data/git/lfsKeep your existing configuration and data mounts as well. The rootless installation documentation shows persistent mounts such as ./data:/var/lib/gitea and ./config:/etc/gitea; the exact paths differ between rootless and rootful images. Select one image family and retain its documented layout rather than combining mappings from both.
4. Match the container’s UID and GID
The mounted directory must be writable by the account used inside the container. The rootless Docker guide uses UID and GID 1000 as its default example and shows:
sudo chown -R 1000:1000 /srv/gitea/repositories /srv/gitea/lfsUse the UID and GID for your selected image, which may differ. If ownership is wrong, the container can report permission errors in its logs, fail to create repositories, or reject pushes even though the host directory appears writable to your shell user.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
5. Copy into the mounted path
Copy the old repository root into the host directory that is mapped to the container path:
sudo rsync -aHAX /old/repositories/ /srv/gitea/repositories/Check the resulting host tree and, if possible, inspect it from a temporary shell in the container. The container-visible result must be /data/git/repositories/<user>/<repo>.git, not /data/git/repositories/repositories/<user>/<repo>.git.
6. Set ROOT to the container path
In the app.ini used by the container, configure:
[repository]
ROOT = /data/git/repositoriesIf your image maps the host directory to another internal path, use that internal path instead. Never place the host-only path in ROOT; it is not visible from inside the container.
7. Recreate or restart the container
Apply the updated volume mapping and configuration, then start the same rootful or rootless image family. Watch the logs for mount, permission, database, hook, and LFS errors. A newly created empty repository directory inside the container is a warning that the mount target or mapping is wrong; stop and correct it before users write data.
Verify the new location before retiring the old one
Verification should exercise both the application database and the filesystem. Test with a non-administrator account as well as an administrator where possible.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Browse: Open several existing repositories, including one with branches, tags, releases, issues, and protected branches. Confirm the web interface shows the expected history and references.
- Clone: Clone over the protocols your users actually use. Inspect the clone for the expected commits, tags, submodules, and default branch.
- Push: Create a temporary branch, push it, and remove it. This confirms write permission, repository locking, and receive-side processing.
- Hooks: Trigger any repository or server hooks used by your deployment. Hooks must remain executable; a share mounted with execution disabled can allow browsing but break pushes or automation.
- Large File Storage: Fetch an existing LFS object and push a test LFS object if your instance uses LFS. Confirm that the LFS path is mounted and writable, not merely the Git repository path.
- Background operations: Run the maintenance, indexing, migration, and scheduled jobs that matter to your installation. Check their logs for “permission denied,” “repository not found,” stale path, or read-only filesystem messages.
- Restart persistence: Restart Gitea, and for Docker recreate the container, then repeat a browse and clone test. The data must still be present after the service starts with the persistent mount.
After successful tests, make a fresh backup from the new location and document the mount, container mapping, ownership, and configuration path. Retain the old copy for a defined rollback period rather than deleting it immediately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.NAS-specific requirements
A NAS can work, but it changes failure modes. Gitea’s FAQ warns that repository filesystems mounted from a NAS must support script execution because Git hooks and related repository operations may execute files from the repository. Verify that the share and its mount options do not disable execution.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
- Make the NAS mount available before Gitea starts, including after a host reboot or network interruption.
- Confirm the server-side account or mapped UID/GID can read, write, create directories, rename files, and preserve executable bits.
- Test clone, push, hook execution, and LFS under realistic network conditions, not only a web page load.
- Plan for temporary unavailability. Starting Gitea while the share is absent can expose an empty local mount point and lead to accidental writes on the wrong filesystem.
- Use NAS snapshots or an independent backup, and test restoring both a repository and its related database record.
Latency and throughput are environment-dependent; there is no official benchmark that makes a NAS universally suitable or unsuitable for Gitea.
Troubleshooting common failures
Repositories appear missing
Check the effective ROOT value and whether it is absolute. In Docker, inspect the path from inside the container and verify that the host directory is actually mounted there. Then check for an extra directory level and confirm every repository ends in .git beneath its user directory.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Gitea creates new repositories on the old disk
This usually means the edited app.ini is not the file used by the running instance, the service was not restarted, or ROOT is relative. Confirm the configuration mount for Docker, inspect the running container’s configuration path, and set an absolute container-visible path.
Pushes fail with permission denied
Compare the owner, group, mode, and mount options of the destination with the identity that runs Gitea. In Docker, correct ownership using the image’s UID/GID rather than the host login account. On a NAS, verify server-side permissions and that the share is not read-only.
Hooks do not run
Check executable bits on hook files and the filesystem’s execution option. A NAS share that disallows execution can serve repository objects while preventing hook scripts from running. Restore executable permissions and remount with an option that permits execution where your security policy allows it.
LFS downloads return errors
Confirm that LFS objects were copied, that the configured LFS path is mounted into the container when applicable, and that its owner can read and write. Moving only repository.ROOT does not automatically move LFS data.
The container starts but writes to the host disk
Look for a missing or incorrectly spelled volume mapping. If the container path is not mounted, Docker presents an empty directory from the container’s writable layer. Stop the instance, correct the mapping, verify the target from inside the container, and restore any test data written to the wrong location from backup.
The host reboot leaves Gitea with an empty repository directory
Make the block device or NAS mount persistent and order Gitea to start after the mount is available. Until that dependency is reliable, keep Gitea stopped during boot maintenance to avoid writing into the mount point on the original filesystem.
Rollback and long-term maintenance
If verification fails, stop Gitea, restore the previous ROOT value and volume mapping, and start it against the untouched original directory. Do not merge partially modified trees from both locations; restore from the backup or repeat the copy from a known-consistent source.
Once the new location has operated successfully through a restart and a backup has completed, update runbooks and monitoring with the new path. Monitor free space for repositories and LFS independently when they use separate volumes, alert on a missing mount, and periodically test restoring a repository, its LFS objects, and the database metadata together.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
