You could port forward.
However, I’d buy a digital droplet for 10 USD a month, point the A record of the domain to that and then use Caddy to implement SSL.
Caddy can run a http server or reverse proxy something on localhost.
You could port forward.
However, I’d buy a digital droplet for 10 USD a month, point the A record of the domain to that and then use Caddy to implement SSL.
Caddy can run a http server or reverse proxy something on localhost.
Openrc is used by alpine and gentoo. They both work great.
Runit used by void is also fine.
If you can figure out gentoo it’s not a bad OS but compiling can be slow. You’ll learn a lot though. Checkout oddlama/gentoo-installer


Tail scale already has a bunch of limitations for unpaid users but it’s only an extra step to set up wireguard in a container.


Honestly, I’ve had little trouble. The Gentoo Wiki and Void Handbook have a lot of overlap with OpenRC and musl, respectively.
While the documentation could be improved, the overall experience has been quite good and very stable.


I’m not trying to be unhelpful. My advice would be to steer into the terminal. Bite the bullet. I use arch and alpine for my servers but Fedora would be fine (but SELinux can be a pain with bund mounts)
Probably just go with Fedora with btrfs for snaps. It has lots of support and is a common choice for servers


Wireguard (or tailscale) would be best here.


Set up wireguard in a docker container and then forward the port to wireguard, the default container on docker hub is fairly straightforward and you can always ask me for help if you need :).
However, If you are using ipv4, you need to make sure that you’re not behind a CG-NAT (If you think you might be, call your ISP and tell them you have security cameras that need to get out or something like that).
You could also try tailscale which is built using wireguard with nat-busting features and a bit easier to configure (I dont personally use it as wireguard is sufficient for me).
After that Caddy + DNSMasq will simply allow you to map different URLs to IP addresses
dnsmasq
my_computer -> 192.168.1.64http://dokuwiki.my_computer -> http://my_computer:8080http://dokuwiki.192.168.1.64 -> http://192.168.1.64:8080Caddy and DNSmasq are superfluous, if you’ve got a good memory or bookmarks, you don’t really need them.
VPN back into home is a lot more important. You definitely do not want to be forwarding ports to services you are running, because if you don’t know what you’re doing this could pose a network security risk.
Use the VPN as the entry point, as it’s secure. I also recommend running the VPN in a docker / podman container on an old laptop dedicated just to that, simply to keep it as isolated as you can.
Down the line you could also look into VLan If your router supports that.
I personally would not bother with SSL If you’re just going to be providing access to trusted users who already have access to your home network.
If you are looking to host things, just pay for a digital droplet for $7 a month, It’s much simpler, You still get to configure everything but you don’t expose your network to a security risk.


If you’re just going to VPN in to your home network, I’ve found caddy to be the simplest.
I think this combined with the solution provided in this comment Will be the most robust approach and solve all your problems.
That’s what I would do
Mobile offline sync is a lost cause. The dev environment, even on Android, is so hostile you’ll never get a good experience.
Joplin comes close, but it’s still extremely unreliable and I’ve had many dropped notes. It also takes hours to sync a large corpus.
I wrote my own web app using Axum and flask that I use. Check out dokuwiki as well.


Oh good to know.
It used to be awful but I’m glad to hear it’s improving.


Maybe snapdrop?
When I was obsd I did FTP and rsync for everything. Syncthing had dinner performance issues for me.
Maybe Seafile but I had a bad time with that.


From memory MTP is pretty flaky and quite slow.
ADB push is pretty good but at that stage rsync is just as easy.
Put SSH in the phone and you can do it all from the computer too.


To be fair, wireguard is pretty painless.


Absolutely that’s what the internet was made for!
But family photos keep a bit more secure, Particularly if it’s syncing directly from your phone, I take a lot of explicit photos of my wife, but also code that I’m writing on my computer, or the kids playing, etc.
Dokuwiki + wireguard would be different but satisfy since if those needs, try it out of you have time.


Quartz or mkdocs
I suppose the problem that I had with Media Wiki is that every update would break extensions. Particularly mathjax and semantic media Wiki. I too amusing it with Docker which helps a lot.
So docuicki has a recent pages view which is really good and lists the user that made the edit. That’s what we use for a feed. There’s also an RSS plug-in that will display other feeds which is kind of nice if you want to discuss other articles.
We create Journal pages that link out to pages for events etc. The events are also linked to from a start page. We display the backlinks using the footer plugin.
Whilst it’s a bit different from social media in that there is no feed, it’s really nice that it provides, like a database of our family’s life in history.
We even have pages for cars and repair logs, computers and updates, everything. The struct plugin is amazing And you can always pop it open in SqliteBrowser too!
I’ve tried a couple of things and I just keep coming back to dokuwiki because it’s the best compromise.
No, I don’t. And that’s going to be one of our big differences here. Everyone in my family is tech literate and knows at least a little bit of programming.
I would strongly suggest dokuwiki. It’s like having a forever Journal of Family affairs and I really like it. I know it’s not quite the social media aesthetic but in my experience I found it to be the thing that stuck.
I would argue against Mediawiki though. It may be more user-friendly for some family members, but the maintenance becomes a nuisance And pulling things out of the database involves half a dozen joins.
Even though dokuwiki editing is text in markup, It’s not a hard concept to grasp and the simplicity makes it feel more tangible which may be appreciated by older family members.
See also duckdb and clickhouse for OLAP of course.