Create Docker Caddy File #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update to include vertigo/ancient pictures.
Update dockerfile to hopefully use variables at runtime? Update Caddyfile Update dockerfile to expose ports. Update to include vertigo/ancient pictures. Update Caddyfile and README. Update readme.
PhlexPlexico
force-pushed
the
docker-caddy
branch
from
1721191 to
f397f83
Compare
Added DockerfileLightCaddy & Fixed the Caddyfile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new type of Dockerfile in order to setup the front end with Caddy. The positives of this is that it gives HTTPS automatically, setup is fairly simple, and you shouldn't need a webserver in front of it now in order to take care of HTTPS or forwarding. Docker processes have been updated in the README accordingly.