constantokra

joined 1 year ago
[–] [email protected] 2 points 8 months ago

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.

[–] [email protected] 2 points 8 months ago (4 children)

Is there a way to embed portions of one page into another page, such that if you edit it on either the change shows up on both, like in logseq?

The documentation is actually pretty good, but i've not been able to find that feature, if it exists. That's probably the last thing keeping me on logseq.

[–] [email protected] 7 points 8 months ago

The way they handle port forwarding is particulalry good, as compared with pia, that assigns a random port every time you bring up a connection, so you have to have a script to update your port in your client.

[–] [email protected] 0 points 8 months ago

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.

[–] [email protected] 1 points 8 months ago (1 children)

I've previously had a problem with my server becoming unresponsive when running immich. It's been a while, but I remember there being some kind of memory leak having to do with immich. It was in their GitHub issues and everything. On my system it would take about a day and a half and then ssh, along with everything else, would become unresponsive. Rebooting would fix it for a day and a half. I stopped running immich and it hasn't happened since. I suppose you could try using a cron job to restart immich periodically and see if that resolves your problem.

[–] [email protected] 1 points 9 months ago (1 children)

Is there a specific benefit to that over something like a security key with a keypad, or even just a passphrase?

[–] [email protected] 2 points 9 months ago

I've read that best practice is to do a database dump, in addition to backing up all the data files. It's my understanding that there's a slight chance of corrupting something in the database if you don't stop the service first, since something could be changed while you're doing your backup.

The easiest solution for me, as well as for being able to just restore my files and start the service again somewhere else, is to stop, backup, and restart. It's down for less than 5 minutes while i'm asleep. If I expected better uptime than that I wouldn't be trying to self host.

[–] [email protected] 3 points 9 months ago (2 children)

FYI, if you run vaultwarden using docker compose with your data volume as a folder, all you have to do is bring it down for like 1minute, make a backup of the folders, and bring it back up. I use a cron script to do this nightly. When my vps host went out of business, I restored my docker folder to a new vps and was up and running again in a couple minutes. Also, you could easily restore it to a virtual machine, if you like. Docker with compose is extremely portable.

[–] [email protected] 2 points 9 months ago (1 children)

Sorry, I've not used a redhat based distro in at least 20 years, so you're going to have to get that info from someone else. I'd assume that's the one though, and I doubt you need to go looking for something better. It is what it is.

[–] [email protected] 13 points 9 months ago (5 children)

Download a wireguard client file and run it as a systemd service. It'll come up on boot and you won't ever have to think about it. The only reason to bother with the GUI is if you want to have graphical control of what server you connect to. Their wireguard config generator on their website gives you the ability to set a geographic area for your wireguard client file, so it's not like you have to select only one server if you go that route either.

[–] [email protected] 2 points 9 months ago

That's pretty neat. I might start doing that, just for kicks.

[–] [email protected] 6 points 9 months ago

Now that's the kind of paranoid I was hoping to see in here. High five, pal.

view more: ‹ prev next ›