@liaizon You know I'm neither impatient nor a sysadmin...

You know I'm neither impatient nor a sysadmin noob, but when trying to install #Kitsune on Debian 11 yesterday, I gave after two hours.

The first hour passed while cargo compiled almost 1000 Rust packages. Fine, I guess this is what happens when you enter a new ecosystem.

The second hour was more infuriating because I failed to construct a valid configuration file for Kitsune. These are in a language called #dhall which seems to be inspired by Haskell.

I tried renaming the config.example.dhall and switching it to sqlite because I thought that for a test drive, installing PostgreSQL was overkill. So I copied the line from https://docs.joinkitsune.org/en/running/basic-configuration/ and got this error message:

thread 'main' panicked at 'Failed to connect to database: Pool(Backend(ConnectionError(CouldntSetupConfiguration(DatabaseError(UnableToSendCommand, "invalid connection string: unexpected EOF")))))', kitsune/src/main.rs:94:6

Using the entire configuration example from that website results in the same error message.

/cc @dev

Like 16 Jun 2023 at 16:18 | Wall-to-wall | Open on digitalcourage.social

7 comments

wakest ⁂

@chpietsch @dev have you already posted this in their issue tracker? you also may get a better response if we tag @0x0 cause I don't think Kitsune has any notification abilities written yet

16 Jun 2023 at 16:20 | Open on social.wake.st

Christian Pietsch 🍑

@liaizon @dev @0x0

Not yet: I needed to wait for the frustration to ebb away. Then I tried to forget about Kitsune. Then you reminded me. ;-)

16 Jun 2023 at 16:22 | Open on digitalcourage.social

Aumetra Ⓐ :nonbinary:

@chpietsch @liaizon @dev oh no, I'm sorry it was a frustrating experience but I can totally understand. It could have been different problems depending on when you tried it.
The most likely problem is that we (as in multiple people in the development chat, this was a large decision and it was best to consult multiple people before going through with this) decided to forego SQLite Support in the newest release.
The reasons were the growing complexity of keeping it in the codebase. When we introduced better full text search, we basically had to split the migrations into two with different constraints, different table layouts, etc.
Basically a lot of maintenance work.

Around that time we were also looking into different ORMs around that time since the old one was on one hand quite dynamic, but on the other hand didn't really aid us via compile-time checks.
The new one we settled on didn't have support for SQLite though.

So those two reasons combined meant that we did forego the support for it.

A classic failure to update documentation by me, my mistake and I apologise for that. I will update them ASAP.
If you wanna give it a try with a PostgreSQL database though but it still has issues, feel free to either ask Mr here or over in one of the chat rooms (linked in the project README)

Expand text...

16 Jun 2023 at 17:22 | Open on corteximplant.com

Christian Pietsch 🍑

@0x0

Thanks for explaining! It all makes a lot of sense. Will try again with Postgres.

@liaizon @dev

16 Jun 2023 at 17:33 | Open on digitalcourage.social

Aumetra Ⓐ :nonbinary:

@chpietsch @liaizon @dev Thank you for giving it a second chance, also the chat channels aren't for development only buy also if someone needs support, so feel free to pop in any time (I should probably add this to the documentation, too)

16 Jun 2023 at 18:45 | Open on corteximplant.com

Christian Pietsch 🍑

@0x0

Maybe try to make this error message more helpful. As it mentions EOL, I thought I had a syntax error in that weird config file.

I was not able to see an unbalanced quote or bracket. So I installed the dhall tool but it was happy with my config file. Then I gave up.

@liaizon @dev

16 Jun 2023 at 18:51 | Open on digitalcourage.social

Aumetra Ⓐ :nonbinary:

@chpietsch @liaizon @dev Thanks for the feedback, I will try to improve that.
In case you still have the config file with which you produced the error, it would be great if you could send that my way.
Because judging from the error, it parsed the file correctly but it was actually the database driver that got confused.
With the repro file I could try to just do some checks on the database string to prevent these unhelpful messages

16 Jun 2023 at 18:56 | Open on corteximplant.com