vscode-extensions/archify-vscode-ext-sync
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: vscode-extensions/archify-vscode-ext-sync:main
vscode-extensions/archify-vscode-ext-sync:main
vscode-extensions/archify-vscode-ext-sync:v0.1.0
..
compare: vscode-extensions/archify-vscode-ext-sync:0570e2d55117cff0938d43c04534568ebf023fd4
vscode-extensions/archify-vscode-ext-sync:main
vscode-extensions/archify-vscode-ext-sync:v0.1.0
9 Commits
main .. 0570e2d551
Author SHA1 Message Date
Oleg Lukasonok 0570e2d551 README: coffee button at the top 2026-11-08 22:06:56 +02:00
Oleg Lukasonok 4d0c0382f1 README: buy me a coffee 2026-11-08 22:04:44 +02:00
Oleg Lukasonok 7dd28ee646 README: sign-in through 127.0.0.1, SSO without setup or passwords, the Argo CD template 2026-11-08 21:53:26 +02:00
Oleg Lukasonok 253635ffef Sign-in ends on a page with a button back to the editor 
Browsers open an app link only after a click on the page. With a live
identity provider session the whole sign-in ran without one, so the
redirect to vscode:// was dropped and the editor never got its code. The
page opens the editor at once and keeps a button for when that is held
back. Server 0.1.4, chart 0.1.5.
 2026-11-08 19:56:53 +02:00
Oleg Lukasonok 50d3d81b78 Sign-in goes straight to the identity provider 
With single sign-on there is nothing to choose, so /authorize redirects to
it; the page shows only when something went wrong there.
Server 0.1.3, chart 0.1.4.
 2026-11-08 19:43:07 +02:00
Oleg Lukasonok 1ab3d0b26a Single sign-on is the only way in when it is configured 
The sign-in page shows only the identity provider; password sign-in and
new local accounts are refused. Invites go through the identity provider.
Server 0.1.2, chart 0.1.3.
 2026-11-08 19:39:02 +02:00
Oleg Lukasonok 01a35f7ba6 Single sign-on servers need no setup step 
With single sign-on there is no first-start code and no /setup form: the
identity provider says who may sign in and who is admin, and the first
allowed sign-in makes the organisation, named after ARCHIFY_SYNC_NAME.
Server 0.1.1, chart 0.1.2.
 2026-11-08 19:34:48 +02:00
Oleg Lukasonok d8d46266dc Chart: postgresql.existingClaim for a database volume made outside the chart 2026-11-06 21:23:49 +02:00
Oleg Lukasonok 99778d7489 Archify Sync server, Dockerfile and Helm chart 
Rust server (axum, yrs, sqlx/PostgreSQL): live shared models over the y-websocket protocol, versions, browser sign-in with PKCE, invites, single sign-on through OIDC, metrics. Docker image on distroless, compose file, and a Helm chart with one pod, optional bundled PostgreSQL and secrets from existing Secrets.
 2026-11-06 12:06:59 +02:00
1 changed files with 0 additions and 2 deletions
Expand all files Collapse all files
README.md
-2
View File
@@ -6,8 +6,6 @@ The server behind live, shared models in [Archify Diagram Viewer](https://market
One Rust process and PostgreSQL.
How sharing, sign-in and setup fit together, as a walkthrough: [articles on Medium](https://medium.com/@root.at.skic).
## How it works
- **A space is one shared model.** Its content is a Yjs document with one `Y.Text` per model file, in the root map `files`, keyed by the path relative to the model root.