laravel.io VS sagan

Laravel.io Forum

Laravel is a web app framework written in PHP. It is open source and is based on Model-View-Controller (MVC) architectural pattern. It was released in 2011. Famous websites built using Laravel are Invoice Ninja, Alison, Barchart, MyRank, AlphaCoders, Laracasts and Laravel.io.

https://github.com/laravelio/laravel.io/blob/main/app/Jobs/BanUser.php yes you are definitely using unnecessary jobs

I have only visited laravel.io briefly, I have not checked the code-base.

Laravel.io has lots of issues you can pick up. https://github.com/laravelio/laravel.io/issues

Hi everyone, what are some examples of large(ish) web applications written in laravel not written by people affiliated with the laravel community (ie: not laravel.io). It doesn't have to be open source. Just links to websites/companies that use laravel.

Maybe I'm not the intended target audience for Laravel.io but I can't see the place it has within the Laravel community.

Empeza con esto https://spring.io/

If you want to do web apps, I'd recommend Django (a python framework) https://docs.djangoproject.com/en/4.1/, but you can do Rails, or Phoenix, or Spring Boot, or whatever. It doesn't terribly matter *which* one you do, as they share characteristics, and, chances are, your company will be using a different one :). Just pick one and go. You can do it. You know a lot more than you think.

With the idea planted, and already internalized that I would use spring-boot to create our API, I needed to decide on which engine it would be built. I had been studying Unreal Engine for some time, but because I had more know-how in Unity and because I found this AMAZING weather system, I opted for our last alternative.

This is an introduction article on how to build a RESTful application in Kotlin using Spring Boot 3 and MongoDB Atlas.

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

Im stuck between just starting up a project, or if following some starter project for learning. I did a tutorial on the spring.io website, but thats about all I have done so far.

I've been following the guides at spring.io, but there's just so many guides there. My company has a template for starting new projects (includes frontend + backend + database) so I decided to start my project using it, thinking the basic guides I followed on REST APIs would help me but I quickly realized it's more complicated than I thought.

Thanks for the advice. I followed some guides on spring.io, but because I am using a template for starting new projects provided by my company, I found most of them couldn't really translate properly to the template.

Spring makes building web applications fast and hassle-free (spring.io). By removing much of the boilerplate code and configuration associated with web development, you get a modern web programming model that streamlines the development of server-side HTML applications, REST APIs, and bidirectional, event-based systems.