A central space to collate all Capco Engineering information sources.
View Demo
·
Report Bug
·
Request Feature
Contents
A central space to collate all Capco Engineering information sources. Aimed at clients, candidates and internal employees alike.
To get a local copy up and running follow these simple steps.
A number of local dependencies are required. To review the local dependencies:
- When using MacOS run
make requirements - otherwise run
cat Brewfileto inspect the requirements
If additional dependencies are required they should be added to Brewfile, for more details please review the official brew bundle documentation here.
This repo follows the principle of minimal manual setup of the local development environment.
A make target has been provided for simplicity make init, the make file can be inspected for more details.
# use the folder name as the repo name
make init
# explicitly pass in the repo name (e.g. my-service)
make repo=my-service initIf at any point the repo name needs to be changed then the make rename target can be called.
make repo=my-service renameUse this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.
For more examples, please refer to the Documentation
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
If you would like to contribute to any Capco Digital OSS projects please read:
Distributed under the MIT License. See LICENSE for more information.