Create a common strategy for deployments

[genaris]

At the moment, we are managing deployments in separate GitLab repositories per module and environment, which is cumbersome and very hard to maintain.

We need to migrate these to GitHub and define a common structure and/or guidelines to make it easier to understand and as error prone as it can be.

For example, I think that we can do an approach like the one in Verana, where a number of modules are grouped together and different GitHub actions are used to update each. In 2060 I can identify at least three potential repositories:

• 2060-core-deploy: containing deployment scripts for DIDComm mediator, Message Pickup Repository, WebRTC Server for P2P, Indy VDR Proxy, Trust Service Resolver, etc.
• 2060-demos-deploy: Chatbot Demo, generic verifier using phone number credential, and other demos we may want to keep public
• unic.id-deploy: containing Issuer DTS, Verifier DTS, Vision service, matcher, WebRTC server, etc.

It would be good to start with UnicID deployment, since it is not already created and it could be a good example to experiment with.