adminandClaude Opus 5.5
043c224cc3
The editor gets a name of its own that fits beside Brandmauer, Glutspeicher and Feuerwehr. This is stage 1, 2 and 4 of #422: the name, the URL and the stored state in the browser. Repository, CI runners, containers and the GAME_MAKER_* variables follow in stage 3. - All paths come from SITE_PATH in src/core/site.ts: the API endpoint, the data folders, the play page and the base in vite.config.ts. A later move is one line instead of fifteen. - The window title, the sign-in screen, the playground and the README say Feuerwerk. The package, __feuerwerkPlay, the take worklet and the writing app in Ogg and Matroska follow. - The session cookie is now feuerwerk_session, so everyone signs in once more. - localStorage keys are now feuerwerk.*. moveOldStoredKeys copies the old game-maker.* keys over on the first start, so settings, panel sizes and save games survive. - tools/ci/serve.sh serves the build under /feuerwerk/. The variable GAME_MAKER_BASE_URL keeps its name until stage 3. Outside the repository, nockal.com/feuerwerk/ is a second symlink to the same tree. nginx sends the bare /game-maker/ folder there with a 301. Everything else under /game-maker/ is still served directly, so shared play links and the API keep working. Finding: when nginx redirects a path without a trailing slash or with a query, the Brandmauer answers with its own 307 to the same URL plus a slash, placed after the query. A play link would lose its token that way, which is why only the bare folder is redirected. Tests: - Gate on melektaus-atx: CHECK EXIT 0, 307 files, 4756 tests (4 new in site.test.ts). - Counter-check: when the migration misses the old prefix, 3 of the 4 new tests fail. - e2e 60 under /feuerwerk/: ALL PASSED, 20 checks. - From outside: /feuerwerk/ 200, /game-maker/ 301, an old play link 200. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
81 lines
2.6 KiB
TypeScript
81 lines
2.6 KiB
TypeScript
import { copyFileSync } from 'node:fs';
|
|
import { dirname, resolve } from 'node:path';
|
|
import { fileURLToPath } from 'node:url';
|
|
import { defineConfig, type Plugin } from 'vite';
|
|
import { publishPlugins } from './tools/lib/plugins.mjs';
|
|
import { SITE_PATH } from './src/core/site';
|
|
|
|
const __dirname = dirname(fileURLToPath(import.meta.url));
|
|
|
|
/**
|
|
* The workspace folder itself is what nginx serves under https://nockal.com/feuerwerk/.
|
|
* The Vite source pages live in `web/`: `index.html` is the editor, `play.html` a released game
|
|
* (#266). The build writes hashed assets into `dist/` and this plugin copies the built pages to the
|
|
* folder root, so that the site URLs load the production bundles while `api/` and `data/` sit next
|
|
* to them.
|
|
*/
|
|
const PAGES = ['index.html', 'play.html'];
|
|
|
|
function publishPages(): Plugin {
|
|
return {
|
|
name: 'feuerwerk:publish-pages',
|
|
apply: 'build',
|
|
closeBundle() {
|
|
for (const page of PAGES) copyFileSync(resolve(__dirname, 'dist', page), resolve(__dirname, page));
|
|
},
|
|
};
|
|
}
|
|
|
|
/**
|
|
* Editor plugins are loaded from `data/plugins/`, which is not in the repository; the ones that
|
|
* ship with it live in `plugins/` and are put there on every build. A file of the same name is
|
|
* replaced, anything else in the folder is left alone. Whether one runs is the open project's
|
|
* business, not the build's (#119).
|
|
*/
|
|
function shipPlugins(): Plugin {
|
|
return {
|
|
name: 'feuerwerk:publish-plugins',
|
|
apply: 'build',
|
|
closeBundle() {
|
|
publishPlugins(__dirname);
|
|
},
|
|
};
|
|
}
|
|
|
|
export default defineConfig({
|
|
root: 'web',
|
|
base: `${SITE_PATH}dist/`,
|
|
publicDir: false,
|
|
plugins: [publishPages(), shipPlugins()],
|
|
build: {
|
|
outDir: '../dist',
|
|
emptyOutDir: true,
|
|
target: 'es2022',
|
|
sourcemap: true,
|
|
rollupOptions: {
|
|
input: Object.fromEntries(
|
|
PAGES.map((page) => [page.replace('.html', ''), resolve(__dirname, 'web', page)]),
|
|
),
|
|
},
|
|
},
|
|
server: {
|
|
port: 5175,
|
|
// During development the PHP API is served by the production nginx; proxy it.
|
|
proxy: {
|
|
[`${SITE_PATH}api`]: {
|
|
target: 'https://nockal.com',
|
|
changeOrigin: true,
|
|
},
|
|
},
|
|
},
|
|
test: {
|
|
root: '.',
|
|
include: ['tests/**/*.test.ts'],
|
|
environment: 'node',
|
|
// Unset locally, so vitest keeps its own guess (one worker per core). CI sets it while the
|
|
// gate runs next to the editor suite: the two jobs share four cores, and the suite measures
|
|
// text widths and frame counts, which a machine under full load reports differently.
|
|
maxWorkers: Number(process.env.GM_TEST_WORKERS) || undefined,
|
|
},
|
|
});
|