Stream: IG creation
Topic: Asset paths for IG
Nick Robison (Jul 25 2019 at 16:59):
Hi folks,
Quick question regarding the IG build process. Is it possible to specify a relative path for asset and page locations?
We're trying to make our IG available under an ig/ route on our website, but it looks like all of the asset and page paths are hard coded to /assets/, whereas we'd like them to be ig/assets/. Is there a way to specify a path prefix for the publisher to use?
Lloyd McKenzie (Jul 25 2019 at 17:30):
The publisher has some constraints around relative paths for security reasons. However, the new template-based publisher approach should let you define shared assets in your template and make them available to all IGs that use that template for publication
Lloyd McKenzie (Jul 25 2019 at 17:31):
(We're just not 'quite' there in terms of releasing the template approach yet - will be ready for Sept. though.)
Eric Haas (Jul 25 2019 at 17:36):
in ig,json specify the path in paths.pages
Nick Robison (Jul 25 2019 at 17:49):
Not sure I'm totally following. If I use the publisher as is, I get all of my resources generated in a single folder with the URL, this works fine when serving from directory (e.g. links to toc.html work correctly). My issue is that we're serving our IG under a different path /ig. Which means that links to toc.html should point to localhost:3000/ig/toc.html, but instead they point to the server root localhost:3000/toc.html. It's the same for all generated StructureDefinitions and such.
So I guess my question is, am I doing something incorrect that is causing the paths to be generated incorrectly?
Eric Haas (Jul 25 2019 at 18:40):
I think I understand what you are asking and I don’t know
Grahame Grieve (Jul 25 2019 at 20:44):
you root URL is wrong then
Last updated: Apr 12 2022 at 19:14 UTC
