Improving lbrycrd binary install #93
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#93
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I am working on documentation for installs of the main pieces of the LBRY system. I use the following environment for testing:
Lubuntu 16.04.3 LTS - Ubuntu derived, takes half the disk space due to graphics diet.
apt update/apt upgrade so it's current.
tmux - share screens and log activity to text file, so I can watch a developer do an install.
When I download and unzip the lbrycrd binaries for Linux that part works fine, but there is no README to explain what to do, no example config, and no lbrycrdd.service file for systemd.
This is what we did for the daemon's configuration:
And I didn't record the contents of /etc/systemd/system/lbrycrdd.service and I've since recycled the VPS where we did that, so I do not have a copy of that text handy.
To be clear, this is a request for DEB packaging for Linux deployment? And we should host those on our own PPA somewhere? Would Snap packaging be okay (instead of DEB)?
The readme was recently updated to include a config example and how to run lbrycrdd. I think that might be enough to close this issue.
closed per Tom's comment