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
It seems Decoy Admin doesn't work well when the site is running from a "url path". The assets are not loaded since they are pointing to the domain root.
I've just deployed my first Decoy website to a production server running cPanel and I'm using the "temporary url" (since the domain is not yet pointed to the new server) which has the format http://server.hostname.com/~useraccount/.
Is there a way to make Decoy work when it's not running from the domain root, but from a URL path (/~useraccount/)?
The text was updated successfully, but these errors were encountered:
Perhaps we're not wrapping every instance that an asset is referenced in a Laravel url() helper so the app.url domain gets appended. That's where I'd look first to fix this.
That said, I don't see us addressing this ourselves immediately as it's not a use case we encounter internally but we'd happily accept a PR with a fix.
It seems Decoy Admin doesn't work well when the site is running from a "url path". The assets are not loaded since they are pointing to the domain root.
I've just deployed my first Decoy website to a production server running cPanel and I'm using the "temporary url" (since the domain is not yet pointed to the new server) which has the format
http://server.hostname.com/~useraccount/
.Is there a way to make Decoy work when it's not running from the domain root, but from a URL path (/~useraccount/)?
The text was updated successfully, but these errors were encountered: