What is Flixty?

Prerequisites

Deploying Flixty — step by step

Step 1 — Choose your cloud provider

Step 2 — Deploy with one MCP tool call

Step 3 — Save your deployment credentials

Step 4 — Get the public URL and set BASE_URL

Step 5 — Add platform OAuth credentials

Environment variables reference

Managing your Flixty deployment

Scaling your deployment

Custom domain

Troubleshooting

OAuth redirects fail after deploy

Posts fail for a specific platform

AI Assist not working

Deployment stuck in "queued"

Session errors after redeploy

Wrapping up 5 min read · Beginner friendly · April 2026 Flixty is an open-source, self-hosted social media creator studio that lets you publish to X, LinkedIn, Facebook, Instagram, TikTok, and YouTube from a single interface. NEXUS AI deploys it directly from source — no Dockerfile required — with a single MCP tool call. This guide walks you through deploying Flixty on NEXUS AI step by step — covering provider selection, environment variable setup, OAuth configuration for each platform, and ongoing management. By the end you'll have a live, self-hosted social posting studio running on your own cloud infrastructure. Flixty (github.com/nexusrun/flixty) is a Node.js 18+ Express application that serves as a unified control panel for social media publishing. It runs on port 3000 and is started with node server.js — no build step, no container image to maintain. Tip: You can deploy Flixty without any platform credentials first to get the public URL, then add OAuth credentials in a redeploy. This is the recommended flow since most OAuth apps require a known redirect URI before you can obtain credentials. Flixty is deployed as a source-based deployment — NEXUS AI clones the repo, installs dependencies, and runs node server.js on your chosen provider. GCP Cloud Run is recommended for production: it handles auto-scaling and provides a stable HTTPS URL you can use for OAuth redirect URIs. Environments map to: PRODUCTION for live traffic (default), STAGING for pre-production validation, and DEVELOPMENT for local testing. Via the NEXUS AI MCP in Claude, call nexusai_deploy_flixty. A minimal invocation — with no platform credentials yet — looks like this: If you don't supply a sessionSecret, NEXUS AI auto-generates a cryptographically secure 64-character hex secret for your Express sessions. You can also pass platform OAuth credentials and an anthropicApiKey at this stage if you have them ready. Or deploy from the CLI: After a successful deploy call, NEXUS AI returns: Important: Copy your sessionSecret immediately — it's returned once. Losing it means active user sessions will be invalidated on the next redeploy. Store it in NEXUS AI Secrets or your secrets manager. Once the deployment is running, retrieve its public URL and redeploy with BASE_URL set. This is required for OAuth redirect URIs to work correctly across all platforms. Use https://flixty.yourdomain.com/auth/<platform>/callback as the redirect URI when registering your OAuth apps on each platform. Redeploy with credentials for each platform you want to enable. You can add them all at once or one at a time: Note: fbAppId and fbAppSecret enable both Facebook and Instagram. A single Facebook App handles both platforms via the Graph API. All variables are injected securely at runtime. None are baked into the image. *BASE_URL is technically optional on first deploy when the public URL is not yet known. Set it on the first redeploy once the deployment is running. NEXUS AI gives you full lifecycle control over every deployment. Here's a quick reference: Scale Flixty up to handle more concurrent users without redeploying: Attach a custom domain so your OAuth redirect URIs stay stable across redeployments: Tip: Set up a custom domain before registering OAuth apps so your redirect URIs never change. Use https://flixty.yourdomain.com/auth/<platform>/callback as the redirect URI template. This means BASE_URL is not set or points to the wrong URL. Check the current value with nexusai_deploy_status and redeploy with the correct public HTTPS URL. All OAuth callbacks are constructed from BASE_URL at runtime. The platform credentials for that network are missing or incorrect. Check that the relevant env vars (X_CLIENT_ID, FB_APP_ID, etc.) are set via nexusai_deploy_status. Use nexusai_deploy_logs to see the exact OAuth error returned by the platform's API. ANTHROPIC_API_KEY is not set or the key is invalid. Redeploy with a valid Anthropic API key. Verify it starts with sk-ant- and has not expired or been revoked in your Anthropic console. Check that your cloud provider credentials are properly configured in NEXUS AI. For GCP, ensure your service account has Cloud Run developer permissions. Use nexusai_deploy_logs to diagnose any build or startup failures — common causes are missing Node.js version compatibility or a package.json install failure. If you redeploy without passing the original sessionSecret, a new secret is generated and all existing user sessions are invalidated. Always save and re-pass sessionSecret on subsequent deploys to maintain session continuity. Flixty on NEXUS AI gives you a fully self-hosted social media publishing stack — no third-party SaaS dependencies, no per-seat pricing, no data leaving your cloud. You control the OAuth tokens, the session data, and the posting schedule. From here, explore attaching a custom domain for stable OAuth redirect URIs, enabling AI Assist with your Anthropic API key, or setting up a staging environment to test platform integrations before they go live. Try it now: Head to nexusai.run and enable the NEXUS AI MCP connector in Claude to deploy Flixty with a single conversation in under 5 minutes. NEXUS AI — AI-native cloud infrastructure · nexusai.run Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse