Eventyay is an open-source platform for managing events, including ticket sales and registration, speaker submissions, session schedules, videos, check-ins, badges, exhibitions, and organiser administration. Event organisers use it to run both in-person and online event workflows.
Borrowing it
Nothing to install: this file belongs to fossasia/eventyay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fossasia/eventyay/dev/.github/instructions/dockerfile.instructions.mdgit clone --depth 1 https://github.com/fossasia/eventyayWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/fossasia/eventyay/dockerfile)<a href="https://agentmods.dev/instructions/fossasia/eventyay/dockerfile"><img src="https://agentmods.dev/badge/instructions/fossasia/eventyay/dockerfile/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/fossasia/eventyay/dockerfile"><img src="https://agentmods.dev/badge/instructions/fossasia/eventyay/dockerfile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00970 | $0.00970 |
| Opus 5.5 | $0.00388 | $0.00388 |
| Sonnet 5.5 | $0.00194 | $0.00194 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
eventyay dockerfile.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker and Container Reference
This document covers Docker Compose usage, container services, environment variables, and the development workflow for Eventyay.
Core Architecture Principle:
- Development (
docker-compose.yml): Builds directly fromapp/Dockerfile. Thewebcontainer serves static assets directly via Django. - Production (
deployment/docker-compose.yml): Uses a pre-built image (eventyay/eventyay-next:${TAG}) rather than building it locally. This image is built fromapp/Dockerfile.prodvia CI/CD pipelines. Static assets are pre-built. In production, Nginx is typically configured at the host level (outside this Compose stack) to reverse-proxy requests to the Gunicorn application server.
For the full production deployment walkthrough including Nginx, SSL, and backups, see DEPLOYMENT.md.
Files
| File | Purpose |
|---|---|
docker-compose.yml |
Development / local stack |
deployment/docker-compose.yml |
Production stack |
deployment/env.dev.sample |
Sample development environment variables |
deployment/env.sample |
Sample production environment variables |
deployment/nginx/ |
Nginx reverse-proxy configuration |
Services
Development stack (docker-compose.yml)
| Service | Container name | Port | Description |
|---|---|---|---|
web |
eventyay-next-web |
8000 | Django development server |
worker |
eventyay-next-worker |
— | Celery task worker |
redis |
eventyay-next-redis |
— | Message broker and cache |
db |
eventyay-next-db |
— | PostgreSQL 15 database |
Environment Variables
Copy the sample file and edit it before starting the stack:
cp deployment/env.dev.sample .env.dev
Key variables to configure:
| Variable | Description |
|---|---|
EVY_SECRET_KEY |
Django secret key (keep it secret) |
EVY_POSTGRES_DB |
PostgreSQL database name used by the Django app |
EVY_POSTGRES_USER |
PostgreSQL username used by the Django app |
EVY_POSTGRES_PASSWORD |
PostgreSQL password used by the Django app |
POSTGRES_DB |
PostgreSQL database name used by the database container |
POSTGRES_USER |
PostgreSQL username used by the database container |
POSTGRES_PASSWORD |
PostgreSQL password used by the database container |
EVY_REDIS_URL |
Redis connection URL |
EVY_SITE_URL |
Public site URL, e.g. https://<SERVER_NAME> |
EVY_ALLOWED_HOSTS |
Django ALLOWED_HOSTS, e.g. <SERVER_NAME> |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 131 lines · 970 tokens per session scan A e66a52c5e415
eventyay dockerfile.instructions.md is an instructions file published in the GitHub repository fossasia/eventyay (1,710 stars, last pushed today), licensed Apache-2.0. It adds 970 tokens to every session, about $0.0039 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.