Major Refactor WIP #61
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#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refactor"
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?
This refactor PR is a work in progress, @EnigmaCurry, and I are cleaning up this repository now that we've committed ourselves to just doing all of the container orchestration from within this repository rather than getting in the way of others within the LBRY Inc organization.
Depends on updates to this issue referenced https://github.com/lbryio/lbry-docker/issues/36#issuecomment-486881385
this needs to be squashed something fierce.
The refactor needs documentation updates and a twice over to ensure that there are no dangling references and a final squash & rebase.
I've read through all of the documentation to verify things are copacetic, and I feel that things are relatively concise and functional no dangling URL or tag references I've set up the following repositories to build the docker files within this repository.
There will need to be a huge overhaul of documentation but that's out of scope for this refactor.
Closes #35 and closes #22
Closes #49
Closes #36