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

Decoy breaks when not running from domain root (but in url path/directory) #63

Open
eminos opened this issue May 12, 2017 · 3 comments
Open

Comments

@eminos
Copy link

eminos commented May 12, 2017

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/)?

@weotch
Copy link
Member

weotch commented May 12, 2017

Is your app.url config set to http://server.hostname.com/~useraccount/ currently?

@eminos
Copy link
Author

eminos commented May 12, 2017

It is.

@weotch
Copy link
Member

weotch commented May 12, 2017

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.

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

2 participants