ForkbombEu / DIDroom_microservices

DIDroom credential issuer part of Forkbomb's SSI solution
1 stars 0 forks source link

Refactoring folder structure for update of the microservices #127

Open andrea-dintino opened 5 months ago

andrea-dintino commented 5 months ago

Issue with updates

Currently, when the microservices are first deployed, the autorun creates secret keys, public keys and requests a DID. The output of this, is stored in a file inside the microservice folder. This makes it hard to update the microservices, as you never know for sure what happens with the secret keys when you update.

Solutions

The secret keys have to be stored in a folder inside /config that has, as name the endpoint of the microservice (e.g.: https://issuer1.zenswarm.forkbomb.eu/credential_issuer )

matteo-cristino commented 5 months ago

Unfortunately I don't think all this can be handle in slangroom autorun contracts since FILES_DIR should point to the root of the folder in order to be able to consistely read the well-knowns (that are also updated in the autorun contracts) and for safety reason slangroom can only read and write inside FILES_DIR (can not exit it with .. or by giving it an absoulte path /home/...).

Thus all this stuff should be done by an external script at the end of make announce command I think

puria commented 4 months ago

You can use a lot of tricks, don't worry... first of all we can think of having mv/cp/ls/fsutils in general in slangroom. Secondly we can use already https://dyne.org/slangroom/statements/#shell-plugin! Whenever something you miss in limited slangroom actions!

matteo-cristino commented 4 months ago

Not totally clear point 3 for me. The first two are done: