You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`PRETALX_SITE_URL`, defaults to the workflow input or `https://pretalx.asyncapi.com`
33
34
-`PRETALX_REMOTE_PATH`, defaults to `/opt/asyncapi-pretalx`
34
35
-`PRETALX_HTTP_PORT`, defaults to `8346`
35
-
-`PRETALX_IMAGE_TAG`, defaults to `latest`
36
+
-`PRETALX_IMAGE_TAG`, defaults to `v2026.1.2`
37
+
-`PRETALX_FILE_UPLOAD_LIMIT`, defaults to `2`
36
38
-`PRETALX_MAIL_TLS`, defaults to `True`
37
39
-`PRETALX_MAIL_SSL`, defaults to `False`
38
40
-`GUNICORN_FORWARDED_ALLOW_IPS`, defaults to `127.0.0.1`
39
41
42
+
Only the Pretalx image is configurable through `PRETALX_IMAGE_TAG`. The supporting nginx, Postgres, Redis, and local Mailpit images stay defined directly in Compose so deploy configuration does not grow extra tag knobs.
43
+
44
+
## Uploaded Media
45
+
46
+
Pretalx writes media and static files to the shared `pretalx-public` volume under `/public`. The compose stack publishes the nginx container, not the Pretalx app container, so URLs such as `/media/avatars/...webp` and `/static/...` are served directly from that volume. `PRETALX_FILE_UPLOAD_LIMIT` defaults to `2` MB, and both nginx configs allow `3m` request bodies to leave room for multipart upload overhead.
47
+
40
48
## Production URL
41
49
42
50
Keep production disabled in website env until DNS and the production droplet are ready:
5. Configure the event, CFP fields, deadlines, review workflow, and schedule release in Pretalx.
63
71
6. Enable the `AsyncAPI CFP API` plugin for each event.
64
-
7. Open `Event settings -> Plugins -> AsyncAPI CFP API -> Location metadata` and fill in the event city, country, address, and map URL. Saving this form also writes a managed `Location` section into Pretalx's public event landing page text. If metadata was saved before this behavior existed, save the form once again after rebuilding the image.
72
+
7. Open `Event settings -> Plugins -> AsyncAPI CFP API -> Location metadata` and fill in the event city, country, address, map URL, and image URL. Saving this form also writes a managed `Location` section into Pretalx's public event landing page text. If metadata was saved before this behavior existed, save the form once again after rebuilding the image.
65
73
66
74
If you need to seed or repair the metadata from the droplet shell, write the same values directly:
The sync endpoint returns global CFP dates and location metadata at:
@@ -85,7 +93,7 @@ The sync endpoint returns global CFP dates and location metadata at:
85
93
86
94
The website sync workflow uses the authenticated Pretalx API. It fetches public events from `/api/events/?is_public=true`, enriches them with `/api/events/{event}/p/asyncapi-cfp/event-info/` when the plugin is enabled, then fetches `/api/events/{event}/schedules/latest/` with expanded schedule slots, submissions, speakers, proposal types, and tracks.
87
95
88
-
The workflow writes generated data to `config/pretalx/city-lists.json`, `config/pretalx/speakers.json`, and `config/pretalx/agenda.json`, then opens a PR. When the plugin endpoint is available, `city-lists.json` includes global CFP deadline, city, country, address, and map URL from Pretalx. Third-party/manual CFP systems remain in `config/third-party/` and are merged into the website by `config/conference-data.ts`.
96
+
The workflow writes generated data to `config/pretalx/city-lists.json`, `config/pretalx/speakers.json`, and `config/pretalx/agenda.json`, then opens a PR. When the plugin endpoint is available, `city-lists.json` includes global CFP deadline, city, country, address, map URL, and image URL from Pretalx. Third-party/manual CFP systems remain in `config/third-party/` and are merged into the website by `config/conference-data.ts`.
Configure Pretalx with `PRETALX_MAIL_HOST=mailpit`, `PRETALX_MAIL_PORT=1025`, `PRETALX_MAIL_TLS=False`, and `PRETALX_MAIL_SSL=False`. Open captured mail at `http://localhost:8025`.
99
107
108
+
To test the real Mailjet SMTP path locally, render `conf/pretalx.cfg` with these mail values instead of Mailpit:
109
+
110
+
```env
111
+
PRETALX_MAIL_FROM=cfp@asyncapi.com
112
+
PRETALX_MAIL_HOST=in-v3.mailjet.com
113
+
PRETALX_MAIL_PORT=2525
114
+
PRETALX_MAIL_USER=<mailjet-api-key>
115
+
PRETALX_MAIL_PASSWORD=<mailjet-secret-key>
116
+
PRETALX_MAIL_TLS=True
117
+
PRETALX_MAIL_SSL=False
118
+
```
119
+
120
+
Use a verified Mailjet sender/domain and do not commit the rendered `conf/pretalx.cfg`.
121
+
100
122
## DigitalOcean Mail
101
123
102
124
Run Pretalx on DigitalOcean, but do not run outbound mail delivery from the Droplet itself. DigitalOcean blocks Droplet SMTP ports `25`, `465`, and `587`, so use Mailjet as the external SMTP provider and configure the `PRETALX_MAIL_*` secrets for it. Prefer Mailjet port `2525` for the test droplet.
@@ -105,6 +127,6 @@ Kit should stay in the newsletter/broadcast path. Pretalx's built-in email deliv
105
127
106
128
## GitHub Deployments UI
107
129
108
-
The deploy workflow uses a GitHub Actions environment named `pretalx-test` by default. GitHub creates deployment status entries for environment jobs and shows them in the repository's Deployments UI with the Pretalx URL.
130
+
The deploy workflow uses a GitHub Actions environment named `pretalx-prod` by default. GitHub creates deployment status entries for environment jobs and shows them in the repository's Deployments UI with the Pretalx URL.
109
131
110
-
When running the workflow manually, you can change `target_environment` to a different value such as `pretalx-prod`.
132
+
When running the workflow manually, you can change `target_environment` to a different value such as `pretalx-test`.
0 commit comments