fix: default config #179
fix: default config #179
Conversation
| "@id": "urn:semcom-node:default:MemoryStore", | ||
| "@type": "MemoryStore", | ||
| "initialData": ["peers", []], | ||
| "initialData": ["storage", ["http://localhost:9000/metadata/"]] |
There was a problem hiding this comment.
If I understand correctly; this config is used to start the repository in production. If so; wouldn't this break something? Because I presume there's no pod server available in production on this uri.
There was a problem hiding this comment.
Hm, the point is there should be a pod server deployed with it.
There was a problem hiding this comment.
(or in any case, there should somewhere be a pod server to which this points, where the metadata is stored)
There was a problem hiding this comment.
Could we use an in-memory store as fallback?
There was a problem hiding this comment.
There was an inmemory config, but it does not yet work with the sync part.
There was a problem hiding this comment.
Might be a justifiable trade-off in this specific case?
There was a problem hiding this comment.
The problem is that, since it does not include the sync handlers, the launch code fails when those are not found.
There was a problem hiding this comment.
Maybe we could solve that with a boolean config variable?
There was a problem hiding this comment.
Wouldn't it be better just to deploy a pod server with it? That is also the only way it's really useable (with the ability to upload new components with oidc auth etc.)
No description provided.