This was it for me now, installed paperless-xng, set it up to scan my email folders, copied all random PDFs from my “organized” tax folder and scanned the rest.
Too bad I just happen to have that Brother printer/scanner without SMB or FTP support. So I need to go through the process of scanning on my computer first, then uploading.
Of course. My setup now is a Proxmox server + a NAS. What I’m planning to do is to install a service for this to Proxmox, then have the files synced over NFS to the NAS, which then backs them up every night to Backblaze. And of course I need to have the paper copies too, but to be able to search, tag and archive the documents is great when you need to remember a thing X that was mentioned in a paper I got back in 2014.
It just doesn’t feel right to have multiple postgres databases running, if every other service uses the one in the network. Having already monitoring, disk space and backups set…
Installed it because of this thread to my homelab today. I never really managed my phone images in any way, never uploaded them anywhere. This was the first time. About 5 gigabytes of images and videos were synced to my NAS in a few minutes, now I can search them and all that. It’s a pretty cool setup, although the installation is a bit tricky if you don’t go to the path they give you. I run a Postgres server in Proxmox, and you have to install just the right version of pgvecto.rs for the system to work.
Browsing the issues I was able to figure out what went wrong, and after downgrading, no issues.
Cloudflare R2 is the cheapest here, it’s free for some gigabytes and egress is free too.
To be honest, I’d just disable image uploads…
As said in the thread, you need some kind of tunnel that stays up and doesn’t need to be fixed if the internet goes down.
Wireguard, or if wanting super easy setup, Tailscale version of Wireguard is great for this. Now you have a private IP address in your VPN network to your home server, that stays up and answers to HTTP. Next thing you need is a cheap VPS somewhere with a public IP address. When that is running, and is in the Wireguard network so you can access your home server from the VPS, you need a Nginx proxy in the public server. Either do it by hand, or use a service such as the Nginx Proxy Manager to handle the proxy setup.
How it basically works is you register a domain name (A, CNAME) to the public VPS service, then with Nginx you setup that anything coming in to the domain X should be proxied to the VPN IP address Y and port Z. Now you can add HTTPS to this domain and get a Let’s Encrypt certificate for it. You can, again, do this manually with Nginx, or let Nginx Proxy Manager handle it for you.
Finally. Stay safe. If you really open services to public internet from your home, be very sure to have all the latest updates and use strong passwords in all of them. Additionally, you can use the home services directly from the Wireguard/Tailscale network by accessing them using the private IP addresses. Your computer should just be in the same network with them.
I’m running it in my homelab for projects I do not (yet) push anywhere public, and projects containing private items such as ssh keys. It is snappy and has a ton of features. I can imagine when the federation support works, one can set up their own git forge and contribute more easily to other forges no matter what software they run.
And, to be honest, that is already how git works if you use the email workflow. Here we just get a web based flow with federated issues and pull requests. But if email is enough for you, you can have a full federation with email and git.
Or AMD 6000 series if power draw and quietness are important. Add Proxmox with ZFS to run all your apps in containers or VMs.
You can script this with nix quite easily without needing a UI. For many this is a big plus.
You could also get the cheapest VPS, put all your services at home together with the VPS to the same Tailscale network and install a service such as Nginx Proxy Manager to terminate the HTTP traffic and proxy your home services.
It’s also a good choice. What I like about opnSense is how it’s basically just a distribution you update from the shell, feels more like a real operating system compared to OpenWRT, which is usually flashed to the router.
What I did is I bought a cheap small PC with an Intel chip (i5), some RAM and an SSD. You can find these with more than one NIC pretty easily from Amazon, and they are just normal computers: only small and quiet. Then go with a virtualization platform such as Proxmox, and to that, install opnSense as the router distribution and use the rest of the processing power to run everything else in your house in virtual machines: Home Assistant, media server, you name it… Just search Amazon with something like “router pc” and you get a long list of machines below and over 200 euros that are more than enough for your home. Computers like this one.
The great thing about opnSense is how it gets regular updates. And when you use a normal PC as your router, you run the latest FreeBSD kernel and get updates basically as long as opnSense is developed.
You probably also want a Wi-Fi. These boxes usually miss it, and even when they have a Wi-Fi card, opnSense is not really great for setting wireless networks. I just bought a few APs from Ubiquiti. They are a bit on the expensive side, but I just don’t need to touch these things after setting them up and the network never fails on me. There are also much cheaper APs in the market, just get anything that fits to your budget and plug it to the router.
At home:
Remote:
I’ve been digging into the settings of this printer and, sadly the only send it can do is as a fax… It’s the entry model, been serving us for years very nicely. It even connects to the internet, but misses features such as email, smb or ftp. For me this looks like something an open source firmware could fix. It has enough processing power to possibly run a lightweight Linux distribution, so installing one that would enable modern communication protocols doesn’t seem impossible.