refactor: extract scheduler to standalone repository
Scheduler service moved to git.schweitz.net/jpmschweitzer/scheduler - Source code removed from this repository - Stack file updated to use container image from Gitea registry - Added Gitea Actions runner to gitea stack for CI/CD - Documentation updated with external service reference 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,53 @@
|
||||
# External Services
|
||||
|
||||
Services that have been extracted to their own repositories but are still part of the overall infrastructure.
|
||||
|
||||
---
|
||||
|
||||
## Scheduler
|
||||
|
||||
**Repository:** https://git.schweitz.net/jpmschweitzer/scheduler
|
||||
**Container Image:** `git.schweitz.net/jpmschweitzer/scheduler:latest`
|
||||
**Stack File:** `stacks/scheduler.yml` (remains in portainer-core)
|
||||
|
||||
### Overview
|
||||
The Scheduler service handles system-wide maintenance orchestration including:
|
||||
- Docker config backups
|
||||
- Documentation mirroring
|
||||
- Task automation via REST API
|
||||
- Integration with Library Desk for consolidation jobs
|
||||
|
||||
### Deployment
|
||||
- Container image built via Gitea Actions on release
|
||||
- Stack file in portainer-core defines volumes, environment, and network
|
||||
- Watchtower monitors for image updates
|
||||
|
||||
### Development
|
||||
To make changes:
|
||||
1. Clone: `git clone gitea:jpmschweitzer/scheduler.git`
|
||||
2. Make changes
|
||||
3. Create a release in Gitea to trigger build
|
||||
4. Watchtower will auto-update the running container
|
||||
|
||||
### API
|
||||
- Health: `http://scheduler:8090/health`
|
||||
- Tasks: `http://scheduler:8090/tasks` (requires API key)
|
||||
- Docs: `http://scheduler:8090/docs`
|
||||
|
||||
---
|
||||
|
||||
## Tatlock
|
||||
|
||||
**Repository:** https://git.schweitz.net/jpmschweitzer/tatlock
|
||||
**Location:** `/home/jpmschweitzer/Projects/tatlock`
|
||||
|
||||
### Overview
|
||||
Tatlock is a separate project maintained in its own repository.
|
||||
|
||||
---
|
||||
|
||||
## Future Migrations
|
||||
|
||||
The following services are planned for extraction:
|
||||
- **core-api** - Infrastructure management API
|
||||
- **library-desk** - Knowledge management and consolidation service
|
||||
Reference in New Issue
Block a user