Closed NicolasMahe closed 5 years ago
This issue should be closed as the goal is to remove the system service and use directly the cosmos module or processes build on top on it. @antho1404 can you confirm by closing this issue
Yes system services will be removed when the full network is implemented. We can add it later again if needed.
I would suggest to simplify the override of the env of the system services. Instead of having to define one variable per env, we could pass ALL envs in one variable as a JSON encoded array. The Engine would have to decode it to start the instances. Maybe we could go further and create a generic system based on JSON encoded string or a file that is transform to an asset during the compilation, that contains all info about the SystemService. Like this we will not have to update the config package to add or update system services. @krhubert suggested something like this on Discord.
Also, why not compiling the service also in the script
dev
? likescripts/build-engine.sh
is doing? because of optimization?It would definitely make sense to move the system services into their own repo and use the mesg-cli to compile them during the build of the Engine.
Related to PR https://github.com/mesg-foundation/engine/pull/1087