might host a shared library of ebooks since I live with lefties, but what else could I do? i'm gonna run it on an old laptop and it has a mic and webcam, so there are some creative possibilities here
might host a shared library of ebooks since I live with lefties, but what else could I do? i'm gonna run it on an old laptop and it has a mic and webcam, so there are some creative possibilities here
i've already set up apache as a reverse proxy (still just an internal server though) - is there a reason to use traefik or caddy instead? i haven't made the jump to docker and probably won't yet because i want to learn the basics a bit better first
Never played with caddy, AFAIK its just a golang alternative to apache like nginx.
Traefiks whole deal is its optimized to serve systems like docker, vagrant or kubernetes. Its configuration is minimal, while the services it routes to tell traefik how to route it. This is would be an absurd design if it was for services like docker, vagrant, etc.
If you're not playing with docker yet then I wouldn't bother with traefik. Docker's not always the right tool but its good if you want a service encapsulated to a git repo as much as possible. Eg: I have all my config files tracked in git and I can deploy it to any platform without disrupting the rest of the system or having anything else in the system interfere with it. Can't say much to basics of it other than focus on understanding Dockerfiles over docker commands. And use docker-compose over docker commands, but know that what commands compose items map back to.