DAM/ts-TEMPLATE
Template
1
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases Wiki Activity

Continuous Integration #2

New Issue
Open
opened 2025-04-09 20:05:17 -05:00 by peskyadmin · 0 comments
peskyadmin commented 2025-04-09 20:05:17 -05:00
Owner
Copy Link

Every-time there is an update to a file other than README.md there should be a git action that uses a reusable authkey to deploy the service(s) via `docker-compose up -d' and verifies the service is up and healthy.

  1. get key and store as gitea secret
  2. create github action
  • Clone repo to linux nuc
  • update docker compose with ts-auth-key
  • OPTIONAL if there is base config needed maybe call a script that stored in each repo for a dummy initialization so far no such problems exist
  • verify service has connected to tailscale
  • use docker health check for every service
  • try and load endpoint (look at /tailscale/config/serve.json to see what protocols to verify
  • OPTIONAL call a test script that is stored in each repo for a service specific healthceck

If service passes all check apply a certified tag to the repo.

BONUS somehow figure out how to validate the deployment when the service image updates to verify which version of the service works with the supplied configs.

Every-time there is an update to a file other than `README.md` there should be a git action that uses a reusable authkey to deploy the service(s) via `docker-compose up -d' and verifies the service is up and healthy. 1. get key and store as gitea secret 2. create github action - Clone repo to linux nuc - update docker compose with ts-auth-key - OPTIONAL if there is base config needed maybe call a script that stored in each repo for a dummy initialization so far no such problems exist - verify service has connected to tailscale - use docker health check for every service - try and load endpoint (look at `/tailscale/config/serve.json` to see what protocols to verify - OPTIONAL call a test script that is stored in each repo for a service specific healthceck If service passes all check apply a certified tag to the repo. BONUS somehow figure out how to validate the deployment when the service image updates to verify which version of the service works with the supplied configs.
peskyadmin added the
enhancement
 label 2025-04-09 20:05:17 -05:00
peskyadmin added this to the Side Car Based FOSS Library project 2025-04-09 20:05:17 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project Side Car Based FOSS Library
Assignees
Clear assignees
peskyadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DAM/ts-TEMPLATE#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?