-
Notifications
You must be signed in to change notification settings - Fork 16
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
Work with rootURL other than / #19
Comments
Hey @scottkidder thanks for the request 🎉 sorry it has taken so long for me to get back to you on this. I understand that quite a few people have asked for the feature of being able to deploy this to a subfolder instead of a subdomain but I would like to know more about your specific use case before we can really fix this 🤔 firstly, you say that you have an "existing subdomain" so I'm imagining you have something like https://docs.yourawesomeapp.com which is some sort of landing page and you're looking to deploy a guidemaker site at https://docs.yourawesomeapp.com/guides is that right? Is the existing application based on Ember too? @jelhan if you want to also give your use case here too that would be very useful 👍 |
I want to deploy the guides to a GitLab Pages automatically in CI. The default domain name for GitLab pages for a repository is |
Hi, thanks for your great work on this project. It's really cool to see Ember being used to bootstrap something that I can hand off directly to non-developers and watch them get stuff done really quickly.
We want to deploy this internally on an existing subdomain with an alternate rootURL. I've changed rootURL in config/environment.js but it seems that ember-data is using absolute paths so the requests for versions.json and pages.json are failing.
Have there been any thoughts around this? I can work on a PR if it seems reasonable.
The text was updated successfully, but these errors were encountered: