dtoro
d4d99a7473
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.
lz-string
LZ-based compression algorithm for JavaScript
Warning (migrating from version 1.3.4 - nov 2014)
Files have changed locations and name since a recent release. The new release file is in libs/lz-string.min.js (or in libs/lz-string.js if you don't care for the minified version)
Sorry about the mess in other repos. This will not happen again.
Note on server side
If you are using one of the ports of lz-string to decode on the server what was encoded in the browser, you might want to use version 1.3.7 as the version 1.3.8 introduced a slight change in the encoding. While the JS versions are completely cross-compatible, the PHP, Go, ... versions might not be as forgiving.
Install via npm
$ npm install -g lz-string
$ lz-string input.js > output.txt
Home page
Home page for this program with examples, documentation and a live demo: http://pieroxy.net/blog/pages/lz-string/index.html
Other languages
This lib has numerous ports to other languages, for server side processing, mostly. Here they are:
- Java: by Diogo Duailibe
- Java: by rufushuang, with base64 support and better performances
- C#: by Jawa-the-Hutt
- C#: by kreudom, another implementation in C#, more up to date
- PHP: by nullpunkt
- Python3: by eduardtomasek
- Another Python: by marcel-dancak
- Go I helped a friend to write a Go implementation of the decompression algorithm
- Go Austin wrote the decompression part as well
- Elixir by Michael Shapiro
- C++/QT by AmiArt
- C++ by Andrey Krasnov, another implementation in C++11
- VB.NET by gsemac
- Salesforce Apex (Java like language): bilal did the port
- Kotlin: from Zen Liu
- Dart: from skipness
- Haxe: from markknol
- Rust: from adumbidiot