Are their instructions for installing locally for development. I would like to contribute to the project. Many thanks
There is currently no documentation on setting up local development for gSender, though we would like to add it at some point in the future.
Happy to see that you’d like to contribute to making gSender even better 
Hello,
I’ve been using gSender for a few years with my FluidNC based CNC, and it’s overall been wonderful. I’d like to contribute improvements to gSender that I’ve been working on, and wanted to know the best way to do that.
I opened up a pull request to fix a small macOS but I’ve encountered. I’d also very much like to contribute some more improvements around the macro system, and a bugfix relating to how gSender can occasionally miss a FluidNC (grbl) status response.
Please let me know how best to proceed. It’s nice that gSender is developed in the open, but it looks like there’s limited resources for external contribution.
I just forked the repo and was able to build the packages.
I was already thinking of creating a README.md for developers because it took me some time to figure out how to build the Pi package for the custom code changes I needed for my ATC project. I couldn’t find any steps in the repository for creating this package, so I was wondering if it was built outside of the Action runner and manually added to each release.
So far, I’ve managed to build a Pi package and even set up my own self-hosted Action runner to automate the build process during release creation and add the assets. The runner is running on my Mac Mini M1.
1 Like