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

Does git repo correspond to the download version? Reproducible build? #115

Open
knyipab opened this issue Oct 19, 2024 · 2 comments
Open

Comments

@knyipab
Copy link

knyipab commented Oct 19, 2024

https://github.com/pfalstad/circuitjs1 was updated 8 month ago, while https://www.falstad.com/circuit/offline/ seems to be updated 2 months ago. Does they correspond? What is the exact source to produce the current build of https://www.falstad.com/circuit/offline/?

Would you ever consider to the build more reproducible? Like nowadays we can use Github Actions, tags to do a release build, making the workflow more automated and transparent. Also, using tags to indicate version should definitely help it to be packaged in Linux distros. Currently only AUR package your software (https://aur.archlinux.org/packages/circuitjs1-web-bin) but that is a 2021 version.

Such a nice software should be promoted and be more easily available to broader audience.

@pfalstad
Copy link
Owner

Whoops, I forgot to do a push. I just did it.

I will look into your other comments. Using tags would be a good idea.

@knyipab
Copy link
Author

knyipab commented Oct 20, 2024

Thanks.

When tagging versions, you may do it along with the Github release feature and a workflow to automate the building and uploading the release binaries. This is an example from stirling-tools (a pdf webapp): https://github.com/Stirling-Tools/Stirling-PDF/blob/main/.github/workflows/releaseArtifacts.yml. Logs and records will be available on their actions page so it could be transparent and more reproducible. You can even program it to upload to your own website for each release. If that is the case, you will want to make use of repo secrets to store some passcodes.

You may make a workflow to build the app for every push. It's completely free for public repo. Example from stirling-tools: https://github.com/Stirling-Tools/Stirling-PDF/blob/main/.github/workflows/build.yml

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

No branches or pull requests

2 participants