Tim Ermilov

Would love to have this feature. IMO just a scheduled restore-merge-backup to selected file in Google Drive would be sufficient (at least for the start).

I've added a small comment to db code. IMO file-based approach would be easier to maintain. > exoframe.json is missing (first deploy) => cli asks for config generation, creates exoframe.json...

> Main reason I suggested this change was to somehow remove the /update endpoint and handle all requests by the /deploy endpoint. This separation exists for a reason - there...

Sure. There are two cases here: 1. Scaling as you've said. Since there's no other way to scale right now 😅 2. Deploying new immutable versions of project (e.g. we...

This changes the behavior quite a bit. It should be behind a flag IMO 🤔

I'm not saying exoframe should mimic all docker commands, I'm just saying this particular one should be behind an opt-in flag. Removing all dangling images has quite a severe impact...

@FDiskas yeah, `--all` (short `-a`) would be perfect

@nelix I still think a specialized Subject would do the trick. Essentially, on Subject init it should spawn new worker and wrap `postMessage` as `onNext` and `onmessage` as incoming data....

Example react app: https://github.com/turrisjs/turris-example-chat

@nelix that's an interesting idea, will probably add it to examples. thanks!