The normal and recommended Proxmox file structure is what you’ve after running rm -rf /. Just move to Incus (LXD) and be done with it.

Incus provides a unified experience to deal with both LXC containers and VMs. If you’re running a modern version of Proxmox then you’re already running LXC containers so why not move to Incus that is made by the same people? Why keep dragging all of the Proxmox overhead and potencial issues?

Incus is free can be installed on any clean Debian system with little to no overhead and on the release of Debian 13 it will be included on the repositories. Another interesting advantage of Incus is that you can move containers and VMs between hosts with different base kernels and Linux distros.

Read more here: https://tadeubento.com/2024/replace-proxmox-with-incus-lxd/

Sorry here’s a better tutorial. I might write one, it is interesting that they all suck in different ways.

https://starbeamrainbowlabs.com/blog/article.php?article=posts%2F237-WebDav-Nginx-Setup.html

The folder is defined by the “root” directive. Like with any other nginx setup.

Cam be anything you want, just have to install nginx and configure it: https://medium.com/learn-or-die/build-a-webdav-server-with-nginx-8660a7a7311

If I connect it to my computer using a SATA to USB adapter instead of directly to the computer’s SATA, can it somehow affect the result of this scan?

It depends on how much power the disk requires and how much power the USB port can deliver. Also note that USB-A is the worst connector out there when it comes to mechanical reliability - it only takes a finger on the plug to screw whatever data transfer is going on.

