+[2016-11-07T22:43:26Z]jaybeUse anything other than pastebin.com :) +[2016-11-07T22:51:08Z]SimbaclawsI've already tried removing all of my gems and reinstalling them to no avail +[2016-11-07T22:51:11Z]Simbaclawssorry for the late response +[2016-11-07T22:52:48Z]SimbaclawsI'm off for today, have to go to sleep, I'll probably be here tomorrow +[2016-11-07T22:53:13Z]SimbaclawsI'll check the source code for running jekyll, perhaps there is something in there that makes me see clearer
I've already tried removing all of my gems and reinstalling them to no avail
+[2016-11-08T06:10:09Z]desnudopenguinoso I'm working with setting up a multiple-jekyll server to run a few blogs/projects (as well as some other web services like RoR, and maybe a basic httpd). What would you guys suggest I do for my jekyll instances? +[2016-11-08T06:13:18Z]desnudopenguinoMy current thought is letting the instances run on the loop-back (as with testing) to update when I add a new file to the _posts directory, and having httpd manage the internet-facing service. +[2016-11-08T06:15:49Z]jaybeuse version control (git); and trigger a build and publish upon commit to 'production' branch +[2016-11-08T06:17:34Z]desnudopenguinothat's a good idea! +[2016-11-08T06:18:21Z]desnudopenguinoi'm familiar with git. just trying to figure out a good workflow and management plan for jekyll stuff