Weave Code
Mixpost Laravel Package
inovector/mixpost
Mixpost is a self-hosted social media management platform built with Laravel. Schedule and publish posts across multiple accounts, collaborate with teams, manage a content calendar, and track analytics from one customizable dashboard without per-seat SaaS fees.
📅 Schedule, 📢 publish, and ⚡ manage your social media content on your server. No subscriptions, no limits. (Buffer alternative)
Frequently asked questions about Mixpost
- How do I install inovector/mixpost in an existing Laravel application?
- Install it with Composer and then run vendor:publish to push out the config, migrations, and assets before migrating. That part is low-friction and well-trodden. The real integration effort sits outside the package: registering OAuth apps per network, completing platform app review, and provisioning a queue worker plus a per-minute scheduler.
- What Laravel and PHP versions does Mixpost require?
- The realistic baseline is Laravel 10 or 11 on PHP 8.1+, with MySQL or Postgres, Redis for cache and queues, and S3-compatible storage for media. Because Mixpost embeds deeply into the host app via Livewire, Vue, and Tailwind, you should pin and record an explicit support matrix covering Laravel minor, PHP minor, Livewire major, database driver, queue driver, and filesystem disk. Check that matrix against your app before installing rather than after.
- Is Mixpost free, or do I need the Pro license for analytics and team features?
- The MIT-licensed core covers scheduling and publishing. Analytics, team permissions, AI captioning, and multi-workspace support are Pro-licensed. Validate your required feature set against the paid tier before committing, otherwise the no-subscription premise only holds partially for your use case.
- Which social networks does Mixpost support and what approvals do I need before publishing?
- Mixpost publishes across multiple connected accounts, but every network requires you to register your own developer app and obtain the right permission grants. Meta, LinkedIn, and TikTok involve app review with multi-week lead times, and X publishing is gated by its paid API tier quotas. None of that is package-specific, so plan the external approval timeline separately from your development schedule.
- Can I run Mixpost as a separate service instead of embedding it in my main Laravel app?
- Yes, and it is often the better first move. Deploy Mixpost as a standalone app, wire SSO through a shared identity provider (SAML, OIDC, or a common user table), and link out from the primary product. This keeps the blast radius small and is the only realistic pattern for non-Laravel stacks such as Rails, Node, or .NET, where embedding is not an option.
- Does Mixpost work in a multi-tenant SaaS, and how are OAuth tokens handled?
- OAuth tokens are stored in your own database, so token encryption, tenant isolation, and revocation handling become your security obligation rather than the vendor's. This matters most if you expose Mixpost to external end users rather than keeping it as an internal tool. Decide up front whether this is single-tenant internal use or a multi-tenant SaaS, because it drives your auth model and support burden.
- What queue and scheduler setup does Mixpost need for scheduled posts to publish on time?
- You need a running queue worker plus a scheduler that ticks every minute, alongside Redis or another supported queue backend. Without both, scheduled posts will sit unpublished or fire late. Provision these in your deployment pipeline before you start testing publishing behavior.
- Will Mixpost conflict with my existing routes, tables, or frontend assets?
- It assumes ownership of a fairly large surface: the /mixpost route namespace, mixpost_* tables, its own auth and workspace model, and its own Tailwind and Vite asset pipeline. That fits cleanly in a greenfield app or a monolith where social scheduling is a bounded, separable domain. Before embedding, verify route and middleware ownership and check for Vite and Tailwind version overlap with your host app, since asset conflicts are the most common friction point.
- How do I test Mixpost publishing without hitting real social APIs, and can it double-post on queue retries?
- Duplicate posting on queue retry is the failure mode worth verifying early, because it destroys user trust quickly. Write integration tests around your job and retry configuration to confirm posts are idempotent before going live. For network calls, use each platform's sandbox app where available, or stub the outbound clients in your test suite rather than relying on live accounts.
- What is the exit plan if Mixpost maintenance stalls or a Laravel or Livewire upgrade breaks it?
- Because Mixpost integrates deeply through Livewire, Vue, and its asset pipeline, major-version bumps can require forking or patching the package yourself. Decide in advance whether you would fork or replace it, and who owns ongoing platform-compliance work such as app review renewals and API version migrations. Social APIs churn constantly, so that maintenance cost is permanent, not a one-off.
Weaver
How can I help you explore Laravel packages today?