Igor Rzegocki

**Edit: Sorry my bad, it seems it was fixed in 4.22.0, as now it works properly.** Hey, I also noticed odd behavior with semver, but using kubernetes, maybe this helps...

Unfortunaltely I'm not a JS dev, so if something else needs to be done, to make this work - I won't be a big help here :/ I did this...

Hey! First of all - thank you for this! This will finally introduce HA to LLDAP in my cluster 😍 Tried this today, however I have problems connecting to postgresql...

Hey @uragit! First of all, thanks for all the amazing work you did. It's always nice to see, that project you took is living on it's own :) Secondly -...

I believe it was fixed in one of the forks. Can you test it again, against `unstable` branch, please?

Can you send yourself a dummy message, and provide the source here (with headers, attachments and all the stuff)? I tested Thunderbird and everything looks fine for me...

After I pushed this PR, I noticed there was another attempt before, but closed because of expected login providers refactor. Since this is (I assume) done, I think we can...

For everyone stumbling upon this problem (as I did), here is a workaround: ```yaml - uses: actions/checkout@v4 with: fetch-depth: 2 # important, to fetch previous commit # workaround for https://github.com/dorny/paths-filter/issues/240...

Ok, there "is" workaround, by using sqlx env vars as described here: https://docs.rs/sqlx/latest/sqlx/postgres/struct.PgConnectOptions.html#impl-PgConnectOptions . So by setting: ```nix { services.atticd.database.url = "postgresql://postgres@localhost:5432/attic"; } ``` and then adding `PGPASSWORD=mypostgrespassword` to credentials...