1. create app in webui
2. add lektor component to the app definition
<think of different versions :|>
3. create a git repo for application
4. think of creating generic application there
cicd_service, appsservice - think which microserver should do that
1. expose different Dockerfiles for different apps, so something like: curl cicd_service/api/app1_lektor/dockerfile or curl cicd_service/api/dockerfile/lektor
difference is, if we should configure a gitrepo to point to specific docker file, or gitrepo should point to microservice which will dynamically check the application configuration to return default or custom dockerfile.
using microservice will reduce need to reconfigure gitlab
2. same goes with gitlab-ci. repo should point to cicd_service/api/app1_lektor/gitlab-ci.yml
let's use
cicd_server/api/v1/gitlabci/?org=test-org&app=app1&component=lektor becase it would be easier to split it someday if neede
maybe support also cicd_service/api/v1/gitlabci/test-org/app1/lektor if it will be straightforward
charts
think if I want to build chart everytime we have a new version of app, or one chart, and I want to manipulate values only during deployment.
or one default chart, downloaded using dependency, and creating chart for every app version, but chart will only have Chart.yaml with dependency of default chart and values for this specific version
gitlab-ci
microservice should prepare a gitlab-ci specific for every applicatoin/component, based on the selected CICD model - ex. deploy every branch as a preview app etc
gitlab operator and cicd_microservice should operate on Application custom resource (single point of configuration)
Updated by