Integrate Traefik (2.0) to our stack #23
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm sorry, this commit contains a compilation of what I've added to
our Plex & co setup over the last two years, without commiting
anything. So... it actually contains multiple changes :/
I thought these changes would be beneficial to our pet project
Essentially, they are meant to make setup and maintainance easier than
ever before, which I think is essential if we want more people to enjoy
this stuff :D
Here's the list:
for everyone who just wants a working setup on a fresh new server.
Using this integrated traefik to route traffic to containers that
aren't part of this stack is still possible of course.
As a result, using custom networks is not necessary any more, it
simplifies our
docker-compose.yaml
file a bit.of its APIs. Docker annotations had to be rewritten.
to CLI flags. Removing this "moving part" that had to be edited and
could be commited by accident (with our credentials in it...) will
make "git pulls" much much easier... and therefore encourage
contributions I hope :)
suggests should be put in the user's
.bashrc/.zshrc
(usingdocker-compose
commands is therefore way simpler, no need toconstantly use Ctrl-R any more).
on the UI on first setup.
typing URLs in the navigation bar. As a result, we now use the
tlsChallenge (instead of http challenge): it doesn't require the
server to listen on port 80. Only 443 is used during the ACME
challenge.
manual uploads from other machines (I used that to RSync music from my
multiple computers, as well as my Pictures, which I think is a rather
valuable feature).