Deploy Mixpost | (Just Updated) Self-Hosted Social Media Scheduler, No License Key, Admin Password Generated

Mixpost self-hosted social media scheduler, Buffer alternative, no license

Deploy Mixpost | (Just Updated) Self-Hosted Social Media Scheduler, No License Key, Admin Password Generated

Just deployed

/var/lib/mysql

Just deployed

/data

Just deployed

/var/www/html/storage/app

Deploy and Host Mixpost on Railway

Built for an LLM agent to deploy and use. The deploy form has no fields to fill and no license key: the owner password and app key are generated, MariaDB and Redis come with the template, and everything sits on volumes. Mixpost is a self-hosted social media management and scheduling app: plan, schedule and publish posts to Facebook, Instagram, X, LinkedIn, Mastodon and more from one calendar, a free alternative to Buffer and Hootsuite.

About Hosting Mixpost

This template runs three services: mixpost, the upstream Mixpost Lite v2.6.0 image (MIT, pinned by digest) through a thin wrapper, with a volume at /var/www/html/storage/app for uploaded media; mariadb, MariaDB 11.8 with a volume at /var/lib/mysql; and redis, Redis 8 with a volume at /data, which carries the queue that Horizon works through when posts publish. One public domain serves the app. The listener is on Railway's injected PORT, and the healthcheck is GET /mixpost/login.

What the wrapper fixes. Upstream's start script creates a default administrator, admin@example.com with the password changeme, on every fresh database, so a new instance is open to anyone who tries the default login. The wrapper replaces that step with an owner created from the ADMIN_PASSWORD variable, and re-syncs the password on every boot, so the default account never exists. It also waits for MariaDB before migrating, makes nginx listen on Railway's port over IPv4 and IPv6, and trusts Railway's proxy so links and cookies are HTTPS. The paid Mixpost Pro and Enterprise images need a LICENSE_KEY; this template runs the free Lite edition and asks for nothing.

Using it. Open the domain, go to /mixpost and log in with admin@mixpost.example and the value of ADMIN_PASSWORD. To use another email, add an ADMIN_EMAIL variable to the mixpost service. Connect your social accounts under Services, then create posts. Lite has no REST API: an agent works through the same session login as the browser, with the XSRF cookie, as the script below does. Keep the three volumes: they are the whole instance.

