Replies: 1 comment
-
I think it would be a good idea to make the update/install process for Linux users more user friendly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Every Bisq release is packaged in different formats. For linux, we use
deb
andrpm
. These are provided as release artefacts, so linux users have to manually download, verify and install them on every release.One way to streamline this is to publish the linux binaries in
deb
andrpm
linux repos (see #4563).I looked into this and found that it's quite simple to create a
deb
orrpm
repo. All that's needed is a webserver to serve static content1. The bisq binary would then be copied there and repo metadata generated.As a test, I tried to publish such a repo using GitHub Pages. However, our release binary is >100MB so it needs to be pushed via Git LFS. Unfortunately, GitHub Pages doesn't support Git LFS (see git-lfs/git-lfs#791).
Could this be done from another Bisq server, which is under our (i.e. a bonded role's) control? Like a dedicated subdomain, for example https://deb.bisq.network (cc bisq-network/roles#18)?
Or would it be better to try to host this on a 3rd party 2?
Footnotes
A static webserver, 3-400 MB of space and some way to new binaries (ssh, ftp, etc) during a release. ↩
https://www.jfrog.com/confluence/display/JFROG/Debian+Repositories ↩
Beta Was this translation helpful? Give feedback.
All reactions