46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
# Self-Hosted Services Planning
|
|
|
|
## Git Repository Hosting
|
|
### Options to Research
|
|
- **Gitea**: Lightweight, Go-based, minimal resource usage
|
|
- **Forgejo**: Gitea fork, community-driven development
|
|
- **GitLab CE**: Feature-rich but more resource intensive
|
|
- **Gogs**: Simple, lightweight alternative
|
|
|
|
### Requirements
|
|
- [ ] Web interface for repository management
|
|
- [ ] Git over SSH and HTTPS
|
|
- [ ] User management and permissions
|
|
- [ ] Issue tracking (optional)
|
|
- [ ] CI/CD integration (future consideration)
|
|
|
|
### Installation Considerations
|
|
- Docker deployment vs native installation
|
|
- Database requirements (SQLite vs PostgreSQL)
|
|
- Reverse proxy setup for HTTPS
|
|
- Backup strategy for repositories
|
|
|
|
## Cloud Storage Solutions
|
|
### Options to Research
|
|
- **Nextcloud**: Full-featured, extensive app ecosystem
|
|
- **ownCloud**: Original project, stable and mature
|
|
- **Seafile**: Performance-focused file sync
|
|
- **Syncthing**: Decentralized sync (no server needed)
|
|
|
|
### Requirements
|
|
- [ ] File synchronization across devices
|
|
- [ ] Web interface for file management
|
|
- [ ] Mobile app support
|
|
- [ ] Calendar and contacts sync
|
|
- [ ] Document editing (optional)
|
|
|
|
## Service Integration
|
|
- Single sign-on between services
|
|
- Shared storage for configuration backups
|
|
- Monitoring and logging setup
|
|
- Automated backups and disaster recovery
|
|
|
|
## Resource Planning
|
|
- Estimate RAM and storage requirements
|
|
- Consider containerization with Docker/Podman
|
|
- Plan for service discovery and networking |