Skip to content
View austinhyde's full-sized avatar
  • Pittsburgh, PA

Organizations

@dbsteward
Block or Report

Block or report austinhyde

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned

  1. dbsteward/dbsteward dbsteward/dbsteward Public

    XML based SQL database change management tool

    PHP 49 15

  2. dbsteward/dbsteward-go dbsteward/dbsteward-go Public

    [WIP] Go rewrite of dbsteward

    Go 2 1

  3. ansible-sshjail ansible-sshjail Public

    An Ansible connection plugin for provisioning FreeBSD jails remotely

    Python 65 34

  4. pathmod pathmod Public

    Modifies your POSIX PATH, without duplicate entries

    Shell

  5. boilerplates boilerplates Public

    Common boilerplates for personal projects

    Go 3

  6. Run Script, with dev docker image Run Script, with dev docker image
    1
    One of the biggest barriers to starting in an unfamiliar repo is understanding how to start up the development environment, build the code, and other common tasks. Once a developer is established in a codebase, it's important to minimize development friction with common tasks.
    2
    
                  
    3
    The `run` script here is a very minimal script that makes it easy to see how to get started, what common tasks are available, and automates those tasks, no matter how trivial. Importantly for long-term maintainability, it allows the "repo maintainers" to change details about, say, starting a dev database, without most other engineers needing to care _how_ that gets done (maybe we use docker-compose, maybe we use raw docker, maybe vagrant). And if they do care, they can just read the script or watch its output.
    4
    
                  
    5
    Importantly, the script is just plain old bash. Most developers are probably familiar with the syntax, and it's ubiquitous, meaning there's no dependencies to install and no esoteric shell-like syntaxes (like `make`) or libraries (like `rake`) to learn. So long as conventions around declaring commands, variables, and help text are conformed to, the file should be relatively self-documenting and easy to contribute to.