Open Source event scheduling software for conventions
If a cookie is signed for one purpose, but the server also uses a differently named signed cookie name for another purpose, then it's possible for a malicious client to substitute the value of one signed cookie with the value of another and have it pass the signature check. Include the name of the cookie when computing the signature so that no cookies signed for example for "user_session" can be used as a value for a hypothetical "admin_session" cookie. |
||
---|---|---|
.forgejo/workflows | ||
.vscode | ||
assets | ||
components | ||
composables | ||
middleware | ||
pages | ||
public | ||
server | ||
shared | ||
utils | ||
.dockerignore | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
app.vue | ||
Dockerfile | ||
error.vue | ||
generate-keys.mjs | ||
index.d.ts | ||
nuxt.config.ts | ||
package.json | ||
pnpm-lock.yaml | ||
README.md | ||
tsconfig.json |
Nuxt Minimal Starter
Look at the Nuxt documentation to learn more.
Setup
Make sure to install dependencies:
# npm
npm install
# pnpm
pnpm install
# yarn
yarn install
# bun
bun install
Development Server
Start the development server on http://localhost:3000
:
# npm
npm run dev
# pnpm
pnpm dev
# yarn
yarn dev
# bun
bun run dev
Production
Build the application for production:
# npm
npm run build
# pnpm
pnpm build
# yarn
yarn build
# bun
bun run build
Locally preview production build:
# npm
npm run preview
# pnpm
pnpm preview
# yarn
yarn preview
# bun
bun run preview
Check out the deployment documentation for more information.