The new and improved OCL terminology service v2

1. sysctl -w vm.max_map_count=262144 #required by Elasticsearch
2. docker-compose up -d
3. Go to http://localhost:8000/swagger/ to benefit.

(use the docker exec command in a service started with docker-compose up -d)

1. Pylint (pep8):

   docker exec -it oclapi2_api_1 pylint -j2 core

   or

   docker-compose -f docker-compose.yml -f docker-compose.ci.yml run --rm api pylint -j0 core

2. Coverage

   docker exec -it oclapi2_api_1 bash coverage.sh

   or

   docker-compose -f docker-compose.yml -f docker-compose.ci.yml run --rm api bash coverage.sh

3. Tests

   docker exec -it oclapi2_api_1 python manage.py test --keepdb -v3

   or

   docker exec -it oclapi2_api_1 python manage.py test --keepdb -v3 -- core.sources.tests.tests.SourceTest

   or

   docker-compose -f docker-compose.yml -f docker-compose.ci.yml run --rm api python manage.py test --keepdb -v3

API_SUPERUSER_PASSWORD corresponde al password del usuario ocladmin.

ENVIRONMENT=development|production
API_BASE_URL=http://localhost:8000
API_SUPERUSER_PASSWORD=qwertyu
API_SUPERUSER_TOKEN=1df23g4h5j67zz

mkdir es-data/data
mkdir postgres/data
docker-compose up -d
docker exec -it oclapi2_api_1 python manage.py search_index --rebuild -f --parallel

docker volume rm oclapi2_es-data
docker volume rm oclapi2_postgres-data
docker rmi openconceptlab/oclapi2:development
docker rmi openconceptlab/oclapi2:production

• redis error: 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1

After modifying model you need to create migration files. Run:

docker-compose run --rm api python manage.py makemigrations

Make sure to commit newly created migration files.

In order to debug tests or api you can use PDB. Set a breakpoint in code with:

import pdb; pdb.set_trace()

Run tests with:

docker-compose run --rm api python manage.py test core.code_systems --keepdb -v3

Run api with:

docker-compose run --rm --service-ports api

Every build is a candidate for release.

In order to release please trigger the release build step in our CI. Please note that the maintenance version will be automatically increased after a successful release. It is desired only, if you are releasing the latest build and should be turned off by setting the increaseMaintenanceRelease variable to false on the Run stage "Release" popup in other cases.

A deployment release will be automatically created and pushed to the staging environment.

In order to increase major/minor version you need to set the new version in core/__init__.py. Alongside you need to login to our CI and update the next release version on a deployment plan here with the same value.

In order to deploy please trigger the deployment here. Please use an existing deployment release.