Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Incorrect pathing in copy binary command in "from scratch" doc #285

Closed
4 tasks done
Spl0itable opened this issue Dec 1, 2023 · 3 comments
Closed
4 tasks done
Labels
bug Something isn't working

Comments

@Spl0itable
Copy link
Contributor

Requirements

  • Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a single bug? Do not put multiple bugs in one issue.
  • Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Summary

Hello, the from scratch doc: https://join-lemmy.org/docs/administration/from_scratch.html

Has the following instruction:

Then copy the binary.

sudo cp target/release/lemmy_server /opt/lemmy-server/lemmy_server

However, the path /opt/lemmy-server/lemmy_server is not correct and should be /opt/lemmy/lemmy-server/lemmy_server

Steps to Reproduce

See summary

Technical Details

See summary

Version

0.18.5

Lemmy Instance URL

No response

@Spl0itable Spl0itable added the bug Something isn't working label Dec 1, 2023
@Spl0itable
Copy link
Contributor Author

Further issue for this doc...

Lemmy config, put this in /opt/lemmy/lemmy-server/lemmy.hjson

But then in the systemd unit file it lists the config location at /opt/lemmy/server/lemmy.hjson

So running the service will fail because of the typo /server/ instead of /lemmy-server/

@Spl0itable
Copy link
Contributor Author

Good lawd... found another typo error preventing fedi...

In the provided nginx example it shows this:

set $proxpass "http://0.0.0.0:1234";
      if ($http_accept ~ "^application/.*$") {
        set $proxpass "http://0.0.0.0:1234";
      }

But the port is wrong for the proxpass var if there's a match of the accept header. Should NOT be 1234 like the first but 8536

@Nutomic Nutomic transferred this issue from LemmyNet/lemmy Dec 4, 2023
@Nutomic
Copy link
Member

Nutomic commented Dec 4, 2023

The file is here, you can make a pull request to fix those things.

Spl0itable added a commit to Spl0itable/lemmy-docs that referenced this issue Dec 4, 2023
Nutomic pushed a commit that referenced this issue Dec 5, 2023
* Update from_scratch.md

Fixing typos from: #285

* Fixed types in from_scratch.md

Removed tls option
@Nutomic Nutomic closed this as completed Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants