Register endpoint, mail, tokens, #489 #254 #544

Author: joepio

.vscode/tasks.json

@@ -15,6 +15,23 @@
 			"group": "build",
 			"problemMatcher": []
 		},
+		{
+			"label": "watch atomic-server (cargo watch)",
+			"type": "shell",
+			"command": "~/.cargo/bin/cargo-watch",
+			"args": [
+				"--",
+				"cargo",
+				"run",
+				"--bin",
+				"atomic-server",
+				"--",
+				"--env-file",
+				"server/.env",
+			],
+			"group": "build",
+			"problemMatcher": []
+		},
 		{
 			"label": "test atomic-server (cargo nextest run)",
 			"type": "shell",

CHANGELOG.md

@@ -7,13 +7,18 @@ See [STATUS.md](server/STATUS.md) to learn more about which features will remain
 
 ## UNRELEASED
 
+- New sign up / register flow. Add `/register` Endpoint #489 #254
 - Add multi-tenancy support. Users can create their own `Drives` on subdomains. #288
-- Add `/register` Endpoint #489 #254
 - Refactor URLs. `store.self_url()` returns an `AtomicUrl`, which provides methods to easily add paths, find subdomains and more.
 - Add support for subdomains, use a Wildcard TLS certificate #502
 - Improve query performance, refactor indexes. The `.tpf` API is deprecated in favor of the more powerful `.query`. #529
 - Improved error handling for HTTPS initialization #530
 - Add `--force` to `atomic-server import` #536
+- Email support. Connect to external SMTP servers. #276
+- Basic plugin support through Endpoints. For now only works if you use `**Atomic**-Lib` as a library. Add your plugins by calling `Db::register_endpoint`.
+- Allow parsing `.env` files from custom locations using the `--env-file` flag.
+- Plugins support `tokio`, so you can spawn async tasks from plugins.
+- Add JWT token support, used for emails and registration #544
 - Fix index issue happening when deleting a single property in a sorted collection #545
 - Update JS assets & playwright
 - Fix initial indexing bug #560

CONTRIBUTE.md

@@ -26,7 +26,7 @@ Check out the [Roadmap](https://docs.atomicdata.dev/roadmap.html) if you want to
   - [Drill](#drill)
 - [Responsible disclosure / Coordinated Vulnerability Disclosure](#responsible-disclosure--coordinated-vulnerability-disclosure)
 - [Releases, Versioning and Tagging](#releases-versioning-and-tagging)
-  - [Including JS app_assets](#including-js-app_assets)
+  - [Including JS app\_assets](#including-js-app_assets)
   - [Publishing manually - doing the CI's work](#publishing-manually---doing-the-cis-work)
     - [Building and publishing binaries](#building-and-publishing-binaries)
     - [Publishing to Cargo](#publishing-to-cargo)
@@ -43,7 +43,8 @@ Since `atomic-server` is developed in conjunction with the typescript / react `a
 - Clone [`atomic-data-browser`](https://github.com/atomicdata-dev/atomic-data-browser) and run it (see readme.md, basically: `pnpm start`)
 - Visit `https://localhost:8080` (default)
 - Visit your `localhost` in your locally running `atomic-data-browser` instance: (e.g. `http://localhost:8080/app/show?subject=http%3A%2F%2Flocalhost`)
-- use `cargo watch -- cargo run` to automatically recompile `atomic-server` when you push new assets using `pmpm build-server` in `atomic-data-browser`. This can be useful if you're debugging specific features that you can't reproduce while the front-end is hosted in vite.
+- use `cargo watch -- cargo run --bin atomic-server -- --env-file server/.env` to automatically recompile `atomic-server` when you update code or JS assets.
+- If you want to debug emails: `brew install mailhog` => `mailhog` => `http://localhost:8025`
 
 ## IDE setup (VSCode)