heroku-buildpack-nano

Heroku buildpack that installs Nano text editor

Installs Nano Ninja version from Ehryk's repository heroku-nano or if you prefer you can set a config var to download Nano from a custom location.

Nano installation ends in /app/vendor/nano directory.

-----> Build succeeded!
-----> heroku-buildpack-nano app detected
    -> Custom nano URL is not set, start downloading from default location
    -> Downloading Nano... (https://github.com/Ehryk/heroku-nano/raw/master/heroku-nano-2.5.1/nano.tar.gz)
    -> Installing Nano...
    DONE
-----> Discovering process types

heroku buildpacks:add https://github.com/velizarn/heroku-buildpack-nano

{
    "buildpacks": [
        {
            "url": "https://github.com/velizarn/heroku-buildpack-nano"
        }
    ]
}

If you prefer to deploy your own nano archve you can set a config var to download Nano from a custom location, e.g.

heroku config:set NANO_URL_CUSTOM=https://your-custom-url.domain.tld/nano.tar.gz

-----> Build succeeded!
-----> heroku-buildpack-nano app detected
    -> Downloading Nano... (https://mycustomurl.rackcdn.com/nano-2.5.1.tar.gz)
    -> Installing Nano...
    DONE
-----> Discovering process types

• Heroku Buildpack API
• Heroku Configuration and Config Vars
• Edit a File on Heroku Dynos using Nano or Vim
• Nano editor homepage
• Nano shortcuts

If your application runs on heroku-20 stack and nano cannot be executed due to a following error or a similar one:

nano: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory

In this case you can remove Nano buildpack and use heroku/heroku-buildpack-apt instead. With this buildpack you can install additional packages that are not included in the stack image. Even with the fork velizarn/heroku-buildpack-apt you can define those packages in a config var instead of an Aptfile.

MIT © Velizar Nenov