ActiveAdmin VS Laravel

Can you clarify what's the "tremendous value" you're getting out of the Django admin?

At Heii On-Call https://heiioncall.com/ we are using Active Admin https://activeadmin.info/ for Ruby on Rails, which seems quite similar to the Django admin. In my experience, it's mostly useful as a fairly basic read-only view of what's in the database. In Rails, it's so easy to whip together a custom view that we tend to do that, and the Active Admin is nice to have but I wouldn't say "tremendous value".

Github Link : https://github.com/activeadmin/activeadmin

for those who know [https://activeadmin.info/](https://activeadmin.info/) it uses a file format [https://github.com/activeadmin/arbre](https://github.com/activeadmin/arbre)

Very neat! My first thought was that this was a competitor to https://bullettrain.co/.

Looking into it a bit more, it seems more aimed at building admin panels than whole apps. I guess it competes against tools like https://activeadmin.info/?

We briefly considered migrating to a full-grown Rails admin interface, such as ActiveAdmin, RailsAdmin, Administrate or Avo. We especially liked Avo which is built on a very modern stack similar to ours (Tailwind + Hotwire + ViewComponents). In the end, we didn’t go this route as we found some of the options a bit too restrictive (even though Avo is very flexible) and we did not feel like trying to amend it to our needs. For example, Avo renders forms in a 1-field-per-row layout while we wanted something more similar to the Tailwind UI Stacked form layout. Nevertheless, we found a great deal of inspiration in the Avo code and its design principles.

I second Rails. It's incredibly polished and has really good gems to speed up dev. ActiveAdmin is a great gem if you need to quickly make an admin dashboard. It was useful when I had a small consultancy.

https://activeadmin.info/

See an example: https://activeadmin.info It provides a fast way to create back office functionality.

[1] https://activeadmin.info/

I can't speak much about Rails, as I've only played with it. But I've used a lot Django in the past.

Regarding the Django admin (in rails you have ActiveAdmin[1]) think if it just as a glorified database explorer. It is an internal tool for developers, product managers and maybe for your support team. It is in no way thought to be used by end users. Every attempt I've seen to use it as such was a catastrophic failure.

With Django, if you know plain HTML and CSS, with the tools I've mentioned in the comment you're responding to, you can build almost anything... For example, let's say you need a highly interactive client side table.... you can always just attach a Vue or a React component for it by using Unpoly compilers [2].

I'd say this stack is less useful the more your app needs to work fully offline... but if you don't have that constraint... I cannot think of anything that can't be built faster and safer.

[1] https://activeadmin.info/

[2] https://unpoly.com/up.compiler

cd /var/www/ || handle_error "Failed to change directory to /var/www/." sudo git clone https://github.com/laravel/laravel.git laravel || handle_error "Failed to clone Laravel repository."

Laravel is a popular PHP framework known for its expressive syntax and rich ecosystem of features. Here's why it shines for building RESTful APIs:

Implementation In this article, we'll delve into the concept of rate limiting in Laravel; a popular PHP framework. We will explore how to set it up, customize it to suit your application's needs, and handle common scenarios. By the end, you'll have the knowledge and confidence to implement rate limiting in your Laravel applications, enhancing their security and stability.

Delving into PHP frameworks like Laravel or Symfony is like building a skyscraper, with Composer acting as your "construction foreman," guiding you step by step to ensure your code is robust and awe-inspiring. This stage involves getting familiar with popular PHP frameworks such as Laravel, Symfony, CodeIgniter, etc., and utilizing the functionalities provided by these frameworks to rapidly develop efficient, maintainable web applications. Tools to consider: Laravel, Composer.

Your very first starting point should be the Laravel documentation. Known for its clear explanations and user-friendly layout, the Laravel documentation makes setup a breeze, ensuring you get off to the best possible start.

In this tutorial, we will learn how to create a GraphQL API with Laravel, a popular PHP web framework. We will be creating a simple student model, seeding the database with dummy data, setting up a database connection, and creating a GraphQL server by defining our API's schema, queries, and mutations. We’ll also learn how to make requests to our API (test our endpoints) using a tool like Insomnia or Postman. By the end of this tutorial, you will have a working GraphQL API that you can continue to expand and improve.

Laravel is an open-source PHP framework on GitHub with 75.7k stars and 24.2k forks used for building web applications. It was first released in 2011 and follows the Model-View-Controller (MVC) architecture. It comes with an expressive and elegant syntax. It is fine-tuned for building professional web applications and ready to handle enterprise workloads. It achieves this by integrating the best packages from the PHP ecosystem and creating a framework that is also developer-friendly. Other than its foundational features, It also provides tools for dependency injection, unit testing, real-time events, and many more.

For this project, we will use Laravel, one of the biggest, most popular and most complete frameworks for PHP, along with Livewire, which will help us make our notifications real-time and reactive. Let's create a project from scratch and implement authentication and notification features for users tagged in posts.