Stream: IG creation
Topic: markdown files showing up output folder
Eric Haas (Jun 08 2020 at 19:59):
When I run the sample-ig using the base-templates, the markdown file do not appear in the output folder, however, when I use my own sample-ig all the markdown files appear in the output folder and cause issues when publishing on Github pages which is using Jekyll to render them and crashing due to broken includes.
Eric Haas (Jun 08 2020 at 20:04):
in essence every md file in my input/pagecontent is winding up in output. Is there a way to prevent this?
Lloyd McKenzie (Jun 08 2020 at 22:31):
You cloned sample-ig and made no changes and files are showing up elsewhere, or you made changes to the template?
Eric Haas (Jun 09 2020 at 00:52):
The sample ig has markdown files already. I made changes to the templates and the sample-ig does not output these files to the output directory however when running the same templates on my sample ig all the markdown files show up in the output directory. otherwise it publishes as expected.
Eric Haas (Jun 09 2020 at 01:02):
(i did update my version of the sample ig since the was an error in the file name. )
Eric Haas (Jun 11 2020 at 16:42):
This is an side effect of adding this parameter to the IG resource
- code: path-pages
value: input/pagecontent
I checked to see if a template thingy and it seems to be... we either need fix it or document it so you can avoid liquid errors when publishing to a liquid aware site like GitHub Pages
Lloyd McKenzie (Jun 11 2020 at 16:50):
So this is only a problem when publishing to Github Pages, but not when publishing using the CI Build or local build?
Eric Haas (Jun 11 2020 at 17:41):
Good question...I’m not sure about the ci build. Ok locally ... lemme check and see...
Eric Haas (Jun 11 2020 at 18:34):
yes OK locally and in ig-build - so far is only a github pages issue which is Jekyll aware.
Lloyd McKenzie (Jun 11 2020 at 18:37):
How is the github pages stuff working? Is it running all of the Ant scripts and other pieces of the publisher? Is it running Jekyll twice somehow?
Eric Haas (Jun 11 2020 at 20:29):
it sees a liquid tag in a markdown file and runs it. so a {% include foo.md %} will cause an error if foo.md since there is no output/_include/foo.md in the repro.
e,g,
GitHub Pages site is currently being built from the /docs folder in the master branch.
https://help.github.com/en/github/working-with-github-pages/about-github-pages-and-jekyll
Your site is having problems building: A file was included in StructureDefinition-template-profile-on-profile-intro.md that is a symlink or does not exist in your _includes directory. For more information, see https://help.github.com/en/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites#file-is-a-symlink.
Lloyd McKenzie (Jun 11 2020 at 22:17):
But where does the /docs folder come from? The template depends on stuff in the Ant script running. As well, the publisher has to generate all the fragments. And we don't want those committed into Github. So how are the Git pages working? Also, do we even need git pages anymore now that we have the ability to publish branches on the CI-build?
Eric Haas (Jun 12 2020 at 20:40):
you can nominate an output folder in the ig parameters and sometimes you just want to share your local output without using the autobuild..and use Git Pages to to view.., its a nice feature of pages.
Eric Haas (Jun 12 2020 at 20:41):
I think its not worth a lot of effort just a note somewhere. but where?
Lloyd McKenzie (Jun 12 2020 at 20:59):
But we don't want to override the output folder in the ig parameters because then the ci-build wouldn't work?
Eric Haas (Jun 12 2020 at 21:03):
I agree is not for ci build but more for dev and testing.
Lloyd McKenzie (Jun 12 2020 at 21:41):
But the IG is configured to publish to the CI-build. You don't want to have to mess around with the IG definition to decide whether the CI build works or not. Every time you commit, the CI-build needs to work.
Lloyd McKenzie (Jun 12 2020 at 21:42):
If you're doing local testing, you've got your local output folder. If you've got something that works there, then it pushes up to the CI-build. If you want to mess around with an idea, then you push it to a branch on the CI-build. What does git pages buy us process-wise?
Last updated: Apr 12 2022 at 19:14 UTC
