LBRYCommunity/lbry-docker
1
0
Fork 0
Code Issues 2 Pull requests 2 Projects Releases 1 Packages Wiki Activity
This repository will be for Dockerfiles for the various LBRY packages.
209 commits 10 branches 3 tags 2.7 MiB
CSS 53.2%
Shell 35.6%
Smarty 7.7%
JavaScript 2.7%
HTML 0.8%
Find a file
Leopere 09c295a103 Adding compose.override and a root docker-compose to gitignore 
The idea is that default settings should be left alone in the app
specific compose files but if the end user wants a custom one at the root
they can have a fully custom one that cherrypicks apps and settings.
2018-10-16 15:29:23 -04:00
chainquery Updated against a multi stage strategy 2018-10-16 03:28:03 -04:00
docs default git issue template 2018-10-06 18:38:23 -04:00
lbrycrd Updated Labels 2018-10-16 03:30:13 -04:00
lbrynet-daemon Updated Labels 2018-10-16 03:30:13 -04:00
reflector.go Updated Labels 2018-10-16 03:30:13 -04:00
traefik MAINTAINER is deprecated in Dockerfile. COPY is preferred over ADD in Dockerfile if additional functonality of ADD is not being used. Improved Shebang lines in many files. 2018-10-14 18:00:06 +05:30
www.spee.ch Updated Labels 2018-10-16 03:30:13 -04:00
.gitignore Adding compose.override and a root docker-compose to gitignore 2018-10-16 15:29:23 -04:00
CONTRIBUTING.md Adding CONTRIBUTING.md notes 2018-10-16 14:49:47 -04:00
LICENSE Started on Reflector.go 2018-10-08 16:53:51 -04:00
README.md Some ultra basic documentation for now 2018-10-06 20:02:13 -04:00

README.md

lbry-Docker

Currently supported platforms

X64 cpu architecture

More will be added on request and over time

Documentation is WIP

Currently this repository is a WIP and is under heavy construction, use at your own risk make sure you keep regular backups of your wallets. Your milage may vary as how far this will work for you be sure to file good and concise issues if you plan to and keep in mind we're allergic to regressions when filing PR's.

Debugpaste

I'll be including a function to get a self destructing debugpaste of your LBRY appliances logs you'll be able to execute something similar to the following in all containers to export raw logs to a paste service where you can then either modify them removing sensitive data or just take that URL and create a new issue after you (Use Issue Search) to make sure there isn't already an open thread for your issue.

Example debugpaste

cd chainquery/
docker-compose exec chainquery debugpaste
https://haste.nixc.us/ocatumatozaq.nginx

You can then take output given in the response from the debugpaste command and put that into your github issue.