docker: Lbrynet as a container #149

Closed

Leopere wants to merge 273 commits from lbry-as-a-container into master

Leopere commented

2018-05-28 01:44:25 +02:00

(Migrated from github.com)

Documentation

Added some basic documentation to docker/README.md it can be used elsewhere but at some point if we add other things which end up justifying that the end user run a git clone and then docker-compose up -d from inside of the git repo of lbrycrd we can let them store data in docker/data/ with some fancy git ignoring.

Docker Compose

For the sake of getting people launched asap I've included a basic docker-compose.yml file which can launch the app with docker-compose up -d then commands can be run using docker exec CONTAINERNAME lbrynet-cli commands

.gitlab-ci.yml

This is for CI/CD prebuild and deploy if we want to use GitLab for building these containers rather than the hub.docker.com route. Currently, this is just configured to show what it would look like with my repositories.

Dockerfile

Currently, the dockerfile is very basic and just installs the daemon into the containers $PATH for easy execution then it stores the daemons content in /app/ as that is defined as the unprivileged daemon processes home directory.

Commit size

https://en.wikipedia.org/wiki/Atomic_commit#Atomic_commit_convention the version I was working from in my topic branch was hugely out of date so rather than carrying over all of the commits I just added everything fresh I know that it's lazy but this code doesn't meddle with anyone's stuff so it seemed like it should be okay to do it this way.

Maintainance

This container should be reasonably future proof for now as I've defined all non-ephemeral blobs to reside in the /app/ directory inside of the container which can be updated at a later time just fine.

The configuration will be added using a shell script in the future which can be optionally included. The goal is to allow configuration using environment variables in the docker-compose.yml file which will be the officially supported launch method as it's the least maintenance method.

## Documentation Added some basic documentation to docker/README.md it can be used elsewhere but at some point if we add other things which end up justifying that the end user run a `git clone` and then `docker-compose up -d` from inside of the git repo of lbrycrd we can let them store data in docker/data/ with some fancy git ignoring. ## Docker Compose For the sake of getting people launched asap I've included a basic docker-compose.yml file which can launch the app with `docker-compose up -d` then commands can be run using `docker exec CONTAINERNAME lbrynet-cli commands` ## .gitlab-ci.yml This is for CI/CD prebuild and deploy if we want to use GitLab for building these containers rather than the hub.docker.com route. Currently, this is just configured to show what it would look like with my repositories. ## Dockerfile Currently, the dockerfile is very basic and just installs the daemon into the containers $PATH for easy execution then it stores the daemons content in /app/ as that is defined as the unprivileged daemon processes home directory. ## Commit size https://en.wikipedia.org/wiki/Atomic_commit#Atomic_commit_convention the version I was working from in my topic branch was hugely out of date so rather than carrying over all of the commits I just added everything fresh I know that it's lazy but this code doesn't meddle with anyone's stuff so it seemed like it should be okay to do it this way. ## Maintainance This container should be reasonably future proof for now as I've defined all non-ephemeral blobs to reside in the /app/ directory inside of the container which can be updated at a later time just fine. The configuration will be added using a shell script in the future which can be optionally included. The goal is to allow configuration using environment variables in the docker-compose.yml file which will be the officially supported launch method as it's the least maintenance method.

Leopere commented

2018-05-28 02:00:01 +02:00

(Migrated from github.com)

Ignore this I added these files to the wrong repo for the PR. I've got an annoying setup so that I can do CI/CD with GitLab as I don't have access to any of the LBRY testing mechanisms like Travis.

Pull request closed

This pull request cannot be reopened because the branch was deleted.

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#149

No description provided.