Add: Gitea push instructions with updated location
Updated Gitea location from 192.168.88.200:3000 to gitea.jgitta.com (resolves to 192.168.88.110 behind Caddy reverse proxy) Includes: - Complete push instructions - Authentication details - Repository structure - Ready-to-use commit message
This commit is contained in:
@@ -0,0 +1,121 @@
|
||||
# Gitea Push Instructions
|
||||
|
||||
## Gitea Location Update
|
||||
|
||||
**Previous Location:** `http://192.168.88.200:3000`
|
||||
**Current Location:** `https://gitea.jgitta.com` (resolves to 192.168.88.110, behind Caddy reverse proxy)
|
||||
|
||||
## Repository Details
|
||||
|
||||
- **Repository:** https://gitea.jgitta.com/jgitta/homelab-configs
|
||||
- **Branch:** main
|
||||
- **Subdirectory:** nextcloud-backup/
|
||||
|
||||
## Contents to Push
|
||||
|
||||
This directory contains the complete Nextcloud Backblaze B2 backup solution:
|
||||
|
||||
### Scripts
|
||||
- `nextcloud-backup-to-backblaze.sh` - Main backup script
|
||||
- `nextcloud-backup.service` - systemd service
|
||||
- `nextcloud-backup.timer` - Daily scheduler
|
||||
|
||||
### Configuration
|
||||
- `nextcloud-backup.env.template` - Config template
|
||||
- `nextcloud-backup.env.configured` - Deployed config (with credentials)
|
||||
|
||||
### Documentation
|
||||
- `README.md` - Quick start guide
|
||||
- `DEPLOYMENT_REPORT.md` - Complete deployment details
|
||||
- `README_NEXTCLOUD_BACKUPS.md` - Feature overview
|
||||
- `BACKUP_QUICK_START.md` - Quick reference
|
||||
- `NEXTCLOUD_BACKBLAZE_SETUP.md` - Detailed guide
|
||||
- `DEPLOYMENT_CHECKLIST.md` - Validation checklist
|
||||
- And more...
|
||||
|
||||
## How to Push
|
||||
|
||||
### Option 1: Direct Push (from this directory)
|
||||
|
||||
```bash
|
||||
cd /home/jgitta/nextcloud-backup-solution
|
||||
|
||||
# Set remote if not already set
|
||||
git remote set-url origin https://gitea.jgitta.com/jgitta/homelab-configs.git
|
||||
|
||||
# Push to Gitea
|
||||
git push -u origin master:main
|
||||
```
|
||||
|
||||
### Option 2: Add to Existing Homelab Configs Repo
|
||||
|
||||
```bash
|
||||
# Clone the existing repo
|
||||
git clone https://gitea.jgitta.com/jgitta/homelab-configs.git
|
||||
cd homelab-configs
|
||||
|
||||
# Create nextcloud-backup subdirectory
|
||||
mkdir -p nextcloud-backup
|
||||
|
||||
# Copy all files from solution directory
|
||||
cp /home/jgitta/nextcloud-backup-solution/* nextcloud-backup/
|
||||
|
||||
# Commit and push
|
||||
git add nextcloud-backup/
|
||||
git commit -m "Add: Nextcloud Backblaze B2 backup solution
|
||||
|
||||
Complete automated backup system for Nextcloud:
|
||||
- Daily backups at 2 AM to Backblaze B2
|
||||
- Database + file backups with zstd compression
|
||||
- Systemd integration for reliable scheduling
|
||||
- Cost-optimized (~$0.01-0.02/month)
|
||||
- Comprehensive documentation
|
||||
|
||||
Deployment Status: ✅ Production ready
|
||||
First Backup: ✅ Verified (203MB DB + 1.3GB files)"
|
||||
|
||||
git push origin main
|
||||
```
|
||||
|
||||
## Current Git Status
|
||||
|
||||
**Location:** `/home/jgitta/nextcloud-backup-solution/`
|
||||
|
||||
**Commits:**
|
||||
```
|
||||
a9c5698 Add: Comprehensive README for nextcloud-backup solution
|
||||
2625cf3 Add: Nextcloud Backblaze B2 backup solution - automated daily backups
|
||||
```
|
||||
|
||||
**Files Ready to Push:**
|
||||
- 15 files total
|
||||
- 3.4 KB backup script
|
||||
- ~50 KB documentation
|
||||
- Configuration templates
|
||||
|
||||
## Authentication
|
||||
|
||||
If you get authentication errors:
|
||||
|
||||
```bash
|
||||
# Use the Gitea web UI to generate a personal access token:
|
||||
# 1. Go to https://gitea.jgitta.com
|
||||
# 2. Settings → Applications → Personal Access Tokens
|
||||
# 3. Create new token with "repo" scope
|
||||
# 4. Use token as password when prompted:
|
||||
|
||||
git clone https://gitea.jgitta.com/jgitta/homelab-configs.git
|
||||
# When prompted for password, use your access token
|
||||
```
|
||||
|
||||
## Next Steps
|
||||
|
||||
1. Push this repository to Gitea
|
||||
2. Create a Gitea issue or documentation linking to the backup solution
|
||||
3. Add the solution to your infrastructure documentation
|
||||
4. Consider setting up automatic backups of this documentation
|
||||
|
||||
---
|
||||
|
||||
**Repository Status:** ✅ Ready to push
|
||||
**Contents:** Complete, documented, tested
|
||||
Reference in New Issue
Block a user