A small code generator and runner designed to replicate a formally defined development environment. To see a real life use case check out my personal setup created using this helper.
DISCLAIMER
This is a personal project created in a few days. It is very hacky at times and probably does not conform to any bash coding standards. It may be refactored in the future to be less of an eyesore. But it works, at least in the limited tests that were performed.
The generated code is only run if the configuration files are well formed. The only part that can do permanent damage is custom commands and the file copying/linking as it will simply execute cp or ln respectively. That means if the destination folder contains a file with the same name it will be overwritten.
This script was designed to have a minimal amount of dependencies.
| Dependency | Why? |
|---|---|
git |
is needed to clone this repository and to clone repositories defined in the setup |
bash |
is used to execute the script as sh was too limited, currently tested on bash 3 and upwards |
tr |
is used to create a random byte sequence from /dev/urandom. Maybe this dependency can be removed in the future |
The script expects two configuration files:
platforms.confsetup.conf
Both files are written in the same format:
| Syntax element | Meaning |
|---|---|
[tag] |
specifing variable data like a directory or app name |
keyword: |
one of the various available keywords for the predecessing tag |
"variable" "amount of" "values" |
content based on the predecessing keyword |
. |
to close a defined tag (see example usage) |
There can only be one syntax element per line, meaning there cannot be i.e. a tag and a keyword on the same line. See the configuration examples showcasing the structure.
The platform configuration contains available platforms with their specific information.
| Supported keyword | Meaning |
|---|---|
pkginstall |
Values[0]: platform specific command to install packages |
The setup configuration contains the setup which should be replicated. It is based on a hierarchy of absolute directories containing repos, files, subdirectories and apps.
Directories and apps are declared using tags. Please note that every tag must be closed using a ..
The following content can be configured under a directory tag:
| Supported keyword | Meaning |
|---|---|
apps |
beginning of a section containing app tags and their respective keywords and values |
env |
creates an .env file Values[0]: environment variable name Values[1]: value of environment variable Values[2]: (optional) use append or prepend to add the value to the beginning or end of the environment variable, overwrites variable with value if not set Notes: a .env file sources all .env files of its subdirectories so only the .env files of the root directories need to be added to a rc file |
files |
files to be copied or linked into the directory Values[0]: relative path (to the path the script was started in) to actual file Values[1]: use copy or link to perform the desired action |
repos |
repos to be cloned into the subdirectory Values[0]: git link to clone the repo Values[1]: (optional) alternative folder name Notes: will not clone if it already exists |
subdirs |
beginning of a section containing tags of subdirectories and their respective configuration |
The following content can be configured under an app tag:
| Supported keyword | Meaning |
|---|---|
packages |
packages which need to be installed depending on the platform Values[0]: platform Values[1]: packages which will be installed with selected platform specific install command |
cmds |
custom commands which are executed based on selected platform Values[0]: platform Values[1]: custom command to be executed Notes: double quotes need to be escaped |
Note: Using all for the first value in a packages or cmds line causes it to be executed regardless of the selected platform. See the example usage of this below.
After the configuration files are created the script can be run with the required options:
--platform=PLATFORMruns the configuration for the specified platform--dir=CONFIGDIRthe directory containing the config files (relative to pwd)
See the example usage below.
This is a rather nonsensical example to showcase the syntax and capabilities.
Directory structure of the example:
.
├── config
│ ├── platforms.conf
│ └── setup.conf
├── res
│ ├── linkfile
│ ├── textfile
│ └── vimrc
└── setup-helper
├── README.md
└── install.sh
With the following config file content
platforms.conf:
[debian]
pkginstall:
"sudo apt install"
.
[osx]
pkginstall:
"brew install"
.
setup.conf:
[~/development/testfolder]
repos:
"git@github.com:themmj/setup-helper.git"
"git@github.com:themmj/slack.git" "slack-api"
env:
"VAR1" "val1"
"VAR1" "val2" "append"
"VAR1" "val3" "prepend"
files:
"../res/textfile" "copy"
"../res/linkfile" "link"
apps:
[cmake]
packages:
"all" "cmake"
.
[vim]
packages:
"osx" "vim"
"debian" "libx11-dev python3-dev"
cmds:
"debian" "git clone https://github.com/vim/vim.git"
"debian" "cd vim && installcmds && cd .."
.
subdirs:
[subfolder]
env:
"VAR2" "val4"
files:
"../res/vimrc" "copy"
.
.
The previously described setup can be used like this:
$ pwd
~/personal-setup/setup-helper$
$ ./install.sh --platform=osx --dir=../configThe resulting environment has the following structure:
~
├── development
│ └── testfolder
│ ├── .env
│ ├── linkfile
│ ├── setup-helper
│ │ └── ...
│ ├── slack-api
│ │ └── ...
│ ├── subfolder
│ │ ├── .env
│ │ └── vimrc
│ └── textfile
└── personal-setup
├── config
│ ├── platforms.conf
│ └── setup.conf
├── res
│ ├── linkfile
│ ├── textfile
│ └── vimrc
└── setup-helper
├── README.md
└── install.sh
Note that there is no vim directory because on OSX it can be installed using brew and will therefore not be cloned.