Migrate infrastructure-template to use new standardized scripts and workflows #9

Closed
opened 2026-05-24 08:15:17 -06:00 by Xeplosion · 2 comments
Owner

Type of chore

Tooling / CI

What needs doing and why?

infrastructure-template predates the conventions defined in .forgejo. It uses restart.sh instead of service-start.sh, lacks validate.sh, healthcheck.sh, and xegames.config.yml, deploys from release branch instead of main, and uses two SSH connections instead of one. It needs to be brought in line with org standards before template-script supersedes it.

Risk or impact

Existing repos cloned from infrastructure-template (node-nginx, node-bungeecord, etc.) will need their workflows and scripts updated manually afterward.

Additional context

No response

Checklist

  • I have described why this is worth doing now
  • I have noted any risk or impact on other work
### Type of chore Tooling / CI ### What needs doing and why? `infrastructure-template` predates the conventions defined in `.forgejo`. It uses `restart.sh` instead of `service-start.sh`, lacks `validate.sh`, `healthcheck.sh`, and `xegames.config.yml`, deploys from `release` branch instead of `main`, and uses two SSH connections instead of one. It needs to be brought in line with org standards before `template-script` supersedes it. ### Risk or impact Existing repos cloned from `infrastructure-template` (`node-nginx`, `node-bungeecord`, etc.) will need their workflows and scripts updated manually afterward. ### Additional context _No response_ ### Checklist - [x] I have described why this is worth doing now - [x] I have noted any risk or impact on other work
Author
Owner

Blocking on a decision about the future of this repo. Now that template-script is planned, infrastructure-template may be fully superseded by it rather than migrated. Options are: (1) migrate infrastructure-template to the new standards and keep it alongside template-script, (2) deprecate infrastructure-template once template-script is ready and migrate existing repos (node-nginx, node-bungeecord, etc.) directly to the new template, or (3) rename infrastructure-template to template-script and migrate it in place. Leaving this open until template-script is created and the overlap is clearer.

Blocking on a decision about the future of this repo. Now that `template-script` is planned, `infrastructure-template` may be fully superseded by it rather than migrated. Options are: (1) migrate `infrastructure-template` to the new standards and keep it alongside `template-script`, (2) deprecate `infrastructure-template` once `template-script` is ready and migrate existing repos (`node-nginx`, `node-bungeecord`, etc.) directly to the new template, or (3) rename `infrastructure-template` to `template-script` and migrate it in place. Leaving this open until `template-script` is created and the overlap is clearer.
Author
Owner

The infrastructure-template repo has been archived and is no longer in use. The standardized scripts and workflows it would have been migrated to are now distributed via the .forgejo sync system to template-script, which supersedes it.

Closing as irrelevant.

The `infrastructure-template` repo has been archived and is no longer in use. The standardized scripts and workflows it would have been migrated to are now distributed via the `.forgejo` sync system to `template-script`, which supersedes it. Closing as irrelevant.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
XeplosionGames/.profile#9
No description provided.