feat: Phase 1 — extract the client (web SPA + desktop) to dtoro/oikos-web
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
This commit is contained in:
70
web/node_modules/@vincjo/datatables/README.md
generated
vendored
Normal file
70
web/node_modules/@vincjo/datatables/README.md
generated
vendored
Normal file
@@ -0,0 +1,70 @@
|
||||
<div align="center">
|
||||
<img align="center" src="./static/logo.svg" alt="logo" width="172"/>
|
||||
<p align="center">
|
||||
<h1 align="center" style="font-size:32px;margin:0;border:none;">svelte simple datatables</h1>
|
||||
<p style="color:#eee">A powerful toolkit for building datatable components.</p>
|
||||
<img src="https://img.shields.io/badge/svelte-runes-v2?color=%23c2185b" alt="any text"/>
|
||||
<img src="https://img.shields.io/github/license/vincjo/datatables?color=c2185b" alt="last commit"/>
|
||||
</p>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
# Docs
|
||||
Streamline your data workflow with a robust API providing advanced features while reducing code complexity.
|
||||
|
||||
:globe_with_meridians: **[vincjo.fr/datatables](https://vincjo.fr/datatables)**
|
||||
|
||||
|
||||
|
||||
# Install
|
||||
|
||||
```apache
|
||||
npm i -D @vincjo/datatables
|
||||
```
|
||||
|
||||
|
||||
# Smooth transition from v1 to v2
|
||||
|
||||
In order to make the migration process a little easier, v1 is embed in “legacy” namespace so you will have the opportunity to upgrade your components progressively by simply modifying imports.
|
||||
|
||||
```diff
|
||||
- @vincjo/datatables
|
||||
+ @vincjo/datatables/legacy
|
||||
|
||||
- @vincjo/datatables/remote
|
||||
+ @vincjo/datatables/legacy/remote
|
||||
```
|
||||
<br>
|
||||
|
||||
|
||||
# Sample code
|
||||
|
||||
```svelte
|
||||
<script lang="ts">
|
||||
import { TableHandler } from '@vincjo/datatables'
|
||||
import { someData } from './data'
|
||||
|
||||
const table = new TableHandler(someData, { rowsPerPage: 50 })
|
||||
</script>
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>First name</th>
|
||||
<th>Last name</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
{#each table.rows as row}
|
||||
<tr>
|
||||
<td>{row.first_name}</td>
|
||||
<td>{row.last_name}</td>
|
||||
</tr>
|
||||
{/each}
|
||||
</tbody>
|
||||
</table>
|
||||
```
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user