-
Notifications
You must be signed in to change notification settings - Fork 8
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
Various Releases for rChore #8
Comments
I could write a AUR (Arch User Repository) script and also try to work on the Bash Script. |
Sure @pspiagicw, thanks for taking this up! If possible, please look into the possibility of automatically releasing it via the GitHub Releaser CI |
The AUR script is ready! You can find at https://github.com/pspiagicw/rchore |
For the debian package , I got this link https://www.internalpointers.com/post/build-binary-deb-package-practical-guide I will try to build a DEB file and test ,if you are comfortable with it. For the bash script , Linux and Mac OS is easy , but I am getting stuck at binary for Windows. |
That's great! Could you please open a PR for the same, and ensure its automated for every release?
Sure, you can definitely give it a try!
The bash script for cURL is already in the works, so that's completely fine. Feel free to work on deb and aur scripts and send a PR for the same! |
DEB file is ready , it is in the same repository as AUR script. For automation we only have to change the version number in both scripts. I will look into GitHub Actions and try to automate that. |
As a method of cross-platform/OS distribution, I would suggest to publish a Docker container. Any needed external files could be mounted, but env vars would suffice for API keys. Thus, you can create an alias for a command such as: alias rchore='docker run --rm -it -e TERM DarthBenro008/rchore' If |
@pataquets, this seems like a nice idea, but we might have a problem. rchore currently stores a physical db at |
What about docker volumes ? They persist throughout sessions ? |
As @pspiagicw mentioned DB and other files can be mounted. Even RW or RO, which would give more sense to #22 as for splitting data storage in different files concerns. I'm also not very familiar with what is stored in the DB and which items are rebuildable and which not, such as options (which might make sense in a |
This seems like a viable solution to give a shot at, but i think it would be better if #22 is solved and closed first so that we can approach the Dockerizing solution |
Need to figure out robust binary distribution mechanisms for rChore
The following would be nice:
Optional:
The text was updated successfully, but these errors were encountered: