Auto Update Functionality for Paper #27
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been really impressed with this server implementation, and I was looking for a way to contribute. I've developed a tool that automates the process of checking for updates on the https://papermc.io/downloads website.
This tool utilizes GitHub Actions to scrape the website for updates, and upon finding any, it automatically updates the Docker files and the README in the repository.
Two GitHub "secrets" need to be configured: GIT_USER_EMAIL and GIT_USER_NAME.
This implementation does rely on web scraping, and currently, the method to identify the version hinges on a class name that is not ideally named. Given the nature of web scraping, it's possible that changes to the PaperMC download page could break this functionality.
It might be necessary to periodically check the action logs to ensure it continues to function properly (if the website's structure changes). I did my best to validate that the version is correctly formatted before the files are ever touched.
I've encountered some challenges with scheduling jobs in GitHub Actions in the past, but I've found that triggering the action via a simple API call is a reliable workaround. I hope this contribution proves to be helpful. Thank you for building and maintaining this project!