Interaction between CLI and Server about atomic-server HOT 4 CLOSED

Besides storing personal data, it might make sense to use the Server as a personal cache for data that you use.

The CLI setup process could be initiated when a write command new or delta is called.

We might need a different Storelike implementation for the CLI, since mutations are to be executed somewhere else.

from atomic-server.

Relates to authentication #13

from atomic-server.

One of the things that I want to do, is edit some existing field. But what kind of behaviour would make most sense in a CLI setting?

• Set the new stringified content in your cli command: atomic-cli set myresource someprop somenewval. Seems kind of inconvenient, but easy to build. I could add set, destroy and remove methods - same as in Commits.
• Select a property, open your favorite text editor, save and exit! A commit will be dispatched. Here's some thoughts on how to do that.-
• Select a resource, show some fancy form-editor like GUI and edit things. Less cli-like, but probably powerful
• Atomic Console! Maybe even allow for some cool ORM-like syntax mything.set(description, "hi there")

from atomic-server.

Added some cool stuff to the CLI, and hid non-functioning commands that don't interact with server yet:

• tpf #35
• new
• validate (should be removed?)
• commit (should be removed?)

from atomic-server.