atomic-server
atomic-server copied to clipboard
An open source headless CMS / real-time database. Powerful table editor, full-text search, and SDKs for JS / React / Svelte.
Currently, functions that authentication (e.g. `Store::get_resource_extended`) take an `Opion`. If passed `None`, they skip authentication. If the user does not have an `Agent`, we pass `PublicAgent`. I think I made...
See https://github.com/atomicdata-dev/atomic-data-rust/actions/runs/3096932713/jobs/5013257684, `check skipped`. Currently doesn't even allow for manual starts. Maybe it has something to do with the name `main.yml` differing from the name of the action `Lint &...
At some point, we'll want to send e-mails. For notifications, registrations, or newsletters, for example. ## Usecases for sending mails - **E-mail confirmation** for Agents. On creating an Agent, send...
After creating the bundles, the signing fails in the CI: https://github.com/atomicdata-dev/atomic-data-rust/actions/runs/2984072526/jobs/4784311358#step:7:831 ``` Finished 3 bundles at: /Users/runner/work/atomic-data-rust/atomic-data-rust/target/release/bundle/macos/Atomic Server.app /Users/runner/work/atomic-data-rust/atomic-data-rust/target/release/bundle/dmg/Atomic Server_0.32.1_x64.dmg /Users/runner/work/atomic-data-rust/atomic-data-rust/target/release/bundle/macos/Atomic Server.app.tar.gz (updater) Error A public key has been found,...
I'd like Collections to update live. The server is keeping track of which user has which Collection opened, and it knows every Commit and updated Atom that crosses it. Some...
Instead of relying on error-prone match statements like [these](https://cs.github.com/atomicdata-dev/atomic-data-rust/blob/7b819b8e6661c5df58eeadc1435d14ad9a9b16a6/lib/src/collections.rs#L362), we could use a library like [`serde_qs`](https://docs.rs/serde_qs/latest/serde_qs/) to parse query strings. Current implementation issues: - Wrong query params are ignored instead...
- Client `SUBSCRIBE`s to some resource, and they have the correct `read` permissions - The `read` permission is taken away - Currently, the existing `WebSocketConnection` will _not_ be aware of...
Creating a new user / Agent is currently always done using Invites. That flow doesn't make a lot of sense for most usecases: users will probably want their own workspace...
Currently, the `all_resources` function returns a `Vec` containing, well, all resources. That means that the maximum amount to export is coupled to the memory of the server. This effectively breaks...
I just had a problem using the Document invite, because apparently one of the Commits is missing. ``` Error opening https://atomicdata.dev/invites/1?public-key=dlOABAaykKn7F5KTOYK3gOuxSiMOLzeljtNLmcnUWNs%3D Unable to get commits for https://atomicdata.dev/document/pnf5jlv3r2f. Resource not found....