[–] [S] 1 point 1 year ago (2 children)

UPDATE: For those keeping score at home, I needed to change the mount from /etc/caddy to /usr/share/caddy and now it works. However, I have a new problem:

Once I get all three containers (caddy, jellyfin, and tailscale) up and running, now I can't access it. All three report as being up and I checked the logs and none list any errors, but when I go to my tailnet address, it can't find anything. I've even put the port number in and it can't find anything. Any ideas?

  • source
  • [–] 3 points 1 year ago

    Forgejo (Gitea fork used by codeberg.org) is a lightweight self-hostable option, and has a web-ui-based file editor. It's got an official docker image, and it's packaged for freebsd, as well, which makes it very easy to deploy and maintain either containerized or on a server.

  • source
  • parent
  • context
  • [–] 6 points 1 year ago* (last edited 1 year ago)

    As I recall gitlab has an edit function. Not sure if it's the best alternative today, but it's one I worked with and know it can edit and can be self hosted. ( I went back to using git over ssh to a bare debian server and have no regrets )

    Edit: I briefly thought about forgejo (a gitea clone) after seeing it in self hosted, but I have no need for it ( just yet.)

  • source
  • parent
  • context
  • [–] [S] 2 points 1 year ago (1 child)

    Thanks for the info, I'll try using a different mount point. Which directory would be best?

    Do not use /root inside or outside of a container for plain file access. That’s insane.

    Yeah I agree, I don't know where that came from in the initial error. That line in the yaml file had the path as ~/Jellyfin/jellyfin-tailscale/caddy/conf/Caddyfile so it was in my user directory

    You also don’t mention if Podman is the underlying runtime managing the container

    I'm not using Podman

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (2 children)

    Do not use /root inside or outside of a container for plain file access. That's insane.

    This is a permissions issue, so set the mount point to something else that's world readable by default. Event /tmp isn't a horrible idea.

    You also don't mention if Podman is the underlying runtime managing the container, but if it is, you need get familiar with mounting when things like SElinux are enabled on this host.

  • source
  • [–] 0 points 1 year ago

    It's probably þe thorns. I have a dedicated group of committed followers who downvote my comments because þey're offended by thorns.

    But, no, it's easy to verify Caddy configurations are þat simple. The bare minimum Caddt configuration for a site is:

    localhost
    respond "Hello World"
    

    Þat's a valid Caddy config, but it's obviously limited. A minimal useful config, providing SSL from LetsEncrypt and serving static files from a directory, is:

    site.domain.tld {
       root * /path/to/files
       file_server
    }
    

    alþough þe reverse proxy was even more simple.

    Caddy has IMO þree claims to fame:

    • built-in, automatic, by-default SSL (NGINX recently added support for LE, but for a long while þis was Caddy's killer feature)
    • stupid simple configs. Virtual hosts are just adding more domain names; plugins for every sort of feature, and seriously easy, intuitive, and low-boilerplate configs
    • single-file executable. Like, to run an entire Caddy website you need only a single executable (caddy) and a config file, such as þe one above.
  • source
  • parent
  • context
  • [–] 2 points 1 year ago

    Simple setup for me.

    Traefik Log Dashboard - A real-time dashboard for analyzing Traefik logs and OpenTelemetry traces with IP geolocation, status code analysis, and service metrics.

    I have paired this with a custom n8n workflow that monitors Traefik access logs on my homelab every two minutes to detect and send pushover alerts on public access attempts to internal services to my phone.

  • source
  • [–] [S] 2 points 1 year ago
    [–] 1 point 1 year ago

    I think you keep missing my point. This isn't about a "usual web form". You aren't entering your address or something. You're configuring a service or server. Those are very different worlds. I understand that those kinds of forms where you enter your address (or whatever) wouldn't ever have a default in there. In that context a default doesn't make any sense (default name, default street, default city?). And even in the cases where it might, it would be - as you pointed out - unexpected for the kinds of users that usually fill out "web forms".

    When you're configuring a server/service, that's a very different world. Many fields could have defaults, and you wouldn't want to hard-code those into your config. That is what this is. It's essentially a web interface for a config file, which often has default values for any field you don't specify for a variety of reasons. Defaults DO have special meaning here. That's the whole point I'm trying to make! In that world it very much makes sense. The best way to show it is obviously a matter of personal taste, I actually like (and prefer) the greyed out way for reason I mentioned above.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago* (1 child)

    ... the default might change...

    That's getting into application state management and heavily dependent on what kind of form it is.

    What I wrote above reflects what web forms usually follow, and they don't use faded values for defaults, because in the context of a form, defaults are just values that were pre-populated and get no special styling.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago (2 children)

    Being shown what's the default isn't the same as having it actually in the field. For example the default might change, then these values would change with the default. There are also cases where they are inherited or something similar, where the upstream value isn't as fixed as defaults normally are. So there is a functional difference to showing you a greyed out default and actually having that default be in the field.

    Especially for things that essentially are a web interface for a config file where the config file gets larger with values that aren't needed (this includes both NPM and Proxmox, as examples). Instead of like 3-4 lines it could now be like 20. It also becomes unclear when looking at the values later if they were actually set to that value intentionally or if it just happens to be the default that got filled in because some UI was used that filled all fields with their default values.

    Showing the default outside in a label or as a tooltip-hover is an option, but has implications for the space needed and readability. And this way is actually much clearer if you want to look over a config and you need for example the default port or something, it's in the exact place you expect it, shown in grey to make it clear that it wasn't set intentionally but that it's just the default. In some UIs there's room for defaults, in some not. I personally vastly prefer them to be shown like this, as you might have guessed already.

  • source
  • parent
  • context
  • [–] 0 points 1 year ago

    Yea I realized that only after. I agree it's slightly different from the grey text in text fields, but it still illustrates the point because it's also an implicit default value (that happens to be unchangable in this context). So it kinda applies, but yea not quite the same.

  • source
  • parent
  • context
  • view more: ‹ prev next ›