| bin | ||
| docker | ||
| script | ||
| .DS_Store | ||
| .gitignore | ||
| .profile.template | ||
| .systems.example | ||
| build | ||
| down | ||
| info | ||
| init | ||
| README.md | ||
| stop | ||
| up | ||
| update | ||
Stack-Up dev-env
Introduction
This project is the development environment of all stack-up projects. It simplifies handling different docker-enabled applications and their maintenance.
Installation
- Create a .systems file bases on .systems.example:
cp .systems.example .systems - Enter all systems in the created file
nano .systems - run
./init. Init will:- update
.aliasesfile, which enables you to switch between your systems easily viagoto-<system-identifier> - updates
.profileto use the updated aliases, enables the dev-env binaries (denv, drun, dcom, ...) and add some utility functions - clones all systems defined in
.systems - calls the
bin/script/initscript for all cloned systems.
- update
- Perform init actions on systems
./upto start your containers- up will also run all the
bin/script/firstRunscripts, if the.firstRunmarker is missing
- up will also run all the
Usage
After the installation was performed successfully and you've sourced your ~/.profile file, you'll have access to the following utilities:
- denv
- without a parameter, navigates to the development environment
- if a parameter is specified, denv will try to execute the passed script in the dev-env base folder
- drun
- executes a command on the app container of a system
- dcom
- executes a docker compose command.
- without a parameter, for the system of the current directory
- with a parameter, for the supplied system-id