Agility Installation Guide

prerequisites for installation frontmanager installation configuration of tenants and applications central it infrastructure access data (git credentials, nexus credentials) kubectl configured for the environment where it will be deployed (this includes the project's environment variables, with their appropriate access data) tools database (postgresql 13+ / sqlserver 2019+ / oracle 12c+) keycloak (must already be installed as frontmanager depends on it) miniio (must already be installed as frontmanager depends on it) kafka (must already be installed as frontmanager depends on it) installation steps steps to install agility clone the hyper kanban api repository git clone http //gitlab centralit io/centralit/hyper platform/hyper kanban api git enter the folder where the project was cloned and check out the devel branch git checkout devel run step 1 migrations run step 2 deploy step 1 migrations the migrations sh script processes migrations for multiple databases according to the settings present in a migrations file in json format which by default is migrations config json in the same folder as the script migrations config json file the file must follow the structure below where the attributes of each tenant that follows example example file with two tenants ( run2biz and tenant1 ) for the hyper kanban api application development environment (this application) running the migrations sh script how to use /migration sh \<tenantname> example /migration sh run2biz tenant1 step 2 deploy via gitlab ci for some environments, there is already automation in gitlab, where simply merging to the branch already triggers the deployment of the product (apps centralit, labcentral) these are the cases of branches with prefix deploy/ gitlab ci example on the deploy/apps centralit com br branch manual via kubectl script to do it manually, the template files for the environment in question must be created configmap template yml deployment template yml ticket template yml service template yml in this case, the only file to be updated would be the configmap template yml (environment variables), the rest of them follow the same pattern and content the files must be created in the k8s folder, in a new folder named after the environment after that, the k8s apply sh script must be executed passing which environment will be updated with deploy ex k8s apply sh dev eveo updating directly in rancher in cases where the kubernetes environment already exists and it is only necessary to update the package, just change the package path to the one available in the registry