• 1 Post
  • 26 Comments
Joined 10 months ago
cake
Cake day: June 6th, 2025

help-circle
  • For someone who just wants a sane editor, I don’t need not care for seeing up my own config or keeping up to date with neovim plugins. Like you mention vim.pack, but why should I add a user need to keep up with which plugins has the latest congenital features?

    The advantage of a distro is that somebody else sets up sane defaults, keeps plugins up to date and uses the latest cool plugins. All without me needing to spend any time reading documentation and trying to set up a new plugin. And it still allows me full customization, where it’s easy to add or disable plugins.

    Essentially all a distro does is move the starting point from a very basic text editor to a fairly advanced text editor. So to me it feels like a no brainier to use as my base, because somebody with 10x my experience with vim will be better at designing a work flow with vim than I will.






  • Many people talking about using subdomains, but that’s only really a thing if you actually have a domain. Just last year the domain .internal was reserved for internal use, so that’s what I’ve set up all my domains to use. E.g. https://pihole.internal/, https://proxmox.internal/.

    To make this work I use pihole’s local dns records to rewrite any *.internal domain to point to my reverse proxy Caddy’s ip.

    As for the certificates, I created my own CA, which I install on all my and my family’s devices. Then, for each new url I set up, I create a new certificate and sign it with my CA certificate, then have my reverse proxy serve it.

    This all sounds like a lot of work, and it is, but using OPNsense for both reverse proxy and certificates makes it well integrated and certificates are trivial to renew. With that said, if you have your own domain, go the let’s encrypt subdomain route instead imo. It saves you a lot of manual labor with setting up your CA on every device you own and creating new certificates for each site.