Hithomelabs/CFTunnels
10
0
Fork 4
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Hithomelabs/CFTunnels#139: Remove portainer-automation service from docker-compose.yaml (now managed independently via portainer-automation/docker-compose.yaml)
All checks were successful
sample gradle build and test / build (pull_request) Successful in 1m58s
Details
Daily cloudflare API integration test / cloudflare-api-test (push) Successful in 1m49s
Details
Promote image with tag test to prod / tag (push) Successful in 6s
Details
Promote image with tag test to prod / build_tag_push (push) Successful in 13s
Details
sample gradle build and test / tag (push) Successful in 7s
Details
sample gradle build and test / build_tag_push (push) Successful in 2m30s
Details

Browse Source
This commit is contained in:
Dave the Dev 2026-07-09 05:04:48 +00:00
parent 35db41573a
commit 8ee2abdbd7
1 changed files with 0 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docker-compose.yaml
View File

@ -30,15 +30,3 @@ services:
- "${DB_PORT}:5432" - "${DB_PORT}:5432"
volumes: volumes:
- ${DB_PATH}:/var/lib/postgresql/data - ${DB_PATH}:/var/lib/postgresql/data
portainer-automation:
image: gitea.hithomelabs.com/hithomelabs/portainer-automation:${ENV}
container_name: portainer-automation_${ENV}
ports:
- "${PORTAINER_AUTOMATION_PORT:-8081}:8081"
environment:
- SPRING_PROFILES_ACTIVE=${SPRING_PROFILES_ACTIVE:-local}
- PORTAINER_API_KEY=${PORTAINER_API_KEY}
- PORTAINER_SERVICE_API_KEY=${PORTAINER_SERVICE_API_KEY}
env_file:
- stack.env
restart: unless-stopped