he lost me at "I've bought a domain on Google Domains"
Self hosting in 2023
201–210 of 307 posts
Re: Self hosting in 2023
#202Earlier quoted context omitted.
Kernel care is apparently free for the raspberry Pi https://tuxcare.com/patch-raspberry-pi-systems-without-a-reb... Also I think you can use Ubuntu PRO on the pi, which includes Livepatch.
I'm only seeing a long and posing as an article telling me to sign up for a 7 day trial.
> KernelCare understands that hobbyists need protection too, so we offer this benefit to Raspberry Pi enthusiasts free of cost. The currently supported chips are the BCM2711 (Pi 4) and BCM2837 (Pi 3 and later models of the Pi 2), and we offer support for Ubuntu Focal Fossa for 64-bit ARM platform, and soon support for Debian and Raspbian.
Re: Self hosting in 2023
#203If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…
What is the worst case scenario for security on your network, in the above self hosted setup ?
Re: Self hosting in 2023
#204Earlier quoted context omitted.
It can be as difficult or hard as you make it. If you want just nginx serving static files or k3s with multiple services on a tiny cluster is up to you. The benefit for me is that I can be confident that my data is mine. But mainly because it's fun and great for learning. In my experience it's not much harder than navigating the AWS interface, where I often feel very lost. But of course YMMV. > There is no real priva…
What privacy is gained by self hosting a static site rather than using anything else?
One (or more) less service(s) to give your e-mail. If you want to see usage you can just check the page loads instead of having to add analytics because github pages doesn't share any stats. The visitors get the same benefits because it's one less site behind cloudflare. The big providers can't figure out (and possibly sell) your interests based on the sites you host.
Not my reason to self host (static) but more a welcome side effect.
Re: Self hosting in 2023
#205If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…
Honestly a basic VPS is a lot easier to me than running a physical home server. Dirt cheap, never have to worry about power failures, dust, heat, home ISP being shitty, etc.
I run vpcs and homeserver
I avoid all the DNS and port forwarding issues by having a wireguard Server in obenbsd that also runs unbound, so i habe some internal DNS entrys for stuff i host at home linke Cale der and co tacts
Re: Self hosting in 2023
#206> a cheap UPS to keep it running in case of power outage (which happened once in the past year, so it might be a bit overkill). I don't think this is overkill, I think it's necessary. A UPS is pretty cheap compared to the completely-uncontrollable chance of losing power in the middle of working on something . Sure, there's autosave and most things are relatively recoverable, but this is just such a cheap investment (…
Have the feeling this is definitely more of an American problem. I'm from a European country and the last time I have had any sort of power outage is more then 10 years ago (can't even remember it to be honest). Even with the current surge in prices the production and transmission system is still reliable as ever.
Re: Self hosting in 2023
#207Is there a good guide that explains all the in and outs of building a server?
Re: Self hosting in 2023
#208If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…
Honestly a basic VPS is a lot easier to me than running a physical home server. Dirt cheap, never have to worry about power failures, dust, heat, home ISP being shitty, etc.
I have only a static website with not too much content or traffic, I even use the free oracle VPS that they offer. It took some while to get the hang of ingress rules and opening ports in their interface in addition to the CLI but now it works and I’m not paying anything. Out of curiosity: where do you get your VPS?
Re: Self hosting in 2023
#209I see a baby flying out of the bathtub here. You can still use NextJS - just get it to prerender the entire site statically. Then you get the plus sides of using NextJS, but can take your static ZIP file of files to any host you like, or self host. You then get, for example, an HTML file, with all the elements ready on page load, which can be 'rehydrated' when React kicks in for deep functionality and interactivity.
Can you explain this please ? I have a netxjs based discussion forum in development. Is it as straightforward as issuing a command to pre-render and then the site re-hydrates via Apollo on it's own ?
Forums are dynamic so no you can't fully static deploy that
Re: Self hosting in 2023
#210I see a baby flying out of the bathtub here. You can still use NextJS - just get it to prerender the entire site statically. Then you get the plus sides of using NextJS, but can take your static ZIP file of files to any host you like, or self host. You then get, for example, an HTML file, with all the elements ready on page load, which can be 'rehydrated' when React kicks in for deep functionality and interactivity.
Can you explain this please ? I have a netxjs based discussion forum in development. Is it as straightforward as issuing a command to pre-render and then the site re-hydrates via Apollo on it's own ?
I have not used apollo but to explain:
Say you have a useEffect that calls an API: maybe firebase or parse. That useEffect only gets run on the client. For the server side render: it runs the react code based on the initial props and takes that first rendering and creates the static html from that. When that static html is run on the browser it will run react and subsequent renders can update the dom.