You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 3, 2021. It is now read-only.
If I run the instance on port 3000 and access it there without a reverse proxy, one of the CSS (/assets/css/lib.css) is linked as an absolute URL, which breaks the linking if the host name is not exactly specified including the port in .env for APP_URL. (ex : http://my.domain:3000/, instead of just http://my.domain/).
This is a side effect of running Postleaf locally (it's intended to run behind a proxy such as Nginx). If you're doing local dev, the [current] requirement is to put the fully URL (including port) in your .env file.
Asset URLs could probably be changed to schemaless URLs. Aside from that, I don't see how the app could know what the proper URL should be.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
If I run the instance on port 3000 and access it there without a reverse proxy, one of the CSS (/assets/css/lib.css) is linked as an absolute URL, which breaks the linking if the host name is not exactly specified including the port in .env for APP_URL. (ex : http://my.domain:3000/, instead of just http://my.domain/).
Steps to Reproduce
Additional info
The text was updated successfully, but these errors were encountered: