NEW FEATURE: The EASIEST way to deploy Laravel

[@ServersideupNet]

*UPDATE:* The Spin Pro Laravel Template is now available 🥳 getspin.pro/

[@DivDax]

I've been waiting for this for a long time. Finally, a production-ready solution is available. I definitely need to test it out.

[@skygnd]

I gave it a try and I'm really happy with the results. Thanks for all your hard work. Even when I was setting up everything cleanly while working on Laravel Sail, I ran into weird issues that I couldn't find any solutions for online (vite hot reloading problems, strange symfony errors). But with Spin, all those problems are gone. I'm really looking forward to seeing how this project evolves 👍

[@JoseFranciscoIT]

An example with multiples apps in the same server would be great

[@ServersideupNet]

On our radar, thanks for sharing the idea 👍

[@rafaelacioly3252]

Is there any plan to support existing "pro" applications?

[@ServersideupNet]

Yup! Our first launch will likely support `spin new laravel-pro`. Shortly after, I plan to come up with a user experience so `spin init laravel-pro` works too 👍

[@devdude7607]

Are there any steps we need to follow to hookup MySql or just having it inside .env (local) as it is will workout?

[@ServersideupNet]

The versions of `spin new laravel` and `spin new laravel-pro` that we released yesterday will configure this for you auto-magically. 🤓 It will even do it during `spin init laravel` or `spin init laravel-pro` 🥳

[@ahmedsafaa1097]

Can it be run using github actions? I got a yml file setup for ci/cd once pushed to certain branch it could be delopyed to the server?

[@ServersideupNet]

Yup! We're working on a "Spin Pro" Laravel template which will include GitHub Actions support by default 😎 We also have open source GitHub Actions available if you prefer to write your own process serversideup.net/open-source/spin/docs/getting-started/how-spin-works#github-actions

[@brahim-oulhaj]

That's incredible, 🔥

[@thomaspotterdotexe]

I gave up using this method and the docker image since it always failed, it doesn't work with inertia vue and github actions 😞

[@ServersideupNet]

We're Intertia & Vue users too! If you're getting stuck, we have a helpful community that's willing to help out. Any questions, let us know github.com/serversideup/spin/discussions

[@thomaspotterdotexe]

@@ServersideupNet I thought I was submitted on the discussion forum before, I'll try to submit it again. Meanwhile, do you have another example other than the financial freedom repo that makes sense for the 3 years old baby to use the image? Like to do app with inertia vue or something. That would be great for me to investigate what's wrong with my custom image settings. Thanks

[@shofada]

Very Nice!

[@JonBrookes]

very interested and exciting to watch this demo of spin. Much gooderer than sail up in many regards methinks. I wrote something like this that you folks have done with spin for myself already but this deserves a look see pronto for me. I like the idea of using swarm, why that and not k3s / k0s ? cheaper to implement ? is swarm dead or still life left in it ? I started with swarm and trinsitioned to k8s so have a place in my head for swarm, I like it

[@ServersideupNet]

Great question! I had the same fears when getting started with Swarm about it being inactive. I found that to be very untrue. One thing I really like about Swarm is it's "feature complete". When I was working with K8s, there were so many releases coming out, it was hard to keep up. I also felt all the K8s features was just to make cloud services more money by requiring some odd service or extra complexity. I feel like with Swarm, it's a "less is more" approach. It has everything that I needed and I loved the simplicity of it. The product is well documented and there is a really cool community of people out there who continue to extend Swarm. Our primary focus with Spin was making it EASY for people to get these awesome features without any headache. K8s has it's use cases, but I feel for the majority of the developer population -- Swarm can get you very far without any unnecessary complexity. Hope this helps! Thanks for sharing your experiences 👍

[@anasouardini]

The problem is that not all servers are the same, you always need some tinkering to find the right versions of packages, etc before you deploy. There should be a standard for this.

[@ServersideupNet]

This is why we use Ansible to configure the server. We can guarantee the Docker Swarm host is configured like everything else. For the application server, we get even more detailed with Docker. Everything is locked to a Docker image. Aligning these dependencies dramatically increase the "disposable and repeatable" ability of the application -- making it easy to run the application anywhere.

[@notMichal]

Is it a Kamal clone?

[@ServersideupNet]

Nope! It's an easier way to use Docker (Docker Compose & Docker Swarm). We have a ton of open source resources to help deploy apps with Docker Swarm. More here: serversideup.net/open-source/spin/docs/getting-started/how-spin-works

[@JohnFarrar-he4pt]

The least popular part of application development is the part with friction and roadblocks.

[@Icaro204]

amazing but the price for a single developer i find it too much