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

  • captcha [any]
    ·
    4 years ago
    • a git user with cgit as their shell and their home directory as your repo list.
    • use the above git user for a central password-store repo.
    • traefik as a reverse proxy for various docker images. Use docker-compose to trivially test out new software that's complicated to install (like nextcloud, WordPress etc). The traefik container is always running and as you spin up new docker-compose stacks they register themselves with traefik. Traefik will also handle https. You can also track your entire stack with git this way.
    • aria2c in json-rpc mode. Use transdroid or aria2ng as interfaces.
    • git-annex can be useful for tracking your data horde.
    • syncthing as an alternative to Dropbox/gdrive. Its fairly unstable unless you have an always on server.
    • Spinoza [any]
      ·
      4 years ago

      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

      • captcha [any]
        ·
        4 years ago

        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.