For external disks (both 2.5 and 3.5") I’ve a bunch of this powered USB disk enclosures. They’ve a good chip, are made of metal and a USB-B 3 port. You can connect those to any USB-A device and you’ll know that only one side might fail… if you’ve USB-C a cable like this tends to be more reliable.

Another good option, if you’ve USB-C and you want something more portable is to get a USB-C disk enclosure as those will be able to deliver more power and be more reliable.

PS: avoid whatever garbage Orico is selling, Inateck is much better.

Yeah, but aren’t others as well? My ideia was to run them on an isolated VLAN without Internet access. What brand would you recommend instead.

Following your advice I found a video for another model and it seems complete, even motion detection was available on the WebUI. I’m assuming you’re on the exact model I was looking at and it doesn’t have that feature am I right?

Besides your take anything else against them?

IP cameras allow you to access the device via web gui where you can view and configure the camera for your needs. Once I’ve set them up I only ever access them again through frigate.

Thanks for the answer. What kind of management do they provide on their WebUI? Can the camera be 100% operated using the WebUI, standalone without anything else? I’m just trying to understand how dependent on external software (be it their apps, cloud or HA) the cameras are.

Are you using an Amcrest IP4M-1041B, can you have a look at this? https://lemmy.world/post/16883143. Thank you.

Are you using an Amcrest IP4M-1041B, can you have a look at this? https://lemmy.world/post/16883143. Thank you.

Are you using an Amcrest IP4M-1041B, can you have a look at this? https://lemmy.world/post/16883143. Thank you.

How do I know all of this? Well I happen to work with WordPress professionally as the lead developer for an agency where I manage literally hundreds of WordPress sites and host all of them myself on servers I manage for them (not shared hosting reselling).

I used to have the same role and before that I managed a shared hosting provider. At that job the majority of websites hosted there were WordPress and customers would pay us to develop or fix stuff sometimes.

The vast majority of those “extensions” (plugins) are horribly made and are security nightmares,

Yes, this is true and a problem, but at the same time the WordPress ecosystem, as you know, gets shit done.

I also had some experiences with PrestaShop/Magento and they are even worse than WordPress. You still have the performance issues, the 3rd party poorly developed themes and plugins and a convoluted API.

WooCommerce powers 38% of the online stores out there…

WordPress’s data structure is not properly suited for an e-commerce site

To be fair WordPress’ data structure is not properly suited for anything, not even posts and pages, let alone block structures and whatever but the truth is that it works and delivers results. Same goes for WooCommerce, if you don’t want to be hostage of Shopify and your objective actually selling shit instead of spending all your time developing store software then WooCommerce is the way to go.

WooCommerce also has an extensive extension list, integrations with all the payment providers out there and it’s easy to get help / support be it free or paid.

and it’s a resource hog.

Did you ever they Magento or PrestaShop? Doesn’t seem like you did as those are store-first solutions and they’re all slower and more of a resource hog than WP can ever be.

Wordpress + Woocomerce.

Well I see your problem, but you’re going to have a bad time without a screen. Maybe you can get something second hand / cheap or even ask a friend to borrow one for a few days?

https://github.com/philpagel/debian-headless

It is possible but I wouldn’t do it. Too much effort for too little result.

Just plug your main monitor / keyboard into the server, run the setup and don’t install a DE. Afterwards login, enable SSH, unplug the monitor and do whatever you need over SSH.

Let’s face it, you’ll have to do this procedure once every xyz years, there’s no point in complicating this stuff. Also depending on your motherboard you may or may not be able to boot into the installer without a screen / keyboard attached. Another option is to install the OS in another computer and the move the hard drive to the target server - this is all fine until you run into UEFI security or another detail and it doesn’t boot your OS.

@[email protected] ,

Step 1: get a cheap VPS, or even a free one (https://www.oracle.com/cloud/free/)

Step 2: If you’ve a static IP at home great, if you don’t get a dynamic DNS from https://freedns.afraid.org/ or https://www.duckdns.org/

Step 3: Install nginx on the VPS and configure it as reverse proxy to your home address. Something like this:

server {
    listen 80;
    server_name example.org; # your real domain name you want people to use to access your website
    location / {
        proxy_pass http://home-dynamic-dns.freeprovider... # replace with your home server IP or Dynamic DNS.
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect off;
    }
}

Step 4: Point your A record of example.org to your VPS.

Step 5: there’s a potential security issue with this option: https://nginx.org/en/docs/http/ngx_http_realip_module.html#set_real_ip_from and to get around this you can do the following on the home server nginx config:

http {
(...)
        real_ip_header    X-Real-IP;
        set_real_ip_from  x.x.x.x; # Replace with the VPS IP address.
}

This will make sure only the VPS is allowed to override the real IP of the client.

Step 6: Once your setup works you may increase your security by using SSL / disabling plain HTTP setup letsencrypt in both servers to get valid SSL certificates for real domain and the dynamic DNS one.

Proceed to disable plain text / HTTP traffic. To do this simply remove the entire server { listen 80 section on both servers. You should replace them with server { listen 443 ssl; so it listens only for HTTPs traffic.

Step 7: set your home router to allow incoming traffic in port 443 and forward it into the home server;

Step 8: set the home server’s firewall to only accept traffic coming from outside the LAN subnet on port 443 and if it comes from the VPS IP. Drop everything else.

Another alternative to this it to setup a Wireguard tunnel between your home server and the VPS and have the reverse proxy send the traffic through that tunnel (change proxy_pass to the IP of the home server inside the tunnel like proxy_pass http://10.0.0.2). This has two advantages: 1) you don’t need to setup SSL at your home server as all the traffic will flow encrypted over the tunnel and 2) will not require to open a local port for incoming traffic on the home network… however it also has two drawbacks: you’ll need a better VPS because WG requires extra processing power and 2) your home server will have to keep the tunnel connected and working however it will fail. Frankly I wouldn’t bother to setup the tunnel as your home server will only accept traffic from the VPS IP so you won’t gain much there in terms of security.

The technology has “been there” for a while, it’s trivial do setup what you’re asking for, the issue is that games have anti cheat engines that will get triggered by the virtualization and ban you.

Total e-waste and a power draw (almost constant 95W). Even a Raspberry Pi 4 Model B can beat it to oblivion:

https://browser.geekbench.com/v6/cpu/compare/6390478?baseline=5583060

Total e-waste and a power draw. Even a Raspberry Pi 4 Model B can beat it to oblivion:

https://browser.geekbench.com/v6/cpu/compare/6390478?baseline=5583060