MESG Development

Core This is the place where all the high level conversations about the core happen. We discuss about different features that might be implemented in MESG Core or the way to architecture the code. Also related to the development of the API for the Services or Applications created with MESG.
About the MESG Development category [MESG Development] (1)
Add more detailed data in the mesg.yml [Core] (9)
Configuring Services with Deploy-Time or Run-Time Arguments [Core] (12)
Improve relation between SID and Hashes [Core] (4)
Don't reserve 'service' name to make it able be used in config file as a dependency key [Core] (2)
Track service deployed time [Core] (1)
Improve Docker config injected in Core's container [Core] (1)
Add more validation on the data [Core] (1)
Better management of errors in the API [Core] (2)
Make a websocket server to expose the APIs [Core] (1)
Filter events and results by data [Core] (1)
Add autoupdate or update command [Core] (1)
Replace leveldb with an other database [Core] (1)
Move logic of stopping core and services to api or daemon package [Core] (1)
Provide a way to start system services as image [Core] (1)
Start docker services in parallel [Core] (1)
Service.configuration is duplicated in Service.dependencies [Core] (1)
Default behavior of the deletion of services' volumes [Core] (3)
Introducing Workflow Files [MESG Development] (12)
New Go version 1.11 [Core] (3)
Go back to version 0.X.X [Core] (4)
Combine service and importer structs into one [Core] (4)
Milestone v0.6 [Core] (3)
Protobuf: change data type [Core] (1)
Fixed Service ID/Name & Service Update, Create Feature [MESG Development] (5)
Brainstorming Service's Alias/SID/Versions and Data Volumes [Core] (12)
Refactoring list [MESG Development] (6)
Ability to Define Tag Fortmats in mesg.yml [MESG Development] (3)
Support Named Services for Communication of Services in the Shared Network [MESG Development] (6)
[Plugin system] Use MESG service to develop MESG core ( 2 ) [Core] (27)