167 lines
4.3 KiB
Markdown
167 lines
4.3 KiB
Markdown
# Gitea Access for NaviDocs
|
|
|
|
## Repository Status
|
|
|
|
✅ **Repository exists and is functional** - All code is pushed and accessible
|
|
|
|
## Current Situation
|
|
|
|
The NaviDocs repository was created via `git push` (Gitea's ENABLE_PUSH_CREATE feature), which creates the Git repository on disk but **doesn't register it in Gitea's database**. This means:
|
|
|
|
- ✅ **Git operations work** (clone, push, pull, etc.)
|
|
- ❌ **Web UI doesn't show the repository** (404 on http://localhost:4000/ggq-admin/navidocs)
|
|
- ❌ **API doesn't list the repository**
|
|
|
|
## Working Git Access
|
|
|
|
**Repository Location**: `/home/setup/gitea/data/repos/ggq-admin/navidocs.git`
|
|
|
|
**Git Remote URL**: `http://localhost:4000/ggq-admin/navidocs.git`
|
|
|
|
**All Git commands work**:
|
|
```bash
|
|
# Clone
|
|
git clone http://localhost:4000/ggq-admin/navidocs.git
|
|
|
|
# Check commits
|
|
cd /home/setup/navidocs
|
|
git log --oneline
|
|
# Shows all 20 commits ✅
|
|
|
|
# Verify remote
|
|
git ls-remote origin
|
|
# Shows: bf9303228dbf49b4e31121665d6904b289268374 refs/heads/master ✅
|
|
|
|
# Push/pull
|
|
git push origin master # Works ✅
|
|
git pull origin master # Works ✅
|
|
```
|
|
|
|
## Workaround Options
|
|
|
|
### Option 1: Use Git Directly (Current - Works)
|
|
Continue using Git commands directly. The repository is fully functional via Git, you just can't browse it in the Gitea web UI.
|
|
|
|
**Pros**: Already working, no changes needed
|
|
**Cons**: No web UI browsing
|
|
|
|
### Option 2: Manually Register in Gitea Database
|
|
Use Gitea's `doctor` command to check and repair the repository database:
|
|
|
|
```bash
|
|
cd /home/setup/gitea
|
|
./gitea doctor check --run=doctor-check-db-consistency
|
|
./gitea doctor recreate-table
|
|
```
|
|
|
|
**Note**: This requires stopping Gitea service first.
|
|
|
|
### Option 3: Create Fresh via Web UI
|
|
1. Log into Gitea web UI: http://localhost:4000
|
|
2. Click "+" → "New Repository"
|
|
3. Name: navidocs-web
|
|
4. Create repository
|
|
5. Push code to new repository
|
|
|
|
```bash
|
|
cd /home/setup/navidocs
|
|
git remote rename origin origin-old
|
|
git remote add origin http://localhost:4000/ggq-admin/navidocs-web.git
|
|
git push -u origin master
|
|
```
|
|
|
|
### Option 4: Use Different Git Hosting (Recommended for Production)
|
|
- **GitHub**: https://github.com
|
|
- **GitLab**: https://gitlab.com
|
|
- **Bitbucket**: https://bitbucket.org
|
|
|
|
All offer free private repositories with better UI/features than self-hosted Gitea.
|
|
|
|
## Current Status (As-Is)
|
|
|
|
**Git Repository**: ✅ Fully functional
|
|
- Location: `/home/setup/gitea/data/repos/ggq-admin/navidocs.git`
|
|
- Commits: 20 total
|
|
- Branch: master
|
|
- Latest commit: bf93032 "docs: Add session status summary"
|
|
|
|
**Code Status**: ✅ All code committed and pushed
|
|
- Database schema: ✅
|
|
- Backend API: ✅
|
|
- OCR services (3 engines): ✅
|
|
- Documentation (17 files): ✅
|
|
- StackCP evaluation: ✅
|
|
- Everything is in Git
|
|
|
|
**Verification**:
|
|
```bash
|
|
# Clone from Gitea (works)
|
|
cd /tmp
|
|
git clone http://localhost:4000/ggq-admin/navidocs.git navidocs-test
|
|
cd navidocs-test
|
|
ls -la # Shows all files ✅
|
|
git log --oneline | wc -l # Shows 20 commits ✅
|
|
```
|
|
|
|
## Recommendation
|
|
|
|
**For Now**: Use Git directly (Option 1)
|
|
- Your code is safe and versioned
|
|
- All Git operations work perfectly
|
|
- No data loss risk
|
|
|
|
**For Production**: Use GitHub/GitLab (Option 4)
|
|
- Better UI/collaboration features
|
|
- Free private repositories
|
|
- CI/CD integration
|
|
- Issue tracking
|
|
|
|
## Accessing Your Code
|
|
|
|
**Local Development**:
|
|
```bash
|
|
cd /home/setup/navidocs
|
|
# All code is here, fully up to date
|
|
```
|
|
|
|
**Clone to Another Machine**:
|
|
```bash
|
|
git clone http://localhost:4000/ggq-admin/navidocs.git
|
|
```
|
|
|
|
**Or Clone from Filesystem** (if Gitea is down):
|
|
```bash
|
|
git clone /home/setup/gitea/data/repos/ggq-admin/navidocs.git
|
|
```
|
|
|
|
## Verification Commands
|
|
|
|
```bash
|
|
# Verify repository exists
|
|
ls -la /home/setup/gitea/data/repos/ggq-admin/navidocs.git/
|
|
|
|
# Check commits
|
|
cd /home/setup/navidocs
|
|
git log --oneline | head -10
|
|
|
|
# Verify remote connection
|
|
git ls-remote origin
|
|
|
|
# Clone test
|
|
cd /tmp
|
|
git clone http://localhost:4000/ggq-admin/navidocs.git test-clone
|
|
cd test-clone && ls -la
|
|
```
|
|
|
|
All these work perfectly! ✅
|
|
|
|
---
|
|
|
|
**Bottom Line**: Your NaviDocs code is **safe, versioned, and accessible via Git**. The Gitea web UI issue is cosmetic - all actual Git functionality works fine.
|
|
|
|
For viewing/browsing code, use:
|
|
- Local filesystem: `/home/setup/navidocs/`
|
|
- VS Code: `code /home/setup/navidocs/`
|
|
- Git commands: `git log`, `git show`, `git diff`
|
|
|
|
**No data loss. Everything is committed and pushed.** ✅
|