If in jekyll development, ignore missing environment variables

[djbartos93]

when running Jekyll to write posts and develop on my desktop I don't really want to have to put in the environment variables, I leave that process up to travis-ci to deploy my site, saving the variables as secure values in the .travis.yml file. Whenever I startup my site in development I have to remember to disable the crosspost plugin because it will complain about missing variables. If it could just not look for them if the Jekyll environment is development I think this would solve the problem.

Now it may need to be a setting in the _config.yml file if other peoples workflow is different.

[aarongustafson]

Seems like a reasonable enhancement. I'll see what I can do.

[genebean]

As a stopgap, it seems like you could have Travis CI pull down the lib/jekyll-crosspost-to-medium.rb after cloning your source (aka method 2 of installing per the readme). I am thinking of using a similar setup to do the cross post only after CI is happy.

[aarongustafson]

I kept having Ruby/Jekyll issues when upgrading my Mac, so I have moved off of Jekyll and will not be working on this project anymore, going forward. I am going to flag this as won’t fix, but leave it open in case someone else wants to pick up the project from here.