devteam/sharenet
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove cleanup script to not check for nonexistent forgejo docker container
Some checks failed
CI/CD Pipeline / Test Backend (push) Failing after 3s
Details
CI/CD Pipeline / Test Frontend (push) Failing after 22s
Details
CI/CD Pipeline / Build and Push Docker Images (push) Has been skipped
Details
CI/CD Pipeline / Deploy to Production (push) Has been skipped
Details

Browse source
This commit is contained in:
continuist 2025-06-29 17:58:12 -04:00
parent 063a6016ae
commit 5a42d81b38
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
scripts/cleanup.sh
View file

@ -18,7 +18,7 @@ REGISTRY_DIR="${REGISTRY_DIR:-/opt/registry}"
DRY_RUN="${DRY_RUN:-false}"
# Critical infrastructure protection
CRITICAL_CONTAINERS="harbor-core,harbor-db,harbor-jobservice,harbor-log,harbor-portal,nginx,redis,registry,registryctl,trivy-adapter,forgejo-runner"
CRITICAL_CONTAINERS="harbor-core,harbor-db,harbor-jobservice,harbor-log,harbor-portal,nginx,redis,registry,registryctl,trivy-adapter"
CRITICAL_IMAGES="goharbor,forgejo-runner"
CRITICAL_VOLUMES="harbor"
CRITICAL_NETWORKS="harbor"
@ -63,6 +63,13 @@ check_critical_infrastructure() {
log_success "All critical infrastructure containers are running"
fi
# Check Forgejo runner service
if systemctl is-active --quiet forgejo-runner.service; then
log_success "Forgejo runner service is running"
else
log_warning "Forgejo runner service is not running"
fi
echo
}