Restructuring of OTP repository
Opened this issue · 5 comments
One or two repositories for old / new OTP instance?
I discussed this with @clezag and we decided to use only the existing repository, by using different branches for the new development.
The new branches will then be merged to the main branches, once the new development is done.
@dulvui And would you like to use the same mechanism for starting OTP (jar + Java) or should I set it up with the upstream container image?
@leonardehrenfried We do not really have a preference here, whatever is easier for you to develop and easier for us to maintain.
Ok. My suggestion is that I start with a first draft with what is easy for me and together we will figure out the details of how exactly the repo needs to be made runnable and deployable.
We could, for example, aim to make it an ansible playbook which makes it easy to deploy it on any Linux server.
Great, that works for us!
We actually already have an ansible deployment for our docker applications, that is used also in this repository.
The configuration of the playbook is available here https://github.com/noi-techpark/odh-mentor-otp/tree/main/infrastructure/ansible and the playbook itself here https://github.com/noi-techpark/ansible-docker-deployment/tree/master
So I think that is not needed, you can simply change the otp Dockerfile as you need and then that docker container gets deployed to ours servers.