Needlessly Promiscuous, Modularize!

    devpail

    2.1.1 • Public • Published

    DevPail - a bucket of development tooling

    This is version 2.1.1.

    GitHub package.json version License Package Version (npm) Downloads Per Month (npm) Buy Me A Coffee

    DevPail is what you carry all your DevTools in. DevPail Logo

    DevPail builds flexible Docker container and GulpJS task runner combinations which isolate and encapsulate your projects' development environments, so you don't have to.

    You don't need to write a custom Gulpfile for each project, but instead configure the operation of Gulp via directives in package.json which enable various plugins.

    Installation

    Before you use DevPail, you will need a working installation of Docker.

    Since DevPail can (should!) be used across multiple projects, it's best to install it globally:

    npm install --global devpail

    If you intend modify the code before use:

    git clone https://github.com/tdesposito/DevPail.git
    cd DevPail
    npm link .

    Usage

    Before you can start using DevPail, you'll need to build at least the default image (python3.8/node14):

    $ devpail --build
    DevPail: Building image "devpail:default"...
    ... lots of stuff happens ...

    You can pass Docker ARG parameters directly on the above to customize the build.

    WARNING: The Docker image DevPail builds will contain various secrets from your local machine, including AWS access keys, SSH keys, and Git credentials. DO NOT PUBLISH OR SHARE YOUR DevPail IMAGES!

    To initialize your project, in the top-level project directory (where your package.json and other project files are):

    $ devpail --init
    DevPail: Setting defaults for your project...

    DevPail creates a Docker volume to contain all your development tooling (NodeJS modules, Python packages, and so forth), and a Docker container which mounts that volume and your source code. Inside that container, it runs a plugin-based GulpJS task runner. Rather than constructing a bespoke gulpfile.js for each project, you configure DevPail plugins via your package.json file. How? Oh, look, that's right here!

    Configuration

    Configuration for your DevPail is kept under the devpail key in your package.json file. You can use devpail --init to provide you with a skeleton. (Even if your project isn't Node-based, you'll need a package.json to track the tooling used by DevPail.)

    Ports

    DevPail uses ports 3000-3009 inside the container. 3000 is always a BrowserSync server, and 3009 is the BrowserSync UI. Use of the remaining ports is optional and application-specific. You specify which you want mapped onto your local ports with the ports key, which is an array of "host:container" mappings, i.e.:

    "devpail": {
        "ports": [ "8080:3000", "4044:3009" ]
    }

    This makes the container's browser-sync available as localhost:8080, and the browser-sync UI as localhost:4044. You MUST list the container's port 3000 FIRST!

    Compiler and Server Plugins

    In DevPail's parlance, Server and Compiler plugins manage distinct parts of the development and build processes.

    During development, a Server plugin can affect the BrowserSync configuration, and it may start a long-running process (such as a Flask instance) which is proxied (or not) into BrowserSync. A Compiler plugin has access to the BrowserSync instance, so it CANNOT alter the BrowserSync configuration.

    During the build task, all the Server plugins run in series (unless otherwise configured), then all the Compiler plugins run in parallel (unless otherwise configured).

    Plugins may not need specific configuration, in which case they can be listed by name. If they need configuration, they are listed in an object which contains that configuration. For example:

    "devpail": {
      "compilers": [
        "compiler/html/terser",
        {
          "plugin": "compiler/javascript/uglify",
          "source": "javascriptSource",
        },
        "compiler/css/clean-css"
      ],
      "Servers": [
        {
          "server": "server/flask",
          "environ": {
            "FLASK_CONFIG_VAR": "flask-config-value"
          }
        }
      ]
    }

    In this case, the terser and clean-css plugins will operate based on their defaults, while the uglify and flask plugins will use the provided configuration.

    Task plugins

    Task plugins provide additional Gulp tasks which are added to the Gulp task list, thus:

    "devpail": {
      "tasks": [
        {
          "name": "serve",
          "plugin": "task/serve/serve-static"
        },
        {
          "name": [ "deploy", "deploy:setup" ],
          "plugin": "task/deploy/aws-s3",
          "bucket": "my-app-deploy-bucket"
        }
      ]
    }

    Each Task plugin is connected to one or more task names in the Gulp task registry, as listed. Configuration parameters are as with other plugin types.

    Plugin Location

    Each plugin is loaded either from the project source code, or via a CDN over the wire.

    To specify a local plugin, use the form ~dir/to/plugin (note the leading ~), which will try to find plugin.js in dir/to in your source tree.

    Otherwise, the plugin is loaded from the CDN defined by the devpail.moduleCDN parameter (if any) in your package.json.

    If you need to operate without internet access, DevPail can provide a "local CDN" with these steps:

    1. Run devpail --cdn from a terminal. The "local CDN" will run on port 8000 unless you specify a port number after --cdn.
    2. Set devpail.moduleCDN to http://host.docker.internal:8000, or whatever port you specified above.
    3. Run devpail as usual!

    MetaTasks

    Some tasks are composed of other tasks; these are metatasks. For example, the default build task is implemented by running the clean:build task, followed by the devpail:build task.

    You define your own metatasks, including overriding a built-in metatask, thusly:

    "devpail": {
      "metatasks": {
        "my-meta-task": [
          "task-1",
          [ "task-2", "task-3" ], 
          "task-4"
        ]
      }
    }

    This creates a new task, my-meta-task, which runs task-1, then runs task-2 and task-3 simultaneously (in parallel), then runs task-4.

    The default metatasks are:

    • build: 'clean:build', 'devpail:build'
    • clean: [ 'clean:build', 'clean:dev' ]

    Running the development environment

    To run the environment, once configured:

    $ devpail
    DevPail: Starting your development environment...
    [19:57:29] Using gulpfile ~/app/gulpfile.js
    [19:57:29] Starting 'default'...
    [Browsersync] Access URLs:
     ----------------------------
     Local: http://localhost:3000
     ----------------------------
        UI: http://localhost:3009
     ----------------------------
    [Browsersync] Serving files from: dev/

    The first time you run devpail, it will have to install at least a few modules, possibly many, which may take a bit of time. But after the first run, it'll go pretty quickly.

    Please remember that the 3000 port specified by BrowserSync is inside the container. The port you should browse to is defined in your devpail.ports configuration.

    You can get a shell into the DevPail container:

    $ devpail --shell
    DevPail: Running a shell in your project container...
    pn@your-project-f44be227:~/app$ 

    From there you can:

    • Install additional project dependencies
      • npm install --save some-package-name
      • poetry add some-package-name
    • Run gulp --tasks or gulp some-task-name
    • Most anything else you'd do from a command prompt.

    You can also pass Gulp task name(s) and parameters to the Gulp instance via devpail:

    $ devpail --tasks
    DevPail: Starting your development environment...
    [20:05:32] Tasks for ~/app/gulpfile.js
    [20:05:32] ├── build
    [20:05:32] ├── clean
    [20:05:32] ├── clean:dev
    [20:05:32] ├── clean:deploy
    [20:05:32] ├── default
    [20:05:32] ├── deploy
    [20:05:32] └── deploy:setup

    Setting Secrets via .env

    DevPail will inject environment variables specified in an .env file at the top level of your source tree into your container's environment.

    TODO: List of Plugins

    TODO: Developing Plugins

    How to Contribute

    We gratefully accept:

    Donating

    I release (most of?) my code under the MIT license, so it's free to use any way you'd like. If you use it and appreciate the efforts I've put into it, please consider Buying Me A Coffee!

    Buy Me A Coffee

    License

    Please see the License.

    Install

    npm i devpail

    DownloadsWeekly Downloads

    1

    Version

    2.1.1

    License

    MIT

    Unpacked Size

    72.5 kB

    Total Files

    24

    Last publish

    Collaborators

    • tdesposito