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.
22 lines
1.0 KiB
JavaScript
22 lines
1.0 KiB
JavaScript
"use strict";
|
|
|
|
module.exports = function (it) {
|
|
const { pattern } = it;
|
|
|
|
return `
|
|
You are linting "${pattern}", but all of the files matching the glob pattern "${pattern}" are ignored.
|
|
|
|
If you don't want to lint these files, remove the pattern "${pattern}" from the list of arguments passed to ESLint.
|
|
|
|
If you do want to lint these files, explicitly list one or more of the files from this glob that you'd like to lint to see more details about why they are ignored.
|
|
|
|
* If the file is ignored because of a matching ignore pattern, check global ignores in your config file.
|
|
https://eslint.org/docs/latest/use/configure/ignore
|
|
|
|
* If the file is ignored because no matching configuration was supplied, check file patterns in your config file.
|
|
https://eslint.org/docs/latest/use/configure/configuration-files#specifying-files-with-arbitrary-extensions
|
|
|
|
* If the file is ignored because it is located outside of the base path, change the location of your config file to be in a parent directory.
|
|
`.trimStart();
|
|
};
|