1
0
Fork 0
Web app for the Arma 3 unit Polaris Task Force. Uses Next.js for client- and server-side rendering, with a Postgres database and some other neat libraries. https://arma.onyxsimple.com
Find a file
Z8MB1E be8e537385 feat(locker): add hover tooltip to wardrobe slot hotspots
- Wrap each wardrobe slot button with shadcn Tooltip component
- Show slot name and current item name on hover
- Use smooth fade-in/zoom-in animation from shadcn tooltip
- Position tooltip to the right of each hotspot with 8px offset
2026-08-02 18:52:45 -04:00
.vscode feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
public/images chore: update TODO.md and add soldier wardrobe images 2026-08-02 18:50:31 -04:00
src feat(locker): add hover tooltip to wardrobe slot hotspots 2026-08-02 18:52:45 -04:00
tests feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
Writerside feat: application staging deployment (ensure better commits after this) 2025-12-15 01:14:30 -05:00
.env.example feat(realtime): add game-tick SSE notification pipeline 2026-08-02 02:03:56 -04:00
.env.test feat: add LAST_UPDATED environment variable, update VersionOverlay to display last updated timestamp, and introduce patch script 2025-12-22 16:41:29 -05:00
.gitignore feat: initial commit 2025-10-15 14:03:31 -04:00
.npmrc feat: initial commit 2025-10-15 14:03:31 -04:00
.prettierrc.json feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
.yarnrc feat: initial commit 2025-10-15 14:03:31 -04:00
AGENTS.md docs: add dev server testing protocol to AGENTS.md 2026-08-02 14:32:55 -04:00
bun.lock feat(locker): add command palette search 2026-08-02 18:50:07 -04:00
bunfig.toml feat: add LAST_UPDATED environment variable, update VersionOverlay to display last updated timestamp, and introduce patch script 2025-12-22 16:41:29 -05:00
components.json feat: application staging deployment (ensure better commits after this) 2025-12-15 01:14:30 -05:00
docker-compose.yml feat: initial commit 2025-10-15 14:03:31 -04:00
Dockerfile feat: initial commit 2025-10-15 14:03:31 -04:00
drizzle.config.ts feat: application staging deployment (ensure better commits after this) 2025-12-15 01:14:30 -05:00
eslint.config.mjs feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
next.config.mjs feat: display app version using environment variable and add VersionOverlay component, add migration for new database tables 2025-12-22 16:07:48 -05:00
package.json feat(locker): add command palette search 2026-08-02 18:50:07 -04:00
playwright.config.ts feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
pnpm-lock.yaml feat(locker): add command palette search 2026-08-02 18:50:07 -04:00
pnpm-lock.yaml.bk fix: move Dashboard to frontend, pin dependencies in bun.lock to specific versions for stability 2025-12-17 15:15:07 -05:00
postcss.config.mjs feat: application staging deployment (ensure better commits after this) 2025-12-15 01:14:30 -05:00
README.md feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
test.env feat: initial commit 2025-10-15 14:03:31 -04:00
TODO.md chore: update TODO.md and add soldier wardrobe images 2026-08-02 18:50:31 -04:00
tsconfig.json feat: switch to Bun, add fonts and styling, update components and UI, add basic front-end 2025-12-16 23:26:52 -05:00
vitest.config.mts feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00
vitest.setup.ts feat: initial payload scaffolding 2025-10-24 02:07:13 -04:00

Payload Blank Template

This template comes configured with the bare minimum to get started on anything you need.

Quick start

This template can be deployed directly from our Cloud hosting and it will setup MongoDB and cloud S3 object storage for media.

Quick Start - local setup

To spin up this template locally, follow these steps:

Clone

After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. If you've already cloned this repo, skip to Development.

Development

  1. First clone the repo if you have not done so already

  2. cd my-project && cp .env.example .env to copy the example environment variables. You'll need to add the MONGODB_URI from your Cloud project to your .env if you want to use S3 storage and the MongoDB database that was created for you.

  3. pnpm install && pnpm dev to install dependencies and start the dev server

  4. open http://localhost:3000 to open the app in your browser

That's it! Changes made in ./src will be reflected in your app. Follow the on-screen instructions to login and create your first admin user. Then check out Production once you're ready to build and serve your app, and Deployment when you're ready to go live.

Docker (Optional)

If you prefer to use Docker for local development instead of a local MongoDB instance, the provided docker-compose.yml file can be used.

To do so, follow these steps:

  • Modify the MONGODB_URI in your .env file to mongodb://127.0.0.1/<dbname>
  • Modify the docker-compose.yml file's MONGODB_URI to match the above <dbname>
  • Run docker-compose up to start the database, optionally pass -d to run in the background.

How it works

The Payload config is tailored specifically to the needs of most websites. It is pre-configured in the following ways:

Collections

See the Collections docs for details on how to extend this functionality.

  • Users (Authentication)

    Users are auth-enabled collections that have access to the admin panel.

    For additional help, see the official Auth Example or the Authentication docs.

  • Media

    This is the uploads enabled collection. It features pre-configured sizes, focal point and manual resizing to help you manage your pictures.

Docker

Alternatively, you can use Docker to spin up this template locally. To do so, follow these steps:

  1. Follow steps 1 and 2 from above, the docker-compose file will automatically use the .env file in your project root
  2. Next run docker-compose up
  3. Follow steps 4 and 5 from above to login and create your first admin user

That's it! The Docker instance will help you get up and running quickly while also standardizing the development environment across your teams.

Questions

If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.