Kategorien durchsuchen
Entdecken
Fiverr Pro
Deutsch
$
USD
I will build a custom github actions ci cd pipeline for laravel
Full Stack SaaS Engineer and Tall Stack Architech
Hi, I'm a Full-Stack Engineer specializing in Laravel 11, the TALL Stack, Filament v3 admin portals, and ultra-fast Astro static sites.
I help SaaS founders and businesses build scalable web software...
Über diesen Service
Are you still deploying your Laravel app manually via FTP or terminal commands? Manual deployments cause downtime, human error, and broken production environments.
I am a DevOps Engineer and full-stack Laravel developer. I will architect a rock-solid GitHub Actions CI/CD pipeline to automate your testing and deployment so you can ship code with confidence.
What I will deliver:
- Continuous Integration (CI): Automated tests (PHPUnit/Pest) & style checks (Pint) on Pull Requests.
- Fast Pipelines: Dependency caching for Composer & NPM to minimize build times.
- Automated Deployment (CD): Secure deployment to your VPS (Hetzner, AWS, DigitalOcean) via SSH or Coolify webhooks on merge.
- Containerization: Build, tag, and push Docker images to registries (GHCR, DockerHub).
- Security: Safe credential handling via encrypted GitHub Secrets.
Supported Stack: Laravel, PHP, Docker, Coolify, Linux VPS.
IMPORTANT: My service covers the CI/CD pipeline infrastructure. It does NOT include fixing broken application tests or writing new application tests.
Message me before ordering so we can review your repository and server setup.
Tools:
Docker
•
GitLab
•
GitHub
•
Andere
Frameworks:
Npm
•
Andere
Cloud-Provider:
Amazon Web Services
•
DigitalOcean
•
Andere
Programmiersprache:
Bash
•
JavaScript
•
PHP
•
PowerShell
Expertise:
Debuggen
•
Entwicklung
•
Konfiguration
Mein Portfolio
Meine weiteren Dienstleistungen im Bereich DevOps-Engineering
FAQ
Do you fix failing tests in my existing codebase?
No. I build the pipeline that executes your tests. Your codebase must pass its tests locally before we set up CI. If you need broken application code or tests fixed, we can scope that separately.
What server providers and hosting setups do you support?
I support Linux VPS environments (Hetzner, DigitalOcean, AWS EC2, Linode) whether running bare Ubuntu, Docker containers, or control panels like Coolify, Laravel Forge, and RunCloud.
How does continuous deployment work with GitHub Actions?
On merge to your main branch, GitHub Actions securely connects via SSH or triggers an authenticated webhook to pull updates, compile assets, run migrations, and reload services with zero downtime.
How are my server passwords and private keys secured?
All credentials (SSH keys, server IPs, API tokens) are strictly stored inside encrypted GitHub Secrets. No private credentials or sensitive variables are ever committed or hardcoded in the YAML file.
Will the CI pipeline slow down my development workflow?
No. I configure automated caching for Composer packages and NPM node_modules, which drastically cuts pipeline execution time from several minutes to under 60 seconds.
Does this pipeline support Docker and container registries?
Yes. In the Premium package, I configure multi-stage Docker builds, push images to GitHub Packages (GHCR) or DockerHub, and trigger container recreation on your production host.
What access do you need to complete the setup?
I will need temporary collaborator access to your GitHub repository (to manage Actions and Secrets) and temporary SSH access to your server (or your Coolify/Forge webhook URL). You can revoke access immediately upon delivery.
Can the pipeline run database migrations and Laravel optimizations?
Yes. The deployment script runs 'php artisan migrate --force' and refreshes production caches ('config:cache', 'route:cache', 'view:cache') automatically on each release.
Can we configure separate staging and production deployments?
Yes. We can configure branch protection so pushes to 'staging' deploy to a preview server, while merges to 'main' or tagged releases deploy to live production
What happens if a test or build fails in GitHub Actions?
The pipeline stops immediately. Deployment is blocked to prevent broken code from hitting production, and GitHub generates error logs detailing the exact failure.
