Our focus today is primarily going to be the first layer of tooling
- Layer 1: Locally available tools. Anyone can use and run the tool if they have the codebase. The tools travel with the codebase. Dependencies are managed.
- Layer 2: Automated tools based on events. The tools above can be invoked from external services (events).
- Layer 3: Build tools. The tools can be installed and built automatically when we move to a containerized development environment, which completely eliminates local dependency management.
Using ground control (repo of all client skels) to aggregate all ssh into one configuration file.
A tool that can be used to sanitize a client's media. Many of our client's media folders are > 1GB which takes a lot of time and resources to pull down locally. This tool aims to shrink the media, using symlinks and keeping the integrity of the media by keeping track of dimensions. This ensures that product images don't end up as swatch thumbnails and vice versa.
A tool that allows us to run our configured static code analysis locally, alerting us of any errors in the code whether they be syntax or performance causing.
A tool that allows us to run our functional regression tests for each client.
Storing and applying application specific configuration whether it be xml modifications, changes in system configuration, or copying files.
Adding the utility that auto-mounts the local SAN
Contributing to the readme for skel to break it down to the average plebe.
Rob TBD
A tool that allows for taking snapshots of a browser using PhantomCSS and comparing that snapshot to another snapshot.
Brice TBD
Brice TBD