Your backend as a Docker image
The pipeline builds your Laravel backend into an image. Your PHP code and its Composer dependencies remain part of your application.
You are building your application with Laravel and AI. MainPath prepares project structure, tests and deployment so your PHP backend can move from local development to your server.
The pipeline builds your Laravel backend into an image. Your PHP code and its Composer dependencies remain part of your application.
MainPath prepares connected servers with Docker, a reverse proxy and HTTPS. Your backend and its database belong to the project.
Migrations, background jobs and data need rules that fit your application.
Test schema changes alongside your code and decide their place in a release. Check how your application works with the changed data before publishing.
Decide which queue workers and scheduled tasks your backend needs. Their configuration and behavior are part of your Laravel application.
The prepared backend uses MySQL. Maintain your own values per environment and keep credentials in managed secrets.
Point Laravel Storage at the intended upload location. User files then remain separate from a new application image.
Create a Laravel backend. If you already have code, your AI agent first checks whether the project can be imported.
Connect the target server and configure your application values. Separate local development, Dev and production, as well as public configuration and secrets.
Develop features, test data changes and run the backend locally. Changes and project rules remain traceable in the repository.
The pipeline tests and builds your changes. Try the deployed Dev version, then deliberately approve the appropriate build for production.
Open the cloned backend repository and start its local development environment with the MainPath CLI. Docker and the required runtimes need to be ready on your machine.
mp run-localStart a Laravel project or talk to us about bringing your existing application to MainPath.
Yes, for supported projects. Your AI agent checks the code first and guides the import. Application values, data and additional services need to fit the prepared setup.
The prepared backend uses MySQL in its own container on the project server. You can enable phpMyAdmin in the project configuration to manage the database.
You decide which migrations, workers and scheduled tasks your application needs. Test their configuration and release behavior for your project; the generated pipeline file is not edited by hand.
Your own values go in the documented custom files and project environment configuration. MainPath manages sensitive passwords and API keys as secrets.
For supported MySQL backends, you can enable Easy Backup in the project configuration. It backs up the database and uploads in production; choose the schedule and retention to fit your project.