• 15 Posts
  • 377 Comments
Joined 1 year ago
cake
Cake day: December 28th, 2023

help-circle
  • N0x0n@lemmy.mltoSelfhosted@lemmy.worldTesting vs Prod
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 hour ago

    Production is my testing lab, but only in my homelab ! I guess I don’t care to perfectly secure my services (really dumb and easy passwords, no 2fa, not hiding plain sight passwords…) because I’m not directly exposing them to the web and accessing them externally via Wireguard ! That’s really bad practice though, but any time soon will probably clean up that mess, but right now I can’t, I have to cook some eggs…

    There are 2 things though I actually do have some more complex workflow:

    • Rather complex incremental automated backup script for my docker container volumes, databases, config files, compose files.

    • Self-hosted mini-CA to access all my services via a nice .lab domain and get rid of that pesky warning on my devices.

    I always do some tests if my backups are working on a VM on my personal desktop computer, because no backup means that all those years of tinkering for nothing… This will bring up some nasty depression…

    Edit: If have a rather small homelab, everything on an old laptop, still quite happy with the result and works as expected.



  • Just create a wildcard domain certificate !

    I access all my services in my lan through https://servicename.home.lab/ I just had to add the rootCA certificat (actually the intermediate certificate) into my trust store on every device. That’s what they actually do, just in automated way !

    Never had an issue to access my services with my self-signed certs, neither on Android, iOS, windows, linux ! Everything served from my server via my reverse proxy of choice (Treafik).

    However I do remember that there was something of importance to make my Android device accept the certificate (something in certificate itself and the extension).

    If you’re interested I can send you the snipped of a book to fully host your own CA :). It’s a great read and easy to follow !















  • Debian as a server is fine and probably the best ! However as a daily drive OS I don’t think it’s the best choice.

    I have always seen Debian as server distro and that’s probably what they meant ?

    I have debian as my server distro since the beginning of my Linux journey (NEVER failed me !) However I can’t see how Debian as daily drive is a good idea. Sure they try to catch up with testing repo for those who wan’t a more up to date distro, but it’s seems harder to keep up when something breaks along the way.

    That’s where Arch and derivatives shine, if something goes wrong it’s fixed in a few days.


  • I think what happens to me is that I completely lack discipline about structure and will often decide to re-organize things.

    Haha ! Same boat here !

    One slightly more stable system I’ve had for my own code is to use the Issues tracker as a sort of documentation storage system.

    That’s a very nice tip, thank you ! That’s something I will explore.

    Thanks for sharing. :) I hope you don’t mind me saying this but it’s nice to see commits like “Just a commit test”. I also have these as part of learning git.

    Yeah that’s a bit embarrassing 🫠 ! Was playing around with some script to convert Obsidian markdown links to GitHub flavored markdown. Because a comment is necessary to push the commit I have always no idea what to put in there xDD.

    Sorry I couldn’t help you out more and hope you will find a workflow that works for you ! 👍



  • Is there any specific reason to keep the docs in the wiki section? Vs markdown documents right in the wiki itself?

    I don’t know sorry :/ I do use a document but only because I want more control over the TOC (Table of content), which is a bit strange in the wiki itself, but that’s just personal taste !

    I’m not a Dev so take everything I say with a grain of salt, but what I would do is add a comment in the code to specify the change and link to your documentation file for more details (if needed). That’s probably one of the advantage of having your documentation not in the wiki page.

    This would keep your code page clean while having proper documtation in the same repo ! However, I have never seen any project doing it like that (for a good reason probably?).

    Here is my codeberg documentation repo about anime encoding in av1. It’s probably not what you’re looking for but maybe this can give you any idea or see if this could fit your workflow?