Agent contract

  • Public URL: https://RAILWAY_PUBLIC_DOMAIN (the generated domain of the mixpost service); the app is under /mixpost
  • Private URL: http://mixpost.railway.internal:8080 (IPv4 and IPv6)
  • Credentials: the variable ADMIN_PASSWORD on the mixpost service is the owner password; the owner email is admin@mixpost.example (add an ADMIN_EMAIL variable to change it)
  • Auth: a session login. GET /mixpost/login sets the XSRF-TOKEN cookie; POST /mixpost/login with JSON {"email": ..., "password": ...} and the header X-XSRF-TOKEN (the URL-decoded cookie value) answers 302 and sets the session cookie. Every other write needs that session and the same header. A write with no login answers 401, a wrong password answers 422, the old default account admin@example.com answers 422, and there is no public registration (/register answers 404).
  • Health: GET /mixpost/login returns 200
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN, ADMIN_PASSWORD (variables of the mixpost service; the owner email is admin@mixpost.example unless you add ADMIN_EMAIL); also curl, mktemp, sed, grep, tail, awk, date. Creates a throwaway tag and removes it again.
R="https://$RAILWAY_PUBLIC_DOMAIN"; ADMIN_EMAIL="${ADMIN_EMAIL:-admin@mixpost.example}"; J="Content-Type: application/json"; A="Accept: application/json"; C=$(mktemp)
xs() { grep XSRF-TOKEN "$C" | tail -1 | awk '{print $7}' | sed 's/%3D/=/g;s/%2B/+/g;s/%2F/\//g'; }
n=0; until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/mixpost/login")" = 200 ]; do n=$((n+1)); [ "$n" -le 60 ] || break; sleep 5; done
curl -s -c "$C" -o /dev/null -w "health: %{http_code}\n" "$R/mixpost/login"
# refusals first, from a fresh session: write with a session token but no login, wrong password, default account, public sign-up
curl -s -b "$C" -c "$C" -o /dev/null -w "write without key: %{http_code}\n" -X POST -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" -d '{"name":"intruder","hex_color":"#ff0000"}' "$R/mixpost/tags"
curl -s -b "$C" -c "$C" -o /dev/null -w "login wrong password: %{http_code}\n" -X POST -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" -d "{\"email\":\"$ADMIN_EMAIL\",\"password\":\"not-the-password\"}" "$R/mixpost/login"
curl -s -b "$C" -c "$C" -o /dev/null -w "default account login: %{http_code}\n" -X POST -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" -d '{"email":"admin@example.com","password":"changeme"}' "$R/mixpost/login"
curl -s -b "$C" -c "$C" -o /dev/null -w "public signup: %{http_code}\n" -X POST -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" -d '{"name":"x","email":"x@example.com","password":"x"}' "$R/register"
# log in with the generated password: 302 to /mixpost, the session cookie then authorises every call
curl -s -b "$C" -c "$C" -o /dev/null -w "login: %{http_code}\n" -X POST -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" -d "{\"email\":\"$ADMIN_EMAIL\",\"password\":\"$ADMIN_PASSWORD\"}" "$R/mixpost/login"
# write with the session: create a throwaway tag (302 = saved), read it back from the page data, delete it by uuid, read again
N="agent-$(date +%s)"
curl -s -b "$C" -c "$C" -o /dev/null -w "write tag: %{http_code}\n" -X POST -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" -d "{\"name\":\"$N\",\"hex_color\":\"#ff0000\"}" "$R/mixpost/tags"
curl -s -b "$C" -o "$C.page" "$R/mixpost/posts/create"
if grep -q ".quot;name.quot;:.quot;$N.quot;" "$C.page"; then echo "read back: found"; else echo "read back: MISSING"; fi
ID=$(sed -n "s/.*.quot;uuid.quot;:.quot;\([0-9a-f-]*\).quot;,.quot;name.quot;:.quot;$N.quot;.*/\1/p" "$C.page" | head -1)
curl -s -b "$C" -c "$C" -o /dev/null -w "delete tag: %{http_code}\n" -X DELETE -H "$J" -H "$A" -H "X-XSRF-TOKEN: $(xs)" "$R/mixpost/tags/$ID"
curl -s -b "$C" -o "$C.page" "$R/mixpost/posts/create"
if grep -q ".quot;name.quot;:.quot;$N.quot;" "$C.page"; then echo "after delete: STILL THERE"; else echo "after delete: gone"; fi
rm -f "$C" "$C.page"

Expected output against a fresh deploy (measured on a Railway deploy of the published template):

health: 200
write without key: 401
login wrong password: 422
default account login: 422
public signup: 404
login: 302
write tag: 302
read back: found
delete tag: 302
after delete: gone

The refusals are the contract: write without key: 401, login wrong password: 422, default account login: 422 and public signup: 404. The remaining lines show the generated owner password gives a session that can write a tag, read it back and delete it.

Why Deploy Mixpost 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 Mixpost 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.

  • No license key - the free Lite edition, with nothing to buy or paste before it starts.
  • Agent-ready - no deployer fields, a contract block, and one script that proves the instance is healthy, the generated password logs in, a write is saved and removed, and strangers can write nothing.
  • No default login - the owner is created from the generated password, and admin@example.com / changeme is refused.
  • Data survives redeploys - the database, queue and uploaded media live on volumes.
  • Pinned - the upstream image is pinned by digest and the wrapper by tag and digest.

Common Use Cases

  • Schedule social posts - one calendar for Facebook, Instagram, X, LinkedIn, Mastodon and more, on your own server.
  • Agency and team publishing - workspaces, approvals and a shared media library without a per-seat bill.
  • Content queue for an AI agent - an agent drafts and schedules posts through the logged-in session.
  • Self-hosted Buffer alternative - keep post history, analytics and tokens in your own database.

Dependencies for Mixpost Hosting

  • The mixpost service, MariaDB and Redis with their volumes, created by the template. A custom domain is optional; the wrapper builds its public URL from the Railway domain.

Deployment Dependencies


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0