:wq!

Is he ok?

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.

The lemmy user in the database needs superuser privilages. Add superuser to the lemmy account, drop the database, and then recreate it.

sudo -iu postgres psql -c "ALTER USER lemmy WITH SUPERUSER;"
sudo -iu postgres psql -c "DROP DATABASE lemmy;"
sudo -iu postgres psql -c "CREATE DATABASE lemmy WITH OWNER lemmy;"

Edit: they may have fixed this but I’m not sure what version it’s in. Let me know if that doesn’t work. https://github.com/LemmyNet/lemmy/pull/3002

Heads up you need to enable hotlinking in cloudflare. Other instances get images directly from yours. For example your profile picture is loaded directly from your server.

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.

If you use a local postfix relay it should queue messages and retry to send on failures.

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.

I tested images with the default setup for pict-rs and it removed all exit data. Having said that you should test the instance your using with sample pictures and check for yourself. It’s possible to disable that feature if an operator really wants it on.

I think that’s the websocket connection that they are working on removing in the next version. Should make the loading issues on mobile go away.

It’s tough because you don’t want them to be technically inept in this day and age. There is also peer pressure amongst friends and a certain social status that for better or worse matters to them.

It’s a balance between unrestricted access and a reasonable amount. We keep them busy enough that it’s never a question. They really only come out on long car rides and trips. We don’t use them in the home at all.

Very rarely at a restaurant, only when it’s large family affair at a place we won’t normally go. I used to judge people throwing screens in front of kids at restaurants but let me tell you it’s better than chasing them around. They get a treat, the screen, for behaving and I get to enjoy a nice meal.

I’ve never paid Reddit a dime but I’m going to signup for at least whatever gold costs. Fuck spez.

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 picked up a black friday deal from mxroute for $15/year. Unlimited domains and 300 email/hour. I have it setup as the relay for my internal postfix/dovecot setup. It also hosts one email account so if I mess up my own configuration I can still do email.

Looks like their current deal is a $5/year for 1 domain https://account.mxroute.com/order/micro You could still set that one domain up as a relay.

At home I have a Proxmox cluster consisting of two Dell R340 and one Intel NUC. There are 25 VM’s across all three machines. They do various development duties along with home assistant, plex, and Blue Iris. The rack lives in a closet under the stairs and I have fiber ran to my office. We did a massive renovation when we purchased so I wired the entire house since the walls were all opened. Average power draw is around 480 watts.

Here is a picture of the rack back when it was all R330. Those have since been sold and upgraded to R340. I added vents during the renovation. Inlet temps stay around the house ambient, and exhaust is about 20 degrees F hotter. I cover the front with additional sound baffles to better route fresh air and control noise. Its pretty much silent outside the closet.

This is the patch panel. I have perimeter cameras all the way around the house plus more than enough wifi access points. Each room also got 2x ethernet on each side, 4x total. My office has got 6x ethernet plus 4x fiber and a 2-inch conduit to pull whatever else I can think of later.

I use Grafana and custom-made scripts for monitoring and alerting. Most of the infrastructure is automated with scripts. One of these days Ill learn Ansible but I really enjoying just figuring it all out. This isn’t my job I just do it for fun. Here is the dashboard I run on one of my desk monitors.

I run my hobby websites, and my Lemmy instance, in the colo but its primary purpose is to be an offsite backup. Proxmox backup server performs best on SSD hence the large array. I also do a lot of travel for work so that’s my remote dev machine too. I run my own mail servers with some small VPSs acting as SMTP and IMAP bouncers to internal servers at home and in the colo working in parallel. HA proxy does the bouncing for high availability and dovecot and postfix do the heavy lifting with solr providing lighting fast search. I do use a third party for outbound mail for better deliverability.

Dell R350 - Colo Proxmox

• Intel E-2388G processor
• 128gb 3200 ECC ram
• Dell H755p raid
• 8x Crucial MX500 4TB in raid 6
• Samsung 990 2TB NVMe

Dell R340 - Proxmox Node 0

• Intel E-2278G processor
• 128gb 3200 ECC ram. Despite the spec sheets and irdrac saying these only support 64gb they run 128gb just fine.
• Ultrastar DC SN640 7.68TB NVMe
• Dell H810 Flash with LSI firmware. HBA for SC200 disk shelves.
• Mellanox CX354A @ 40GbE

Dell R340 - Proxmox Node 1

• Intel i3-9100T processor
• 64gb 2400T ECC ram
• Ultrastar DC SN640 7.68TB NVMe
• Intel X520-DA2 @ 2x 10gbe

Intel 7th Gen Nuc - Proxmox Node 2

• Intel i5-7260U processor
• 32gb 2400 ram
• Ultrastar DC SN640 7.68TB NVMe

This is mounted to the wall under my desk in a silent case. I use Verizon Wireless home internet as a backup and this server is the router. My entire closet rack can go offline and Ill still have internet access.

Dell R730 - GPU

• 2x Intel E5-2696 V4 processor
• 512gb 2400T ECC ram
• SanDisk Skyhawk 3.84TB NVMe
• 2x Nvidia P100 16gb GPU
• Intel X520-DA2 @ 2x 10gbe
• This one stays powered off when not in use. I built it to play around with tensorflow and AI but haven’t had much time.

Dell SC200 Disk Shelf 1

• 12x WD 8TB 5400 rpm shucked drives
• Single z2 pool
• Roughly 74 usable TB
• Cold backups of the primary array. Only powered on once a month to sync.

Dell SC200 Disk Shelf 2

• 12x HGST 10tb SAS drives
• 2x z2 pools
• Roughly 72 usable TB
• Primary storage array. Sitting at about 70% utilized so its time to upgrade.