Joep Meindertsma

@AlexMikhalev If you feel like it, sure! I have no clue where to find a solution for this. Note that for me there is no direct reason to make this...

I might explore this further, but for now I don't think it has serious advantages over a regular setup.

I think this is a duplicate of #324, right?

Thanks!

A different approach to multi-node, is FAAS. Convert all logic to stateless functions. Has some interesting benefits to scalability - no longer needed to copy instances and all their logic....

@AlexMikhalev has made some interesting progress on having a multi-node Atomic-Server setup. See the [`aws-ops`](https://github.com/applied-knowledge-systems/aws-ops/) repo. He suggests: ## One docker instance per user - use Github Username to create...

Another approach: ## Link Drives to Nodes - Every Drive (workspace) is linked to one specific machine. - Requires only minimal coordination between nodes. With a smart URL strategy, we...

Yeah it's definitely a weak spot, although I'm not entirely sure how I can provide enough convenience with a tool like keyring. Users should be able to read and set...

## The risks The private key is created by the server (if none existing is found) and used to sign all changes that the server makes by itself. If the...

You're right, thanks! Still need a solution for this.