Deploy Fider | (Just Updated) Feedback Board and Feature Voting, REST API and API Key Generated
Fider feedback board and feature voting app with REST API, key preset
Just deployed
postgres
Just deployed
/var/lib/postgresql
Deploy and Host Fider on Railway
Built for an LLM agent to deploy and use. The deploy form has no fields to fill: the session secret and a REST API key are generated, the board and its administrator are created at first boot, public sign-up is closed, and the database sits on a volume. Fider is the open-source, self-hosted feedback board where users post ideas and vote on them, with a REST API.
About Hosting Fider
This template runs two services: postgres, PostgreSQL 17 on a volume at /var/lib/postgresql, and fider, the upstream Fider 0.40.0 image (pinned by digest) through a thin wrapper. Fider keeps posts, votes, users and uploaded images in PostgreSQL, so the volume holds everything and survives redeploys. The server listens on Railway's injected PORT, and the healthcheck is GET /_health.
What the wrapper fixes. A fresh upstream Fider has no board: the first visitor to the public URL is sent to /signup and becomes its owner, and the REST API accepts only a personal API key that a signed-in user generates in the web interface, after an e-mail sign-in link. The wrapper creates the board and an administrator before the server listens, seeds the administrator's API key from the generated variable FIDER_API_KEY, and sets SIGNUP_DISABLED=true so /signup and board creation answer 404. It also bakes the SMTP host and no-reply address Fider refuses to start without, so the deploy form stays empty.
Using it. Call the API with Authorization: Bearer $FIDER_API_KEY. The key belongs to the administrator admin@fider.invalid. Fider has no passwords: people sign in with an e-mail link or an OAuth provider, so to let people sign in by e-mail add EMAIL_SMTP_HOST, EMAIL_SMTP_PORT, EMAIL_SMTP_USERNAME, EMAIL_SMTP_PASSWORD and EMAIL_NOREPLY to the fider service. To make the administrator your own address, add FIDER_ADMIN_EMAIL before the first deploy (it is also applied on later boots). Keep JWT_SECRET stable: changing it signs everyone out.
Agent contract
- Public URL:
https://RAILWAY_PUBLIC_DOMAIN(the generated domain of thefiderservice) - Private URL:
http://fider.railway.internal:8080 - Credentials: the variable
FIDER_API_KEYon thefiderservice is the administrator's REST API key;JWT_SECRETsigns sessions and is not a login;POSTGRES_PASSWORDon thepostgresservice is the database password - Auth: send
Authorization: Bearer $FIDER_API_KEYon every API call. A write with no key answers 401 and a write with a wrong key answers 400. Public sign-up is closed: board creation answers 404. - Health:
GET /_healthreturns 200
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN, FIDER_API_KEY (variables of the fider service); also curl, sed. Creates one throwaway post and deletes it.
R="https://$RAILWAY_PUBLIC_DOMAIN"; J="Content-Type: application/json"; A="Authorization: Bearer $FIDER_API_KEY"
n=0; until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/_health")" = 200 ]; do n=$((n+1)); [ "$n" -le 60 ] || break; sleep 5; done
curl -s -o /dev/null -w "health: %{http_code}\n" "$R/_health"
# read with the key
curl -s -o /dev/null -w "read users: %{http_code}\n" -H "$A" "$R/api/v1/users"
# write with the key: create a post, read it back, delete it
NUM=$(curl -s -X POST -H "$J" -H "$A" -d '{"title":"agent contract check","description":"throwaway post"}' "$R/api/v1/posts" | sed -n 's/.*"number":\([0-9]*\).*/\1/p')
if [ -n "$NUM" ]; then echo "write post: created"; else echo "write post: FAILED"; fi
curl -s -o /dev/null -w "read post: %{http_code}\n" -H "$A" "$R/api/v1/posts/$NUM"
curl -s -o /dev/null -w "delete post: %{http_code}\n" -X DELETE -H "$J" -H "$A" -d '{}' "$R/api/v1/posts/$NUM"
# refusals: no key, wrong key, public sign-up
curl -s -o /dev/null -w "write without key: %{http_code}\n" -X POST -H "$J" -d '{"title":"no key post","description":"x"}' "$R/api/v1/posts"
curl -s -o /dev/null -w "write wrong key: %{http_code}\n" -X POST -H "$J" -H "Authorization: Bearer not-the-key" -d '{"title":"wrong key post","description":"x"}' "$R/api/v1/posts"
curl -s -o /dev/null -w "public signup: %{http_code}\n" -X POST -H "$J" -d '{"tenantName":"Intruder","subdomain":"intruder","name":"Intruder","email":"intruder@example.com"}' "$R/_api/tenants"
Expected output against a fresh deploy (measured on a Railway deploy of this template):
health: 200
read users: 200
write post: created
read post: 200
delete post: 200
write without key: 401
write wrong key: 400
public signup: 404
The refusals are the contract: write without key: 401, write wrong key: 400 (the key is rejected) and public signup: 404 (a second board cannot be created). The first five lines show the API key works for reads and writes.
Why Deploy Fider on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Fider on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
- Agent-ready - no deployer fields, a contract block, and one script that proves the instance is healthy, the API key can read and write, and unauthenticated writes and sign-ups are refused.
- Setup done for you - the board, the administrator and the API key are created from generated variables before the server listens, so nobody can claim the board.
- Sign-up closed - nobody else can create a board on the public URL.
- Data survives redeploys - posts, votes and users live in PostgreSQL on a volume.
- Pinned - the upstream image is pinned by digest and the wrapper by tag and digest.
Common Use Cases
- Public feedback board and feature voting - let customers post ideas and vote, and answer with a status.
- Roadmap input for a product team - rank requests by votes before planning.
- Feedback intake for an AI agent - a REST API to create, tag, comment on and close posts without a person clicking.
- Replacement for Canny, UserVoice or Featurebase - an open-source feedback board you host yourself.
Dependencies for Fider Hosting
- The fider and postgres services with the postgres volume, created by the template. A custom domain is optional; if you add one, set
BASE_URLto it.
Deployment Dependencies
Template Content
