+ [2016-11-07T22:43:26Z] jaybe Use anything other than pastebin.com :)
+ [2016-11-07T22:51:08Z] Simbaclaws I've already tried removing all of my gems and reinstalling them to no avail
+ [2016-11-07T22:51:11Z] Simbaclaws sorry for the late response
+ [2016-11-07T22:52:48Z] Simbaclaws I'm off for today, have to go to sleep, I'll probably be here tomorrow
+ [2016-11-07T22:53:13Z] Simbaclaws I'll check the source code for running jekyll, perhaps there is something in there that makes me see clearer

message no. 156040

Posted by Simbaclaws in #jekyll at 2016-11-07T22:53:13Z

I'll check the source code for running jekyll, perhaps there is something in there that makes me see clearer
+ [2016-11-08T06:10:09Z] desnudopenguino so 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] desnudopenguino My 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] jaybe use version control (git); and trigger a build and publish upon commit to 'production' branch
+ [2016-11-08T06:18:21Z] desnudopenguino i'm familiar with git. just trying to figure out a good workflow and management plan for jekyll stuff