just going to build and push locally instead of gitea actions
This commit is contained in:
13
README.md
13
README.md
@@ -30,12 +30,13 @@ npm run dev
|
||||
|
||||
In simulated mode, SharePoint and ACC are in-memory stand-ins. A demo project is created at startup, filled with sample files, and edited at random every 45 seconds so there's something to watch. One file (`Corrupt model.rvt`) is always rejected, so the issues list has something in it. Nothing persists: a restart starts over.
|
||||
|
||||
| Command | What it does |
|
||||
| --------------- | ------------------------------------------------------------------------------------------------------------------- |
|
||||
| `npm test` | Unit and integration tests (Vitest) |
|
||||
| `npm run check` | Type check |
|
||||
| `npm run lint` | Prettier + ESLint |
|
||||
| `npm run build` | Production build into `build/` (`node build` runs it; run it from the repo root so `drizzle/` migrations are found) |
|
||||
| Command | What it does |
|
||||
| ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
|
||||
| `npm test` | Unit and integration tests (Vitest) |
|
||||
| `npm run check` | Type check |
|
||||
| `npm run lint` | Prettier + ESLint |
|
||||
| `npm run build` | Production build into `build/` (`node build` runs it; run it from the repo root so `drizzle/` migrations are found) |
|
||||
| `npm run image:publish` | Checks, builds and pushes the Docker image to the Gitea registry (see the runbook) |
|
||||
|
||||
To try the Docker image locally: put `ADMIN_USERNAME`, `ADMIN_PASSWORD`, `SESSION_SECRET`, `SYNC_BACKEND=simulated` and `ORIGIN=http://localhost:3000` in `.env`, then run `docker compose up -d --build`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user