Hello all, sorry I didn’t see this sooner, it seems I don’t have email notifications set up correctly.
the server would not be reachable directly over the internet, so only connections from localhost would be accepted.
The server is a development convenience, and is not meant to be accessed over the internet
you’d have a hard time finding a way to stop it after it run, unless you used some magic around running things in the background and setting timers to kill them - our build won’t exit until ALL your processes exit - servers and all - and if they haven’t exited before time runs out you’ve paid for the CPU time, but gotten no deploy published since “didn’t fully exit all processes” == “unsuccessful” by our standards.
I use this shell script to start he node.js process, which ensure that it is killed when the calling process (Jekyll, in this case) dies.
As a test to confirm this (which would narrow the search area for the root cause), I would like to disable this server. Is it possible to build the site with PostCSS disabled? If so, how is that done?
My workaround for this was to only start the node.js TCP server when
JEKYLL_ENV=development or is not set. So you can disable it by setting
JEKYLL_ENV=production. This is available in v0.3.1 and higher.
I’ve done some more digging and had a successful deploy downgrading jekyll-postcss to v0.2.2
There is a breaking change in the next version (0.3.0), as listed here: https://github.com/mhanberg/jekyll-postcss/blob/master/CHANGELOG.md#030
That breaking change is not related to this Netlify issue.