Unable to build the HTML/PDF about codewriting

[briandominick]

There simply has to be an order that works. I found another that Netlify builds properly and updated PR #29. I'd love if you could pull and test one more time @plaindocs (and @RodinGolodin).

https://app.netlify.com/sites/codewriting-org/deploys/5b61c7edb13fb12ca5a78709

[plaindocs]

So, the branch in #29 works for me.

With the proviso that I had to manually delete the offending dir before running liquidoc.

Doing the same with master results in the same problem.

[briandominick]

Thanks for the report, Sergey. I appreciate your patience and interest!

This looks like the same issue as #13, which I'm hoping is resolved by PR #29 -- if you get a chance to test that PR on your local, I'd be thrilled to get a +1.

And thanks for reminding me about the _config/s/ bug, as I call it in my head now that I've sat on a patch till I can confirm this...

Also: Can you let me know wha OS you're using?

[RodinGolodin]

Hi, Brian! Thank you for a prompt reply.

I'm using macOS Mojave 10.14 Beta (18A336e), and now that you asked, I think I should have mentioned this in the report since a lot of things can go wrong (unexpected) when one is using beta software.

[briandominick]

The plot thickens. I have not been able to reproduce it on MacOS 10.13.4 but have produced it on Linux. This rearranged build config works on Netlify when the master version does not.

[plaindocs]

I'm testing this out with ruby 2.3.6 because neither 2.4.1 and 2.5.0 work for me, on master or on #29 branch. (Linux)

Except building 2.3.6 (using is proving to be a pain due to ssl issues. :-(

[plaindocs]

Maybe try it with 2.4.3 which is also available on Netlify? Doesn't work for me though.

[briandominick]

I am still unable to reproduce the error anywhere but Netflow, where reorganizing solved it. I tried 2.4.3 locally and it works fine. This is reeeeeeally troubling for me, since the whole point of going through all this trouble and using Ruby runtime is to NOT have problems like this between installations. Maybe I need to do some more research into distributing Ruby gems and expecting them to work consistently.

[plaindocs]

Distributable cross platform ruby gems won't help if the underlying filesytem logic is faulty. Not sure what is going on though.

[plaindocs]

Might be a differing permissions issue on osx/linux? I really don't know.

[briandominick]

Thanks for testing @plaindocs! The good news is Netlify's env seems to test this better than I can, so I'm going to use it for tests for LiquiDoc. I've been setting up a content repo that attempts to build actual projects so I can use it for testing the gem itself. I'll also write up instructions about configuring builds in proper order and testing them on a Linux platform at some point (obviously already core to my toolchain for CD).