mirror of
https://github.com/aliasvault/aliasvault.git
synced 2026-07-31 01:07:06 -04:00
7a6c6c084c
Bumps the npm_and_yarn group with 1 update in the /apps/browser-extension directory: [adm-zip](https://github.com/cthackers/adm-zip). Bumps the npm_and_yarn group with 1 update in the /core/models directory: [brace-expansion](https://github.com/juliangruber/brace-expansion). Bumps the npm_and_yarn group with 1 update in the /core/vault directory: [brace-expansion](https://github.com/juliangruber/brace-expansion). Removes `adm-zip` Updates `brace-expansion` from 1.1.16 to 5.0.8 - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](https://github.com/juliangruber/brace-expansion/compare/v1.1.16...v5.0.8) Updates `brace-expansion` from 1.1.16 to 5.0.8 - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](https://github.com/juliangruber/brace-expansion/compare/v1.1.16...v5.0.8) --- updated-dependencies: - dependency-name: adm-zip dependency-version: dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: brace-expansion dependency-version: 5.0.8 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: brace-expansion dependency-version: 5.0.8 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
AliasVault documentation
The documentation site for AliasVault (docs.aliasvault.com), built with Docusaurus.
Run locally (development)
Hot-reloading dev server:
npm ci # first time, or when dependencies change
npm start # serves at http://localhost:5190
Run locally with Docker
Serves the production build through nginx, exactly as it runs in production. The site must be built first, then Docker just serves the static output:
npm ci && npm run build # produces ./build
docker compose up -d --build # serves at http://localhost:5191
docker compose down # stop
Deployment
Deployment is automated — see .github/workflows/deploy-docs.yml.
It builds the static site in CI and ships it to the docs server:
- Automatically on every published GitHub release.
- Manually via the Actions tab → Deploy docs → Run workflow, where you can choose the branch or tag to deploy from.
Server-side setup is documented internally.