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

Documentation doesn't mention ROCKET_ADDRESS #57

Closed
asonix opened this issue Jul 28, 2019 · 3 comments
Closed

Documentation doesn't mention ROCKET_ADDRESS #57

asonix opened this issue Jul 28, 2019 · 3 comments

Comments

@asonix
Copy link

asonix commented Jul 28, 2019

When setting up Plume, I found I couldn't access my instance when visiting the URL I had set up, this was because Plume wasn't running on the same host as the Reverse Proxy, and it had bound to localhost:7878 and not [my host's ip]:7878. I found the env("ROCKET_ADDRESS") when looking through the source code and got it set up properly, but not everyone will be able to read Rust code.

@asonix
Copy link
Author

asonix commented Jul 28, 2019

(btw, my instance is up at blog.asonix.dog, now)

@trinity-1686a trinity-1686a transferred this issue from Plume-org/Plume Jul 29, 2019
@trinity-1686a
Copy link
Contributor

trinity-1686a commented Jul 29, 2019

(I've transferred this issue to the right repository)
ROCKET_ADDRESS is mentioned here, and this page is linked just under the sample .env that is given as an installation step here. Do you know what we could do to make it standout more (rephrasing, different formatting...) ?

@asonix
Copy link
Author

asonix commented Jul 29, 2019

ah, I missed that link entirely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants