DevOps on the way for Go programs in general and WeGO services in particular
Edit me
Introduction
ToGO contains a set of scripts and a template Makefile.
Makefile
The togo Makefile allows anyone to construct GO programs in WeGO with great ease. The Makefile can be copied and used as is. Makefile can be customized by editing .env file. The .env file contains values for some important environment variables.
.env file
The comments above make the .env file variables self evident.
scripts folder
The scripts folder contains scripts that help the application build. Its structure is shown below:
├── LICENSE
├── Makefile
├── README.md
├── make.autocomplete
└── scripts
├── docker-deploy
│ ├── Dockerfile
│ └── docker-build.sh
├── prepare-dependencies
│ ├── copy-configs.sh
│ ├── copy-tests.sh
│ ├── gen-error.sh
│ ├── generate-dependencies-go.sh
│ └── generate-main-test-go.sh
├── release
│ ├── increment-tag.sh
│ ├── make-hotfix-branch.sh
│ └── merge-hotfix-to-master.sh
├── swagger
│ ├── swagger-generate.sh
│ └── templates
│ ├── header.gohtml
│ └── op.gohtml
└── test
└── test.sh
Explaining the files
The Makefile.sample is useful to create makefiles. A subset of commands can be picked up from this file for typical GO projects. (it is useful beyond WeGO projects)