A space age developer's task runner/asset pipeline tool

Astro aims to eliminate setup time needed when creating or enhancing micro-service modules. Astro provides a framework for incorporating the latest workflow tooling and processes into daily software engineering workflows, and Astro does not require any configuration to be used out of the box.

As workflow tooling and processes change, existing applications will not require task runner updates, new scripts, or additional dependencies to use the latest tools. Never write or change another gulp or grunt or broccoli file!

Currently Astro provides Node.js and front-end development workflow tools:

  • Babel
  • SASS (coming soon)
  • Concat / Minification (coming soon)
  • Image compression (coming soon)
  • Docker (coming soon)

Astro modules, by convention, will be named "astro-{moduleName}".

Astro is responsible for handling commands and running the appropriate astro modules. This allows for new modules to be created and incorporated seamlessly. Astro ships with no modules by default, all desired modules will be installed when they are requested.

Discover astro modules

Each module will have it's own available options. See individual module documentation for details on usage options available.

Astro was also made to work with applications that run within a Docker container. If your application has a Dockerfile then Astro provides you the option of running all your asset pipeline or workflow tasks from within your application's container.

This, for example, lets you execute your tests from within your application's Docker container, ensuring that your tests are passing in your application's production docker container.

For more information see the "--docker" option section below.

Currently astro only works on OSX/Linux. Windows support is in progress currently

$ npm install -g astro

It is recommended to that your NPM environment be configured to not require 'sudo' for global installations.

If not then 'sudo' will be required when installing astro and when running astro commands for the first time (which performs an npm install of the corresponding astro-module.

For more information on configuring NPM to not require 'sudo' see here

Once installed, from any project directory you can run:

$ cd /myProject
myProject$ astro mocha
$ cd ../myModule
myModule$ astro mocha

myProject and myModule in the above example require no setup other than tests in a '/test' folder.

The first time the 'astro-mocha' commmands is executed by Astro, astro will add astro-mocha to your local astro-cli for use.

Astro comes with a built in directory watch mechanism (using Chokidar) that can be added to any astro command. To add a watch just add the "--watch" option to any Astro command:

$ cd myProject
myProject$ astro mocha --watch

Astro will now run the "mocha" command but it will also watch for any changes to "myProject"

Execute any astro command from within your application's docker container. When the --docker option is present, Astro will look for a Dockerfile from within the current working directory. Astro then builds an image from your application's Dockerfile and executes the provided Astro commands from within that container.

This feature has three dependencies

  1. A Dockerfile located at the current working directory where the astro command is issued.
  2. A running Docker instance. For information on running Docker on your development platform see the Docker Installation Instructions for your OS specific installation instructions.
  3. astro-cli must be installed as a local dependency for your specific application.