ch00f

I’m running funkwhale in docker. This consists of a half dozen docker containers one of which is postgres.

To run a backup, funkwhale suggests shutting down all of the containers and then docker compose running pg_dump on the postgres container. Presumably this is to copy the database when nobody is accessing it.

For some reason when I do this, I get an error like:

pg_dump: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
	Is the server running locally and accepting connections on that socket?

It would seem that postgres isn’t running. I see the same error with other commands such as psql.

If I fully boot the container and then try exec-ing the command, it works fine.

So it would seem that the run command isn’t fully booting the instance before running the command? What’s going on here?

The container is built from postgres:15-alpine

I'm moving my music library to a funkwhale instance, but I don't want to have to keep two copies of every song (one imported to Funkwhale, one on a local drive).

It looks like Funkwhale will let you download a single song at a time from your own library , but there doesn't seem to be a similar button for albums or playlists.

The files themselves are obfuscated in whatever indexing system it uses, so there's nothing to be done there.

Anyone know how this is possible?

Just got Whisper working on my local server so I can send it audio files via curl POST request and receive transcribed text.

Are there any keyboard plugins for phones that could be directed to a personal server running Whisper to replace functions like Siri/Google assistant voice transcription?

I'm hosting a few services using docker. For something like an openstreetmap tileserver, I'd like it to remain on my SSD because high speed improves performance, and the directory is unlikely to grow and fill the drive.

For other services like NextCloud, speed isn't as important as storage size, so I might want it on a larger HDD raid.

I know it's trivial to move the volumes directory to wherever, but can I move some volumes to one directory and some volumes to another?

You always hear about gun sales in the US, but you never hear about what happens to the guns at the end of their lifecycle. I assume guns wear out eventually, and I assume you can't just chuck them in the garbage when they do. What happens to them?

Upgrading a server for the first time in 10 years, so I’m a little out of the loop. I was surprised to find that the RAM I bought didn’t fit.

This is my first time dabbling in ECC RAM, so I figured there was some minor detail I missed when purchasing, but I eventually came across the data sheet for this stick, and the dimensions given don’t match the measurements I’m making. The tip of the caliper should be in the middle of the notch at 68.1mm.

What’s more is that the dimensions in the data sheet seem to match the dimensions on my motherboard. What’s going on here?

[SOLVED] I and Kingston are morons. I ordered RDIMM instead of UDIMM. The Kingston datasheet gives the wrong dimensions.

Since 2016, I've had a fileserver mostly just for backups. System is on 1 drive, RAID6 for files, and semi-annual cold backup.

I was playing with Photoprism, and their docs say "we recommend placing the storage folder on a local SSD drive for best performance." In this case, the storage folder holds basically everything but the pictures themselves such as the database files.

Up until now, if I lost any database files, it was just a matter of rebuilding them by re-indexing my photos or whatever, but I'm looking for something more robust since I'll have some friends/family using Pixelfed, Matrix, etc.

So my question is: Is it a valid strategy to keep database files on the SSD with some kind of nightly backup to RAID, or should I just store the whole lot on the RAID from the get go? Or does it even matter if all of these databases can fit in RAM anyway?

edit: I'm just now learning of ZFS caching which might be my answer.

I’m working on driving a very finicky lcd. I have it working now with an FPGA dev kit. I had to use an FPGA because some of the timing requirements are in the tens of nanoseconds.

At the end of the day, I wrote a block for a one shot/continuous clock with a programmable duty cycle and initial delay. This block was repeated six times for the various clocks with their specific values.

Moving to the final product, this feels like overkill. In the past, I’ve managed to make this kind of thing work with a Rube Goldberg collection of on-board timer/counters on the microcontroller.

I’d like to avoid that mess this time around. If I can generate the clocks externally, I can have the host MCU send the data quickly using DMA.

An FPGA works great, but they’re expensive and there’s the issue of licensing for FPGA and and CPLD software.

I’ve seen this problem solved with a lookup table, but there aren’t a lot of cheap/small rom/ram options for what I’m trying to do.

Basically, what I’m asking is is there a component that can be easily programmed to generate a number of clocks, doesn’t need any costly software licensing, and comes in a very small package? (Like wlcsp)

Back in my day, you could usually sip a few mA from a USB2 port without any trouble.

When I try that now, Windows pops up with a “device not recognized” error. I know you can draw up to 150mA before enumeration, but it looks like after some time, Windows will complain that you haven’t enumerated yet.

Is there an easy way to keep from getting this error without having to actually make the device smart?

I’m hoping for something dumb along the lines of USB-PD but facing the other direction. For the record, it has to work on a USB-A port, so USB-C hacks won’t work.

Just curious because I don’t see people talk about it a lot.

Like why do I feel like I’m supposed to be able to name the seven boroughs? I can’t tell you anything about L.A., Chicago, Boston, etc.

Edit: to clarify: I mean that everyone in America are expected to know NYC. Not just New Yorkers. Obviously everyone should know the layout of where they live.