- How do I install prateekbhujel/larapost in a Laravel application?
- Install the package with Composer using composer require prateekbhujel/larapost, then follow the setup steps in the repository README to register the service provider and publish any package configuration or migration files. Because the package is Laravel-native, it is designed to drop into an existing app rather than requiring a separate service. Always check the README for the exact commands and any required environment variables before running migrations in production.
- Which social networks does Larapost support for publishing?
- Larapost supports publishing to Facebook, X (formerly Twitter), LinkedIn and TikTok. Each platform is handled through its own OAuth flow and publishing driver inside the package. If you need a network outside that list, check the repository for support status or plan to implement a custom driver.
- How does OAuth account connection work in Larapost?
- Larapost handles the OAuth handshake for each supported network so you can connect user or page accounts and store the resulting credentials. Connected accounts are then used by the publishing layer when a post is sent. Review the README for the routes, redirect URIs and callback configuration you must register with each social platform's developer console.
- Can I schedule posts for a future date and time with Larapost?
- Yes, scheduling is a core feature: instead of publishing immediately, you can queue a post to be dispatched at a later time. Scheduling works together with Laravel's queue system, so a delayed job releases the post when it is due. Make sure your scheduler and queue worker are running so scheduled posts are actually sent.
- How do queues and retries work in Larapost?
- Publishing is pushed onto Laravel queues rather than executed inside the HTTP request, which keeps your application responsive during slow API calls. When a platform API call fails, the package can retry the job based on your queue and retry configuration. You should tune retry counts and backoff to match each network's rate limits so transient failures recover without flooding the API.
- Do I need to run a queue worker in production to use Larapost?
- Yes. Since publishing is queued, you need a running queue worker (for example via Supervisor or Laravel Horizon) in any environment where posts must actually be sent. Without a worker, jobs will sit in the queue and posts will never be published. For scheduled posts you also need the Laravel scheduler running every minute.
- What is the optional MCP support in Larapost?
- MCP support is an optional integration that lets an MCP-compatible client or AI tool interact with the package's publishing capabilities. It is not required for normal OAuth, queue or scheduling usage, so you can leave it disabled if you only need standard social publishing. Check the README for how to enable it and what it exposes.
- Which Laravel and PHP versions are supported by Larapost?
- Version support is defined by the package's composer.json constraints, so check that file and the README before installing. Confirm that your PHP version and Laravel major version satisfy those constraints. If you are on an older Laravel release, verify compatibility first or the Composer resolution may fail.
- How can I test social publishing without hitting real Facebook, X, LinkedIn or TikTok APIs?
- Use Laravel's HTTP fake helpers or bind a stub driver so outbound API calls are intercepted in your test suite. Queue assertions (for example Queue::fake or Bus::fake) let you verify that a post was dispatched without performing the actual publish. This keeps tests fast and avoids rate limits or accidental live posts in CI.
- How do I securely store social access tokens and keep the package maintained?
- Store the OAuth tokens issued during account connection in your database or secret manager, and never commit them to source control. Because access tokens expire or can be revoked, plan for a refresh or reconnect flow and monitor failed publish jobs for auth errors. Also pin a tested version in composer.json and review the repository for recent commits and releases before adopting it in production.