-
Notifications
You must be signed in to change notification settings - Fork 50
browser url incorrectly points to content-api #88
Comments
The problem is that binaries were removed, so you have to set Then it works:
Right now there's a problem without using binaries (see #89). I'll wait until that is resolved before figuring out how to let users specify that they are using a static site. Note: Ideally, if baseURL is empty we should just make static the default, since most apps will need to specify baseURL for content-api. |
just dropping this by because i think its related to this and issue #83. previously i opened a ticket that was throwing the same type of errors. you had added a new param that when used in the main configuration. would allow the generated site to work correctly. The reason was because the environmental variable is not available, in the browsers context when hosting as a plain static site. |
Yes |
no prob, i was just taking a quick peek. Something like this should do it (https://www.npmjs.com/package/envify). idk if thats the best fit or not but something along those lines might help. |
related to comment in #83
The text was updated successfully, but these errors were encountered: