Migrate gitea data from on instance to another

Migrating Gitea from one instance to another is essentially a backup and restore operation. Since Gitea stores its data in two main places—the database and the filesystem—the process involves moving both while keeping them in sync.

The most reliable method is using Gitea’s built-in dump command, which packages everything into a single zip file.

Method 1: The “Dump & Restore” (Recommended)

This method is the cleanest because it ensures all metadata (issues, pull requests, users) is captured along with the code.

Add website to Authentik

Integrating a new application into Authentik using a username-based approach (like <user>) typically involves setting up a Provider and an Application. Since you are using a local IP (192.168.0.x ), you’ll likely be using Authentik as a Forward Proxy or via an Outpost.

Here is the step-by-step workflow to get paper.<domain>.com connected:

1. Create the Provider

The Provider defines how Authentik communicates with your website.

1. Navigate to Resources > Providers and click Create.

   authentik

Install NFS on Ubuntu

Connect to my NAS via NFS

make the directory

sudo mkdir /media/nfs

Change permissions to all

sudo chown 777 /media/nfs

add mount to fstab

sudo nano /etc/fstab

192.168.0.x:/volume/NFS /media/nfs nfs auto 0 0

install NSF

sudo apt install nfs-common

sudo mount --a

Check that the Synology or disk host gives permissions to the ip address to access the mounted drive

How to migrate a plex server to a new Host

How to Migrate a Plex Server to a New Server (Ubuntu/Linux)

This guide outlines the steps to migrate a Plex Media Server from one Ubuntu server to another while preserving your library data, watch history, and metadata.

Prerequisites

1. Access: Root or sudo access to both the Source (Old) and Destination (New) servers.
2. Media: Your actual media files (Movies, TV) must be at the exact same mount path on the new server as they were on the old one. If they change location, you will need to remap them later.
3. Versions: Ensure both servers are running the same version of Plex Media Server to avoid database compatibility issues.

Step 1: Preparation on Source Server

1. Disable “Empty Trash”:

   plexmigrateubuntu

How I use and installed Gitea in my homelab

Initial Setup

NB: Create Initial Repo and Change Repo Name

cd /home/<user>/<project>
git config --global user.name "Your Name"
git config --global user.email "[email protected]" 
git init
git remote add origin https://<user>:YOUR_GITEA_TOKEN@gitea.<domain>.com/<user>/traefik-n8n.git
git add .
git commit -m "Initial commit"
git branch -M main
git push -u origin main

Updates

NB: Change to app directory

cd /home/<user>/WHAT
git add .
git commit -m "Update files"
git push -u origin main

1. Install Git

sudo apt update && sudo apt install git -y

Blog Post Workflow and instructions using Jekyll (similar to Hugo)

Blog Publishing Agent Workflow

This document outlines the “AI Agent” workflow we have constructed. This system automates the lifecycle of a blog post from ideation in Obsidian to deployment on your self-hosted Jekyll server.

The Pipeline:

1. Create: Obsidian Templater script generates a structured post.
2. Sync: Local Shell Script (deploy_blog.sh) pushes changes to the server.
3. Build: Remote Shell Script (blogupdate.sh) compiles the Jekyll site.
4. Trigger: Obsidian “Shell Commands” plugin executes the pipeline with one click.

1. The Creator (Obsidian Template)

File: Meta/Templates/JekyllBlogPost.md Purpose: Standardizes frontmatter, handles file naming (date + slug), and sorts posts into the correct directory (Blog or Documentation).