this post was submitted on 07 Jun 2023
2 points (100.0% liked)

Lemmy Support

4942 readers
12 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago
MODERATORS
 

I'm trying this on Ubuntu 22.04 Rust's cargo install seems to keep creating permission problems between what I have to install, compile and what gets published in the cargo "registry", which causes issues at runtime when I run as lemmy:lemmy through systemctl.

If I run: cargo install lemmy_server --target-dir /usr/bin/ --locked --features embed-pictrs as a non-root user, I get permission denied issues with /usr/bin/.future-incompat-report.json and /usr/bin/release

If I run the build as a root user, and then manually copy the binaries to /usr/bin and chmod them to lemmy:lemmy, then try to run as lemmy:lemmy, it appears the binary is trying to access some "registry" files in /root/.cargo/registry (for which of course it does not have permissions.)

How do I fix this?

you are viewing a single comment's thread
view the rest of the comments
[–] RoundSparrow@lemmy.ml 1 points 2 years ago* (last edited 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.