When building a robust application, maintaining distinct environments for development, staging, and production is a best practice to ensure stable releases. With Post for Me, you can easily manage these different lifecycle stages by creating completely isolated projects for each of your environments.
Here is a breakdown of how to structure your projects to securely handle testing and production data.
The Project-Based Architecture
A project in Post for Me acts as a completely independent container for your API configurations, credentials, and user data.
How it works
Instead of trying to flag individual posts or accounts as "test" data within a single integration, you simply create a distinct project in your dashboard for each of your environments (e.g., "My App - Dev", "My App - Staging", "My App - Prod"). This guarantees total separation of concerns.
Isolation of Configurations
Because each project is strictly isolated, you must manage their specific configurations independently within your application's environment variables.
How it works
Each project generates its own unique API_KEY. Furthermore, every project will have its own isolated database of connected social accounts, active webhooks, and global callback URLs.
This architecture ensures that a test account connected in your staging environment will never accidentally cross over, and test posts will never accidentally leak into your production environment.
Mixing Project Types
You are not locked into a single setup strategy across your entire development lifecycle; you can mix and match project types to optimize your workflow.
How it works
For example, you might create a Quickstart project for your development or staging environment. This allows your engineers to test features quickly using our system credentials without needing to wait for native platform app approvals.
Then, you can use a White Label project for your production environment. By doing this, your actual end-users will go through a fully branded OAuth flow using your own approved platform credentials, while your developers enjoy the frictionless testing of a Quickstart project locally.