action-hosting-deploy VS laravel-backup

Could they not have their own FB to develop against? Does every dev need to use just yours? If that is the case, then you'd need to use https://support.google.com/firebase/answer/7000272?hl=en also, it looks to be possible to include Firebase in your GitHub for them to pull from https://firebase.google.com/docs/hosting/github-integration

Github Actions is the way to go for this: https://firebase.google.com/docs/hosting/github-integration

Whenever a Pull Request is created we need to be able to quickly checkout the changes. Reading code diff is great, but sometimes you just need to tinker with the new version, test it on mobile, different browsers and OS. Cloud services are perfect for this case, they allow you to deploy the code temporarily and access it with a link from any device. We chose Firebase to host it for us and a Github action posts a link to the deployment as a comment in the Pull Request. It works like a charm and speeds up code reviews a lot. Read this article to set it up on your repository!

Lambdas and firebase on the GCP stack for CRUD apps.

One nice thing about firebase -> each PR deploys to its own preview channel[1].

Downside: Very JS heavy. I write lambdas in python though.

[1] https://firebase.google.com/docs/hosting/github-integration

Google Firebase has a pretty straightforward guide to setting up auto-deploy from Github, which you can take a look at here: https://firebase.google.com/docs/hosting/github-integration

What is the easiest way for setting up CI/CD from GH for Firebase functions? Maybe something like this for hosting, but only for functions?

Note: you can find more info about the used steps actions here actions/checkout@v2 and here FirebaseExtended/action-hosting-deploy@v0

https://github.com/jeremykenedy/laravel-logger#authentication-middleware-usage https://github.com/beyondcode/laravel-dump-server https://github.com/barryvdh/laravel-debugbar https://github.com/laravel-shift/blueprint https://github.com/spatie/laravel-backup https://github.com/spatie/laravel-permission https://github.com/spatie/laravel-activitylog https://github.com/realrashid/sweet-alert https://github.com/rappasoft/laravel-livewire-tables https://github.com/yajra/laravel-datatables https://github.com/Labs64/laravel-boilerplate https://github.com/creativetimofficial/argon-dashboard-laravel https://github.com/the-control-group/voyager https://github.com/beyondcode/laravel-er-diagram-generator

8. spatie/laravel-backup

4. spatie/laravel-backup https://github.com/spatie/laravel-backup

In my case I'm dumping + zipping the entire database at the application level. In my case is as simple as adding a library [1], scheduling the job and transferring to AWS S3 (my main application is on DigitalOcean)

[1] https://github.com/spatie/laravel-backup

Database backups via php artisan backup:run