• 0 Posts
  • 73 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle


  • All of your issues can be solved by a backup. My host went out of business. I set up a new server, pulled my backups, and was up and running in less than an hour.

    I’d recommend docker compose. Each service gets its own folder inside your docker folder. All volumes are a folder in the services folder. Each night, run a script that stops all of them, starts duplicati, backs up to a remote server or webdav share or whatever, and then starts them back up again. If you want to be extra safe, back up to two locations. It’s not that complicated if it’s just your own services.


  • There’s no forgetting where I have something hosted. If I ssh to service.domain.tld I’m on the right server. My services are all in docker compose. All in a ~/docker/service folder, that contains all the volumes for the service. If there’s anything that needed doing, like setting up a docker network or adding a user in the cli, I have a readme file in the service’s root directory. If I need to remember literally anything about the server or service, there’s an appropriately named text file in the directory I would be in when I need to remember it.

    If you just want a diagram or something, there are plenty of services online that will generate one in ASCII for you so you can make yourself a nice “network topology” readme to drop in your servers’ home directory.


  • Landlords are familiar with utility install people and how unpredictable they can be. Even if they get mad, this will put the blame squarely on someone else so it’s probably a good option for you. “I dunno why he put it there. You know how utility guys are. It’s the only place he’d put my hookup.”


  • constantokra@lemmy.onetoSelfhosted@lemmy.worldNetworking Dilemma
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    5 months ago

    Second this. Landlords don’t want their stuff screwed up by inexperienced tenants’ diy projects, and they don’t want to pay for something they think it’s unnecessary. I’d get an estimate for a pro to do it (could be a guy off Craigslist or whatever, just someone who does this for a living) and then just ask the landlord if they’d be alright with you paying to get it done. They’ll probably want to know exactly what they’re going to do, and they’ll likely say yes, especially since you say they already have coax running through the house.





  • I have a champ from the 90s, and the tools are all great, but I mostly find myself needing pliers and a blade. It’s great for.outdoors though.

    I actually just finished cleaning up a Swiss army knife I found in a house I was cleaning out. I had the scales off, because it was super nasty, and they were solid in the back, so i’m guessing it’s oldish, which might explain why I can’t figure out which model it is. Everything sizeable I find has the hook, and mine, unfortunately, does not.

    You seem to know a lot about them. Any idea what it is, or where I could look to figure it out?








  • I’m getting a bit concerned with logseq. It’s just kind of backwards to have a web app packaged as a desktop/android app that can be hosted on a server, but you can’t store your files there. I get that they want to monetize sync, but they’re kind of bending over backwards here to not have what’s inherently a pretty reasonable feature in a web based app, and it makes me concerned about what they’re going to do with the project in the future.




  • Everyone else is telling you to stay local, which is great advice, as far as it goes. But you said you want to host your website publicly available, so i’d recommend getting a cheap vps and starting there. It’s not on your network, so if you screw up with security, worst case is you start again from scratch. I’d recommend the cheapest virmach VM you can get, with Debian or Ubuntu, if you like snaps.

    First things first, set up ssh with key based logins, with a passphrase on a non standard port (doesn’t provide security, but it will keep your logs from getting innundated immediately). Install UFW, and block all incoming traffic, allow all outgoing traffic, and limit traffic to your ssh port. Install docker and add your user to the docker group. Start learning how to use docker, compose, and as your first container, set up duplicati to back up your docker directory (including all your volumes, which I would store as folders inside your docker directory) somewhere else. I’d set it up to run every evening after you go to bed, and i’d also set a cron script to bring down all your containers before you back up, then bring them back up. Just in case.