Appliance connectors: https://en.wikipedia.org/wiki/IEC_60320
North American connectors: https://en.wikipedia.org/wiki/NEMA_connector
Worldwide industrial connectors: https://en.wikipedia.org/wiki/IEC_60309
Worldwide standard connectors: https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets

From google images it looks like this PSU has an IEC C20 male connector on it meaning you would need an IEC C19 end on your cable. C19/20 is a higher amperage version of C13/14 which is what could be considered standard on a normal consumer PSU. Google C19 to whatever plug your 220v outlet needs and you should find the appropriate cable.

I’ve found the solution to this problem is to not have friends.

Oh no I hope i can get a refund.

It allows for different hashes on the front end so individual users can still delete their upload. The sled database maps front end to back end hashes. At least this is what I read from the developer in their matrix chat room.

Pict-rs uses a database to match the uri hash to the file name on disk or object store. This allows for deduplication. It always needs to sit between storage and requests. I have my instance setup to use a separate CDN domain and caching servers to reduce load in my instance. One day soon I hope to get a write done on how to do it.

Scroll down to do a complete reload doesnt work on my iphone but other than that it’s great.

It won’t work well. Other instances make assumptions about paths as it’s standardized. For example they don’t store the full pictrs path, just the ID. It’s assumed the path is /pictrs/image. You would have to set 301 redirects. Other instances may link directly to your root uri when making links back to you. The api requests are also likely going to your root uri.

The front end can do whatever you want. Just change the paths typescript files before you compile as those also use root urls.

I have my instance setup to use a CDN and separate URL for all static content including pictrs. I have a script that modifies the front end while compiling to accomplish this. I use 301 redirects to fix all the assumed paths and requests from other instances.

Proxmox and shell scripts. I have everything automated from base install to updates.

All the VMs are Debian which install with a custom seed file. Each VM has a config script that will completely setup all users, ip tables, software, mounts, etc. SSL certs are updated on one machine with acme.sh and then pushed out as necessary.

One of these days I’ll get into docker but half the fun is making it all work. I need some time to properly set it up and learn how to configure it securely.

I tried pasting a kbin magazine link into the search box but nothing ever showed up in my communities. I would love to be wrong but I’m not sure we can subscribe to their native groups.