Skip to content

Conversation

tobil4sk
Copy link
Member

Unlike #178, this doesn't change the way the site is deployed, which caused some DNS issue when migrating nekovm.org. This should get the site deploying again while we figure out how to solve that.

@kLabz
Copy link
Contributor

kLabz commented Aug 31, 2024

There's no problem anymore with how nekovm is deployed though?
I don't think #178 is wrong, and looks less weird than this git user thing 🤔

@tobil4sk
Copy link
Member Author

There's no problem anymore with how nekovm is deployed though?
I don't think #178 is wrong, and looks less weird than this git user thing 🤔

Yeah #178 is the correct solution, but if it is still blocked due to the DNS issues, then this version uses the same gh-pages branch workflow as travis so it should be safe to merge without breaking anything. This could be merged to get deployment working immediately in the meantime, then we can move to the setup in #178 once we are more confident about that.

The git user setup allows pushing/committing from the github-actions[bot] user, which has permission to push from the automated token and doesn't require a PAT being set up as it was previously for the @haxe-ci bot.

@kLabz kLabz mentioned this pull request May 12, 2025
@tobil4sk
Copy link
Member Author

No longer needed as #178 has been merged and deployed.

@tobil4sk tobil4sk closed this May 15, 2025
@tobil4sk tobil4sk deleted the fix/deploy-2 branch May 15, 2025 12:52
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.

2 participants