Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update maxo.yml, switching maxo to GitHub release PURLs #998

Merged
merged 4 commits into from
Jun 13, 2024

Conversation

matentzn
Copy link
Contributor

We moved MAxO to using GitHub releases instead of raw.github locations for the release files. This is always a painful process, as you have cannot have two conflicting wildcard based rewrite rules in nginx, so all have to be done manually. I added a test for all of them.

matentzn added 4 commits June 11, 2024 22:06
We moved MAxO to using GitHub releases instead of raw.github locations for the release files. This is always a painful process, as you have cannot have two conflicting wildcard based rewrite rules in nginx, so all have to be done manually. I added a test for all of them.
@jamesaoverton
Copy link
Member

@matentzn Do you want to go ahead with this PR, or simplify it based on our discussion?

@matentzn
Copy link
Contributor Author

Its fine, you can go ahead!

@jamesaoverton jamesaoverton merged commit 64bba89 into master Jun 13, 2024
1 check passed
@jamesaoverton jamesaoverton deleted the matentzn-patch-9 branch June 13, 2024 15:08
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