This file has been copied from WEBSITE-TEMPLATE. Keep modifications minimal and improve the original instead. Project specific conventions are located in README.md.
Table of contents:
- Node.js (LTS version)
- Docker Compose
- Some editor plugins depending on technology (e.g. ESLint and Prettier for JavaScript/TypeScript)
Install mandatory libraries on host:
npm install
Install additional libraries on host for autocompletion/linting on editor (optional):
npm run install-dev
Set up environment variables required by docker-compose.yaml
:
. ./taito-config.sh
Start containers defined in docker-compose.yaml
:
docker-compose up
Open the application on browser:
http://localhost:9999
Use npm
, docker-compose
and docker
normally to run commands and operate containers.
If you would like to use some of the additional commands provided by Taito CLI also without using Taito CLI, first run the command with verbose option (taito -v
) to see which commands Taito CLI executes under the hood, and then implement them in your package.json
or Makefile
.
Instructions defined in CONFIGURATION.md apply. You just need to run commands with npm
or docker-compose
directly instead of Taito CLI. If you want to setup the application environments or run CI/CD steps without Taito CLI, see the following instructions.
- Run taito-config.sh to set the environment variables for the environment in question (dev, test, stag, canary, or prod):
export taito_target_env=dev . taito-config.sh
- IF MONITORING IS REQUIRED:: Run terraform scripts that are located at
scripts/terraform/
. Usescripts/terraform/common/backend.tf
as backend, if you want to store terraform state on git. Note that the terraform scripts assume that a cloud provider project defined bytaito_resource_namespace
andtaito_resource_namespace_id
already exists and Terraform is allowed to create resources for that project. - IF BASIC AUTH IS REQUIRED: Set Kubernetes secret values with
kubectl
. The secrets are defined bytaito_secrets
inscripts/taito/project.sh
, and they are referenced inscripts/helm*.yaml
files.
You can easily implement CI/CD steps without Taito CLI. See continuous integration and delivery chapter of Taito CLI manual for instructions.