Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Rakefile mode switch #330

wants to merge 4 commits into


None yet
2 participants

Added a rakefile switch to allow deployment to production or development servers.

  • Generates _config.yml from source files (config-default.yml + config-MODE.yml) (task :gen_config)
  • Can specify different deploy document_root for different modes.
  • Defaults to development (rake task names backward compatible)
  • Added rake task options, eg. rake generate['production']

Pull request submitted in case someone else finds this useful. Or please tell me if I duplicated some work that was already done. There is a Jekyll pull request for a config switch on the command line (mojombo/jekyll#393). If this existed then presumably the _config.yml would not need to be generated, but the octopress rakefile would still need a MODE option.

Jim Pravetz added some commits Dec 17, 2011

Added comment to compass config file
Added mode (development or production) to Rakefile. Now generate _config.yml dependent on which mode.
Added Rakefile tasks for generating config file based on mode, and de…
…ploying based on mode, where mode is one of development or production.

imathis commented Dec 17, 2011

I've been thinking about this for a while because yeah it'd be nice if there was this capability. We're working through some major changes in configuration right now so that may change the way this feature would be implemented and we may or may not end up merging this in. Regardless, thanks for the submission.

No worries. I can understand this getting blown away given any changes to how config is done. I wasn't sure if I should have entered an issue asking if this was worth posting. Thanks for the note.

@imathis imathis closed this May 23, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment