Do you have a collection of tools and scripts that you've written to save time at the command line? Is it hard to keep them documented, and difficult for new teammates to get familiar with them? Subcommander is here to help.

Several familiar tools (like git, subversion, cvs, zip, even, etc., follow a pattern where the main executable is invoked with an argument naming another executable specific to that system. For example, git push causes git to invoke git-push. This establishes a kind of "namespace" for executables.

Subcommander attempts to provide a simple convention-based way to encapsulate this pattern, so you can get your piles of disparate scripts organized. It intends to be language agnostic: all sub-commands may be implemented in any number of languages. Subcommander itself happens to be implemented in Python, but this should make no difference to the user. The author plans to re-implement the same functionality in Rust.

What's new since v0.x

The first version of Subcommander was implemented as a bash script. We've left that behind for a complete rewrite in Python, and made a few design changes:

  • Eliminated default .d directory; default to /usr/lib/blah or ~/usr/lib/blah
  • Perform recursive walk; don't rely on sub-symlinks to subcommander
  • Implemented in python
  • Creates rcfile if nonexistent
  • Package may be installed system-wide by package manager/pip/easy_install,
  • Separate logic of context discovery into an included subcommand, not part of main executable.

However, v0.x was more thoroughly used and tested, so it may have fewer bugs than this branch under development.


Clone this repository somewhere on your system.

Example Configuration

Let's pretend that you have a collection of scripts in your ~/bin directory that you use while working on your project: proj_runserver, proj_db_start, proj_db_stop, and proj_deploy. Let's use subcommander to clean this up a bit, and create a single tool named proj.

  1. Create a symlink to (or a copy of) the script in ~/bin named proj.

     $ ln -s /path/to/lib/ ~/bin/proj
  2. At this point, running proj will already produce useful information:

     $ proj
     Creating rcfile /home/mike/.projrc.
     Subcommands directory does not exist. Place executable files here to
     enable them as sub-commands: /home/mike/usr/lib/proj
  3. So, do what it recommends. Create the directory ~/usr/lib/proj to hold all the sub-scripts:

     $ mkdir -p ~/usr/lib/proj
  4. You should now have:

     ├── bin/
     │   └── proj -> /path/to/lib/
     └── usr/
         └── lib/
             └── proj/
  5. help is a subcommand included with subcommander that you will probably want as well. Place a symlink (or copy) of it in your scripts directory.

     $ ln -s /path/to/lib/subcommander/help ~/usr/lib/proj/
  6. You should now have:

     ├── bin/
     │   └── proj -> /path/to/lib/
     └── usr/
         └── lib/
             └── proj/
                 └── help -> /path/to/lib/subcommander/help
  7. Now, running proj produces:

     $ proj
     usage: proj COMMAND [OPTION...] [ARG]...
     Available 'proj' commands are:
        help                 Lists the available sub-commands (this text)
     No COMMAND specified.

Pretty good for two symlinks and a couple directories, eh?

  1. Let's move your scripts into that scripts directory. Since we have a nice namespace, we can make their names a bit less verbose.

     $ mv ~/bin/proj_db_start ~/usr/lib/proj/db_start
     $ mv ~/bin/proj_db_stop ~/usr/lib/proj/db_stop
     $ mv ~/bin/proj_deploy ~/usr/lib/proj/deploy
     $ mv ~/bin/proj_runserver ~/usr/lib/proj/runserver
     $ tree
     ├── bin/
     │   └── proj -> /path/to/lib/
     └── usr/
         └── lib/
             └── proj/
                 ├── db_start
                 ├── db_stop
                 ├── deploy
                 ├── help -> /path/to/lib/subcommander/help
                 └── runserver
     $ proj
     usage: proj COMMAND [OPTION...] [ARG]...
     Available proj commands are:
        help                 Lists the available sub-commands (this text)
     No COMMAND specified.
     $ proj db_start
     Starting the database...


The steps above are sufficient for most, but we need not stop there. In the example above, we have two commands db_start and db_stop that are database-specific: we can further organize them into their own namespace so that we can call them with proj db start and proj db stop respectively.

    $ mkdir -p ~/usr/lib/proj/db
    $ mv ~/usr/lib/proj/db_start ~/usr/lib/proj/db/start
    $ mv ~/usr/lib/proj/db_stop ~/usr/lib/proj/db/stop

    $ tree
    ├── bin/
    │   └── proj -> /path/to/lib/
    └── usr/
        └── lib/
            └── proj/
                ├── db/
                │   ├── start
                │   └── stop
                ├── deploy
                ├── help -> /path/to/lib/subcommander/help
                └── runserver

Now the main command list is shorter:

    $ proj
    usage: proj COMMAND [OPTION...] [ARG]...

    Available proj commands are:
       db                   Runs subcommands
       deploy               copies working directory up to server
       help                 Lists the available sub-commands (this text)
       runserver            runs my server on port 8080

    No COMMAND specified.

Running the new db command shows its subcommands:

    $ proj db
    usage: proj db COMMAND [OPTION...] [ARG]...

    Available 'proj db' commands are:
       start                starts the database
       stop                 stops the database

    No COMMAND specified.

Which can be called like so:

    $ proj db start
    Starting the database...

Improvements for subcommander-based sub-scripts

Automatic descriptive text

Subcommander's help script has some built-in logic for pulling short descriptive text out of your scripts for display in the list of available commands. It's super simple: just add a comment near the top of your script that begins with "Desc" or "description" followed by a colon or equals, and a short line of text. Continuing with the examples above, let's add comments like these to our scripts:

    # Description: runs my server on port 8080

    /* Description: starts the database

    // desc: stops the database

    DESC=copies working directory up to server

The result:

    $ proj help
    Available proj commands are:
       db_start             starts the database
       db_stop              stops the database
       deploy               copies working directory up to server
       help                 Lists the available sub-commands (this text)
       runserver            runs my server on port 8080

Environment variables available to sub-scripts

When executed as a sub-command, the following environment variables will be available to subcommand executables:

  • SC_ARGV0: The basename of the top-level symlink to subcommander. In the examples above, this would be "proj".

  • SC_COMMAND: The full command used to execute the script. When ~/usr/lib/proj/db/start is being executed, this would be "proj db start".

To see what variables are set by subcommander when it executes your tool, try the info subcommand included with subcommander.

    $ ln -s /path/to/lib/subcommander/info ~/usr/lib/proj/
    $ proj info

"I don't like ~/usr/lib/proj"

A subcommander-based tool named proj will default to looking in the directory ~/usr/lib/proj for its subcommands. This may be overridden by setting PROJ_EXEC_PATH in the environment. Add a line to your ~/.projrc file like:

export PROJ_EXEC_PATH=/path/to/proj_subcommands

These names are dependent on what you name your tool. If instead of proj you called your tool foo, FOO_EXEC_PATH would name the location for subcommands, which would default to /usr/lib/foo/, and you would put foo-specific configuration in ~/.foorc.

Automatic context discovery

Git performs context discovery for its subcommands. Whenever git is invoked, the first thing it does is identify what git repository you intend for it to work with, by checking environment variables and walking up the directory tree. Subcommander includes an optional feature that apes this, allowing your disparate tools to have an easy way to determine the location of the root directory of the current context/project/checkout/virtualenv you are working with, and to have project-specific settings and hooks.

To enable context discovery, symlink the .apply_context subcommand into your EXEC_PATH.

    $ ln -s /path/to/lib/subcommander/.apply_context ~/usr/lib/proj/

You can also link in the init script is included to make the setup of a context easy.

    $ ln -s /path/to/lib/subcommander/init ~/usr/lib/proj/

Now, let's say you're working on a version of your project, with a directory structure like this:

    ├── module1/
    └── module2/
        └── feature/

Within devel/branch1, proj init produces:

    ├── module1/
    ├── module2/
    │   └── feature/
    └── .proj.context

Then, from anywhere within devel/branch1, running any proj command would invoke it as before, but with the SC_CONTEXT environment variable set to devel/branch1.

Hook scripts and environment variables

If you would like to call hook scripts or set variables into the environment every time you use proj, add them to ~/.projrc.

If you want to call hook scripts or set variables specific to your project, add those commands to the context file .proj.context in the root of your proj context.

The context file .proj.context and rc file ~/.projrc are by default executable shell scripts. You can replace them with any executable, written in any language, as long as you follow their convention of executing (with exec()) their argument list. Here's a context file that sets one environment variable:

export FOO_PATH="/tmp/foo"
exec "[email protected]"

Here it is again, in Python:

import os
os.environ['FOO_PATH'] = '/tmp/foo'

It doesn't even need to be a script. Here it is again, as a C program you can compile and use as a context file. (Though I can't imagine why anybody would do this.)

#include <stdio.h>
int main(int argc, char *argv[])
    setenv("FOO_PATH", "/tmp/foo", 1);
    return execvp(argv[1], &(argv[1]));

Now, whenever a subcommand is executed by proj, the environment variable FOO_PATH will be set to /tmp/foo.

Remember: Subcommander configuration files are just normal executables that exec() their arguments.

These names are dependent on what you name your tool. If instead of proj you called your tool foo, your context files would be named .foo.context, and your rc file would be named ~/.foorc.

Integration with virtualenv

I dislike the way virtualenv's bin/activate works; I prefer a system level tool that launches a subshell. Such a method is described here: Virtualenv's bin/activate is Doing It Wrong. You can enable it for use with a subcommand script like this, which I call inve, for "in the virtualenv":

    export PATH="$SC_CONTEXT/bin:$PATH"
    unset PYTHON_HOME
    exec "${@-:$SHELL}"

If you have already done proj init in the root of your virtualenv environment:

  • proj inve python will run python as if it were being run after sourcing bin/activate.
  • To simulate bin/activate try proj inve. Where you would normally use deactivate, just type CTRL+D or exit.
  • Now pip behaves as you would expect. pip installs to your system or user-level environment unless you call it like proj inve pip.

Other tools like this one

There are many tools that accomplish something similar. This is my defense against accusations of NIH Syndrome. Here is a comparison of similar tools I have found, and the reason why I created this instead of using them.

  • 37signals/sub: This tool adopts many of the same principles as Subcommander, such as language-agnosticism. I discovered it months after I had written Subcommander. You might consider it if you prefer its license or architecture. There's a good introduction in this blog post: Automating with convention: Introducing sub


It may be simple to create a small launcher for scripts in other languages, but that means every time you add, move, or rename a script you'd have to touch some main file. Subcommander is entirely configured by the existence of a script at a particular place in the filesystem.

To Do:

  • I built a much more robust and featureful inve at work, that checks that you are within a virtualenv environment, provides docs and friendly error messages, etc. Get permission to release it here, or re-write.
  • Explore building unit tests for subcommander and subcommander-based tools using chroot. I would love some way to automatically verify whether or not all code paths in all of these scripts work perfectly on various unices-- Ubuntu, Debian, OS X, Arch, Red Hat.
  • Employ another way to get descriptive text; we won't be able to parse binaries for 'Description:' lines.


All of the code herein is copyright 2016 Michael F. Lamb and released under the terms of the GNU General Public License, version 3 (or, at your option, any later version.)


Collect your pile of utility scripts into a single command, as sub-commands.

Subcommander Info

⭐ Stars 24
🔗 Source Code
🕒 Last Update 4 years ago
🕒 Created 11 years ago
🐞 Open Issues 1
➗ Star-Issue Ratio 24
😎 Author datagrok