I found another documentation page that actually tells you how to get the "v3" version....
https://join-lemmy.org/docs/en/contributors/04-api.html
That needs to be part of the "Lemmy from Scratch" documentation page too.
RoundSparrow
joined 2 years ago
I knew it was v3 because I saw a webapp failure on one of the Lemmy instance (lemmy.ml) I was using ;) We need to update those install documents.
It seems right now I can get a client to load, but websockets aren't working. Others on Reddit reported the same issue: https://old.reddit.com/r/Lemmy/comments/142sszq/spinning_up_lemmy_websockets_dont_connect/
EDIT: Ok, I solved the websocket problem by using proper nginx config that the instructions said. I was confused about the domain names with the certification generation as I already had some nginx certs for other subdomains in place.
A couple of us have been detailing experience and problems with those instructions:
!lemmy_admin is the official place for discussing install and being a server administrator
My guess is to leave open the possibility of adding HashTag support within the app. YouTube hash HashTags that allow you to jump between channels... I could see something like that working.
Is that the correct was to specify the version?
No, I had to dig around too, the correct command is:
curl localhost:8536/api/v3/site
The lemmy-ui steps, the next part - are pretty outdated. It has instructions to install NodeJS 12.x, which is really far back. I have no idea which version the Docker install is using...
The latest version of Node is 20
> thread 'main' panicked at 'Couldn't run DB Migrations', crates/db_schema/src/utils.rs:165:25
I fixed this by issuing:
sudo -iu postgres psql -c “ALTER USER lemmy WITH SUPERUSER;”
Obviously this has database security implications, but at least it identified that was why DB Migrations is failing.
EDIT: I found the developers of Lemmy seem to have identified the cause for this, it's just a couple SQL statements: https://github.com/LemmyNet/lemmy/pull/2983/commits/29c4144e61e97e895fb7eb37d2c257c8520fd6a6
EDIT 2: The developers are currently treating this as a documentation bug: https://github.com/LemmyNet/lemmy-docs/issues/201
I am stuck at this same point!
We need some help here....
Were these remote instance communities or local ones?
I've only seen it happen with remote instance ones. I'm curious what the code is doing.