lbrynet refactorings #72
No reviewers
Labels
No labels
Accepted
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
In Review
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
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-docker#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lbrynet-start.sh"
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?
Various lbrynet container additions:
Are you certain that 127.0.0.1 isn't going to just bind it to the internal container processes IP only? Otherwise, this is great work thanks again!
@Leopere Yes thank you I changed it to 0.0.0.0
@ -39,10 +39,11 @@ RUN apt-get update && \
FROM dependencies as compile
ARG REPO=https://github.com/lbryio/lbry.git
This will be wonderfully useful, however, lbry's release schema isn't via branches as much as it is via tagged releases. So if this can be adjusted to pull tags automagically it would be extra useful.
@ -6,2 +7,3 @@
ADD https://lbry.io/get/lbrynet.linux.zip /lbrynet/lbrynet.linux.zip
ARG VERSION=latest
RUN URL=$(curl -s https://api.github.com/repos/lbryio/lbry/releases/$(if [ "${VERSION}" = 'latest' ]; then echo "latest"; else echo "tags/${VERSION}"; fi) | grep browser_download_url | grep lbrynet-linux.zip | cut -d'"' -f4) && echo $URL && curl -L -o /lbrynet.linux.zip $URL
Same as above down here.
@ -10,3 +10,3 @@
else
`$@`
bash -c "$*"
fi
I'm curious about the thoughts behind this change.
I would be wary of 127.0.0.1 as that should perspectively only accept connections from inside of the container itself and not on the external.
yes my mistake, fixed.
@ -39,10 +39,11 @@ RUN apt-get update && \
FROM dependencies as compile
ARG REPO=https://github.com/lbryio/lbry.git
This case will work with branches and tags.
git checkout v0.37.0rc5
works for instance.@ -10,3 +10,3 @@
else
`$@`
bash -c "$*"
fi
$@
was not accepting additional arguments beyond the first one. "$*" captures the entire argument string. You showed me the page https://eklitzke.org/bash-$%2A-and-$@ and he outlines the case for "$*" translating to "$1 $2 $3 ..." which is exactly what we want to pass tobash -c
@ -39,10 +39,11 @@ RUN apt-get update && \
FROM dependencies as compile
ARG REPO=https://github.com/lbryio/lbry.git
I wonder if we can find a way to do new tag releases with magic.