Let me clarify my ideas about structure of the mission I am engaged on.
The mission code repository encompass:
- Scrapy part – after all it serves to scrape information, course of it and calculate relations between information. It populates MySQL database.
- Django visualization part – it merely shows information saved in database utilizing many filters.
Proper now they’re deployed as two separated docker containers which works advantageous.
The concept of former collegues was to go additional with cut up and cut up additionally code repositories.
I can see potential means to create CI/CD per repository, so it would solely run checks/lintes/checks and ultimately will solely deploy container which really was modified. It will not run every little thing for different container which is okay(logical separation).
However as a result of they’re really engaged on identical database tables(Scrapy populates them, Django reads them) it appears to be like like overkill for me. I would wish to keep up two separate DB mannequin specs in sync in each repositories. Proper now Scrapy makes use of Django ORM for interplay with DB.
What do you suppose? Do you suppose it is value splitting code repository to 2 separated ones and hold in sync fashions in each of them? Or possibly not? Is there a method to set off/run Gitlab CI/CD course of for under affected container in single repository?