BTW those aren't actual PHP files, they're most likely HTML. PHP is what they're called when they're code on the live website but the tools that make these archives only copy a dump of the webpages. It should have renamed them but apparently didn't. You'll have to do the renaming instead in order to open them. It's also extremely likely that the links between the forum pages are also ending in .php and won't work (the tool was also supposed to have converted the links inside the files).
GolemancerVekk
joined 2 years ago
httrack.com is one option to mirror the site for your personal use. Unfortunately there's no way to tell how long it would take and how large it would end up being.
I wonder also about the legality of then uploading the site to another domain
That would most likely be a breach of copyright.
What filesystem does the original HDD use?
Not understanding how you will set up the vdev without losing data.
I'm confused, I haven't used TrueNAS before, can it only work with one pool at a time or what? Why would it lose data?
Can't OP connect the two new drives as a separate RAIDz1 pool, copy the data, then wipe the original drive/pool?
- Get a cheap VPS.
- Get a domain name and point its
Arecord to the IP of the VPS. - Set up a VPN tunnel between the VPS and your home server. You can use Tailscale or wg-easy. You don't need to worry about CGNAT because you're establishing the VPN by going out of your server (either through Tailscale or to the VPS IP with wireguard).
- Port-forward 443 on the VPS public IP through the tunnel to a reverse proxy running on the home server (NPM, Caddy, Traefik etc.)
- Get a Let's Encrypt wildcard TLS certificate for *.yourdomain.tld.
- Set up the reverse proxy to use the TLS certificate for immich.yourdomain.tld and point it at your immich container.
I use Cloudflare tunnels because they are a good way of exposing sites to the internet without exposing my IP
What difference does that make? I only ever heard one realistic reason for hiding your IP, which was a guy living in a suburban neighborhood with static IPs where the IP indicated his house almost exactly.
If you have a dynamic IP it will get recycled. If you get a static IP it will eventually get mapped to your precise location, Google & other big data spend a lot of time doing exactly that.
or opening ports [...] or other attacks
If your services are accessible from the internet they are accessible... doesn't matter that you don't open ports in your local LAN, there's still an ingress pathway, and encrypting the tunnel doesn't mean your apps can't get hacked.
I don’t have to worry as much about DDoS
How many DDoS's have you been through? Lol. CF will drop your tunnel like a hot potato if you were ever targeted by a DDoS. If you think your $0/month plan is getting the same DDoS protection as the paid accounts you're being super naive. Let me translate this page for you: your DDoS mitigation for $0/mo amounts to "basically nothing". Any real mitigation starts with the $200/mo plan.
I'm partial to the DIY PC option because it allows far more flexibility. If you can swing the space for the larger box IMO it's the best way to go.
Some things to keep in mind when speccing the box:
- Some PCIe slots can come in extremely handy down the line. There's an amazing variety of expansion cards that can save your butt when you decide to do something you haven't foreseen.
- Consider how many HDDs you'd like to have. This will determine the case size as well as how many SATA connectors you need to get.
- Get an Intel CPU at least gen6 because they have GPU with hardware transcoding built-in.
- Get at least one M.2 slot, to be able to install the OS on a NVMe SSD and not take up a SATA connector. Read the motherboard specs though, some of them disable a SATA connector anyway if you use the M.2 slots in a certain way.
- You can run a server on RAM as low as 4 GB. You actually don't need very high RAM if you don't intend to run VMs or ZFS.
Are you familiar with any Linux distro in particular? I would strongly recommend using Docker rather than native regardless of distro.
Here's an idea, check out ytdl-sub: https://github.com/jmbannon/ytdl-sub
You can set it to track a YouTube channel and it will download videos and set up nice collections for you in Jellyfin, which you'll never lose again and can watch without ads.
Please take such advice with a large grain of salt. OP's experience is very much not the norm. Especially for more complex apps like Jellyfin or Nextcloud, it's almost guaranteed you'll break them if you just update blindly.
You do not need RAID. But if I were you I'd get a second HDD and back up files to it once a month. You don't need to keep this 2nd HDD running, just bring it out for backups. There are lots of nice backup solutions on Linux you can use, I can recommend BorgBackup – it takes snapshots and it does compression, deduplication and optionally encryption.
I think it really depends on what you intend to do with it... Many answers here will mention what they use but not why.
In my case I want to have various services installed in docker containers, and I have the skills to manage Linux in console. A very simple solution for me was to use a rock-solid, established Linux distro on the host (Debian stable) with Docker sourced from its official apt repo. It's clean, it's simple, it's reliable, it's easy to reinstall if it explodes.
Why containers (as opposed to directly on the host)? I've done both over several years and I've come to consider the container approach cleaner. (I mention this because I've seen people wondering why even bother with containers.) It's a nice sweet spot in-between dumping everything on the host and a fully reproducible environment like nixOS or Ansible. I get the ability to reproduce a service perfectly thanks to docker compose; I get to separate persistent data very cleanly thanks to container:host mapping of dirs and files; I get to do flexible networking solutions because containers can be seen as individual "machines" and I can juggle their interfaces and ports around freely; I get some extra security from the container isolation; it's less complicated than using VMs etc.