Permalink
Commits on Mar 26, 2015
  1. Update CHANGES for 0.11.1

    gma committed Mar 26, 2015
  2. Bump version to 0.11.1

    gma committed Mar 26, 2015
  3. Add dependency on Tilt 1.4

    gma committed Mar 26, 2015
    Tilt 2.x will try to require the gems that implement the different
    Markdown processors (e.g. Maruku), irrespective of whether or not it's
    installed on the system. This can cause a LoadError.
    
    It's new behaviour, and Nesta will need updating to avoid it. Requiring
    version 1.4 works around it in the meantime.
  4. Sort dependencies in gemspec

    gma committed Mar 26, 2015
Commits on Mar 16, 2015
  1. Made notes on the release process

    gma committed Mar 16, 2015
  2. Update dependencies

    gma committed Mar 16, 2015
  3. haml-contrib no longer required in smoke tests

    gma committed Mar 16, 2015
    We needed this so the demo site didn't break when rendering a page using
    Haml's Markdown filter. It's not required any more as haml-contrib is
    now a dependency of nesta.
  4. Update smoke test script to use chruby

    gma committed Mar 16, 2015
    I use chruby in favour of rbenv or rvm these days, so this change just
    makes life a bit easier when releasing a new version of the gem.
  5. Bump version number to 0.11.0

    gma committed Mar 16, 2015
  6. Update CHANGES for 0.11.0

    gma committed Mar 16, 2015
  7. Pass new object as default scope

    gma committed Mar 16, 2015
    This fixes the test suite under Ruby 2.2. Prior to this change
    `convert_to_html` would raise a `NoMethodError` when `upper` was called
    on `nil`.
Commits on Mar 3, 2015
  1. Merge branch 'plugin-templates'

    gma committed Mar 3, 2015
  2. Prefer Kernel.system to backticks

    gma committed Mar 1, 2015
    When running external programs backticks come in very handy if you want
    to operate on the text printed by a program, but they also have the side
    effect of preventing that output from being printed to STDOUT.
    
    When it's useful to display the output of a command, `Kernel.system`
    feels like a good fit.
  3. Delete a typo

    gma committed Mar 1, 2015
  4. Coding style

    gma committed Mar 1, 2015
  5. Give plugins a Rakefile for managing/releasing gems

    Glenn Gillen committed with gma Feb 24, 2015
  6. Re-implement plugin generation with templates

    gma committed Feb 11, 2015
    Plugins are distributed as Ruby gems. Prior to this commit the gems were
    created using Bundler's `bundle gem` command.
    
    Some time ago the Bundler maintainers changed the file structure of the
    gems that Bundler produced [1], in accordance with some naming
    guidelines for Ruby gems. The suggestion in these guidelines was that
    words separated by hyphens in gem names should correspond to directories
    within the gem (e.g. the nesta-plugin-foo-bar gem would contain a
    `lib/foo/bar` directory).
    
    The argument put forward is that this convention makes it easier for
    people to start using your gem without reading any documentation, as
    they'll know which file to require [2]. This strikes me as a fairly
    ludicrous extrapolation, but there you go.
    
    Nesta has been written to expect a plugin called foo-bar to have a
    `lib/foo-bar/init.rb` file, rather than `lib/foo/bar/init.rb`.
    
    Switching to this new folder hierarchy would have been fairly easy, but
    existing plugins would have had to be re-released.
    
    Jake Owens worked up a patch [3] to Nesta that allowed it to cope with
    loading plugins with either directory structure, but after much thought
    I decided that this extra complexity in Nesta's code didn't sit well
    with me. It's not as if we benefit from it, and we'd still have to fix
    Nesta to cope with future changes in Bundler.
    
    I dislike churn in software, especially if it can be avoided. We've all
    got better things to do than update code that works perfectly well
    already. I've therefore rewritten the `nesta plugin:create` command to
    generate a gem from template files that are totally under our control.
    
    Future edits to the output of `gem bundle` will no longer affect Nesta,
    or our plugin ecosystem. :-)
    
    [1] bundler/bundler@eeba36b
    [2] http://guides.rubygems.org/name-your-gem/
    [3] gma#153
  7. Prefix root-level ignores with /

    gma committed Mar 1, 2015
    The previous rules were matching files within the project, when we
    only intended to ignore those that started with those names.
Commits on Feb 11, 2015
  1. Test on Ruby 2.2, bump 2.1 to 2.1.5

    gma committed Feb 11, 2015
  2. Split commands.rb and its specs into multiple files

    gma committed Feb 9, 2015
    The files were getting far too long and unwieldy; this makes them far
    easier to work with.
Commits on Jan 20, 2015
  1. Nesta::Config.can_use_yaml? is now redundant

    gma committed Jan 20, 2015
    See the previous commit from Glenn; the concept of when you can use Yaml
    is now as simple as "does it exist?" It used to mean "is a NESTA_...
    environment var defined, and if not, does it exist?".
  2. Merge branch 'selective-env'

    gma committed Jan 20, 2015
    For a long time now Nesta has prevented you from spreading your settings
    between `config.yml` and the environment. If you set a single
    `NESTA_...` environment variable, Nesta would expect all your
    configuration to come from the environment.
    
    This behaviour was added back in commit 4ffa508, on the "heroku" branch.
    
    I have a sneaky suspicion that members of the community persuaded me
    that having a config file on Heroku was just not the done thing. It
    seems insane now, and the blog post where the idea was put forward (and
    in whose comments the debate was held) no longer exists.
    
    With the benefit of hindsight, this limitation seems insane!
    
    As Glenn has pointed out, anybody who wants to use the environment to
    configure their apps can use Erb tags within `config.yml` to read values
    from `ENV`, and insert them at run time.
    
    In the future, I'd like to remove all the code that reads the
    environment variables directly, and just recommend that people who want
    to use the environment do that.
    
    Nice one, Mr Gillen. :-)
Commits on Jan 19, 2015
  1. Allow ENV and yaml configs to co-exist.

    Glenn Gillen committed Jan 19, 2015
Commits on Dec 10, 2014
  1. Fix Google Analytics test

    gma committed Dec 10, 2014
Commits on Nov 18, 2014
Commits on Nov 17, 2014
  1. Merge pull request #159 from philmill/md-extension-allowance

    gma committed Nov 17, 2014
    Adds support for Markdown files with md extensions
Commits on Nov 15, 2014
Commits on Oct 16, 2014
  1. Merge pull request #155 from jkowens/fix-27

    gma committed Oct 16, 2014
    Continue parsing menu when a page not found.
Commits on Oct 15, 2014