-
Notifications
You must be signed in to change notification settings - Fork 16
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
Host packages as pacman repository using GitHub Pages #26
base: main
Are you sure you want to change the base?
Conversation
Specifying the repo was not required.
This is very cool |
Is there a timeline on when this will get reviewed? |
It could be fine for me, but I don't know if this either:
|
@NeroReflex here is some info on limits on github pages: https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#usage-limits If we start exceeding 100 GB of bandwidth per month, we might be asked to tone it down and we are not allowed to use pages for commercial purposes. There is also a soft limit of 1 GB for a pages site. The TOS doesn't really talk about pages. I think we should comply with all of that even if we host a repo through pages. The users should be limited to contributors and maybe our build system. |
1GB limit means basically only 2 kernels... Have I understood it correctly? |
I think we could probably fit at least 5, since the packages are compressed. We only host one at a time, though. Each commit causes a new build to replace the previous one. |
Do you think it is possible to host the latest stable and the latest pre-release version? It would help debugging problems... |
This will make it so releases are also hosted as a pacman repository using GitHub Pages.
I did one build using it. To test this, add the following to your
/etc/pacman.conf
:Then you can download the packages using the following command:
I've added instructions specific for the ChimeraOS group to the README.
Before merging this PR, make sure to set the GitHub Pages source to GitHub Actions in the settings of the GitHub repo like in the image below:
It would be possible to add signing later, but since right now packages are just downloaded using wget, I don't think that will be needed. Especially since we're using https here, so a man in the middle attack would be very hard to do anyway.