Create template-script repo for infrastructure and config repos #4
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Compat/Breaking
Compat/Deprecation
Kind
Bug
Kind
Chore
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Investigation
Kind
Question
Kind
Security
Kind
Testing
Meta/Good First Issue
Meta/Help Wanted
Meta/Stale
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Resolution
Confirmed
Resolution
Duplicate
Resolution
Invalid
Resolution
Won't Fix
Status
Abandoned
Status
Blocked
Status
Needs More Info
Status
Needs Triage
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 27 minutes 10 seconds
Due date
Xeplosion
27 minutes 10 seconds
No due date set.
Blocks
#9 Migrate infrastructure-template to use new standardized scripts and workflows
XeplosionGames/.profile
Reference
XeplosionGames/.profile#4
Loading…
Add table
Add a link
Reference in a new issue
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?
What problem does this solve?
There is no standardized starting point for new infrastructure repos (nginx, systemctl, Docker). Each one is currently set up manually with inconsistent structure, scripts, and workflows.
Proposed solution
Create
template-scriptin XeplosionGames as a Forgejo template repo containingxegames.config.yml,scripts/service-start.sh,scripts/service-stop.sh,scripts/validate.sh,scripts/healthcheck.sh,scripts/build.sh,.forgejo/workflows/ci-script.yml,deploy-production.yml,deploy-test.yml,rollback.yml,healthcheck.yml,release.yml, ISSUE_TEMPLATE copies, andpull_request_template.md. All copied from.forgejo.Alternatives considered
No response
Additional context
No response
Checklist
Escalating to
Priority/Critical.template-scriptis now a blocker for multiple open issues — the migration decision forinfrastructure-templatecannot be made until this template exists, and active infrastructure development onnode-nginx,node-bungeecord, and other service repos is halted waiting for standardized workflows and scripts. This is the highest priority template repo to complete.Closing as complete.
template-scripthas been created as a Forgejo template repo containing all standard issue templates, PR template,xegames.config.yml, script stubs (service-start.sh,service-stop.sh,validate.sh,healthcheck.sh,build.sh), and all CI/CD workflows (ci-script.yml,deploy-production.yml,deploy-test.yml,rollback.yml,healthcheck.yml,release.yml). All files sourced from.forgejo. The infrastructure-template migration decision remains open in a separate issue tracked here.