If you wind a 2 or 3 layer pancake coil the size of the platter out of 12 or 14AWG magnet wire and dump a couple kJ through it from a capacitor bank, the platter will launch into the air. Don’t try it indoors unless you want a platter embedded in the ceiling.
That’s not too easy methinks. You get kvm vm-s though gui/shell/api with proxmox, but no docker (they use lxc). Unless you set up a podman or similar inside it.
Other than that I’d say go with a xen (xcp-ng). Proxmox or esxi host, and spin up a vm as docker host.
I ditched docker in my latest setup, just running 2 machines in a proxmox cluster. I like lxc - as it’s got the footprint of docker and behaves like a vm
I used to make clocks with the platters and give them to friends and family. Michael’s used to sell inexpensive clock mechanisms that looked really cool against the platter background. I haven’t seen them lately, but I’m sure someone sells them online.
The older IDE drives with the 5.25" platters and smaller ones make great wind chimes. The laptop ones are a bit .ore fragile due to thinner material. Years ago, we used to do this with a few of them.
By exposed you basically mean that I can reach them using my browser? I can reach my homeassistant web ui on port 8123 but when I try to forward to that port with the servers IP I get a 400 Bad Request error. I’m not sure if this is caused by nginx being unable to forward or by homeassistant not accepting the connection somehow
Someone below mentioned adding some more IPs to the trusted_proxies list so I tried that as well without result. The IP I used for the reverse-proxy is the IP listed in portainer under the network for the proxy container. Just to reiterate, the container is running on a different device than homeassistant (technically same device but different VM but that shouldn’t make a difference).
<span style="color:#63a35c;">http</span><span style="color:#323232;">:
</span><span style="color:#323232;"> </span><span style="color:#63a35c;">use_x_forwarded_for</span><span style="color:#323232;">: </span><span style="color:#0086b3;">true
</span><span style="color:#323232;"> </span><span style="color:#63a35c;">trusted_proxies</span><span style="color:#323232;">:
</span><span style="color:#323232;"> - </span><span style="color:#0086b3;">192.168.208.2 </span><span style="font-style:italic;color:#969896;"># IP of reverse-proxy in its network
</span><span style="color:#323232;"> - </span><span style="color:#183691;">192.168.208.0/20 </span><span style="font-style:italic;color:#969896;"># Subnet of proxy docker network
</span><span style="color:#323232;"> - </span><span style="color:#0086b3;">192.168.1.103 </span><span style="font-style:italic;color:#969896;"># HA IP
</span>
My NPM window looks the same as yours. Im not sure mate, I would try disabling firewall just to see is that the problem. Im not expert in that area and nothing else comes to my mind sorry. Im also running everything under one host
If you have any kind of firewall on your network, you might make sure it’s not blocking that port with a rule. Here’s a couple screenshots from my setup in case that helps.
Thanks for the configuration example. Unfortunately it doesn’t seem to work for me. I’ve replied to someone above with screenshots of what my configuration now looks like. The base_url option you use there wasn’t available to me because it apparently has been deprecated and replaced with internal_url and external_url.
I use old platters to hang around our chicken houses. The idea is to distract hawks and eagles with the sparkle as they spin in the breeze… Probably doesn’t work, but I like the shiny disks :)
I took a look and didn’t see domains mentioned until you go to the members login page. It’s not even on the sign up page.
So, uh, maybe go take a look at the link you’re posting. And also don’t write “pay for what you use” when someone is asking about buying a domain if you don’t want people to think you misunderstood the question
I would stick with namecheap (for now) and pony up for a multi year registration. If in 5 or 10 years they are jacking the price up then you can use another registrars cheap port option to get a discount. I did this recently between godaddy and namecheap. I had one domain left with godaddy that I have owned for over probably a couple of decades at this point and they were seriously jacking the rate up on me, I ported it to namecheap for a massive discount.
selfhosted
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.