Migrate infrastructure-template to use new standardized scripts and workflows #9
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
Due date
No due date set.
Depends on
#4 Create template-script repo for infrastructure and config repos
XeplosionGames/.profile
Reference
XeplosionGames/.profile#9
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?
Type of chore
Tooling / CI
What needs doing and why?
infrastructure-templatepredates the conventions defined in.forgejo. It usesrestart.shinstead ofservice-start.sh, lacksvalidate.sh,healthcheck.sh, andxegames.config.yml, deploys fromreleasebranch instead ofmain, and uses two SSH connections instead of one. It needs to be brought in line with org standards beforetemplate-scriptsupersedes 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
Blocking on a decision about the future of this repo. Now that
template-scriptis planned,infrastructure-templatemay be fully superseded by it rather than migrated. Options are: (1) migrateinfrastructure-templateto the new standards and keep it alongsidetemplate-script, (2) deprecateinfrastructure-templateoncetemplate-scriptis ready and migrate existing repos (node-nginx,node-bungeecord, etc.) directly to the new template, or (3) renameinfrastructure-templatetotemplate-scriptand migrate it in place. Leaving this open untiltemplate-scriptis created and the overlap is clearer.The
infrastructure-templaterepo 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.forgejosync system totemplate-script, which supersedes it.Closing as irrelevant.