Skip to content

Conversation

@arkhi
Copy link
Member

@arkhi arkhi commented Dec 5, 2025

I only tweaked the workflow from staging for now, not trying to optimise and reuse any common code.

  • Add GitHub Workflow to deploy on a self-hosted server.
  • Differentiate secrets between Staging and Production.
  • Remove GitHub generated CNAME file.

Once this PR merged, we can make another one from staging to master, which should deploy the new code to our server before we merge to master.

Then switch DNS to that server.

@arkhi arkhi changed the title chore: Deploy to self-hosted prod. chore: Deploy to self-hosted prod Dec 5, 2025
@arkhi arkhi marked this pull request as ready for review December 7, 2025 10:26
@arkhi arkhi requested a review from j9t December 8, 2025 20:15
@arkhi arkhi removed the enhancement label Dec 8, 2025
Copy link
Member

@j9t j9t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I follow a different convention for names in workflows but only mention this if of interest. Fine to use a different one. LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants