jetstream
django-unicorn
Our great sponsors
jetstream | django-unicorn | |
---|---|---|
23 | 51 | |
3,881 | 2,159 | |
0.9% | - | |
8.7 | 9.1 | |
7 days ago | 6 days ago | |
PHP | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jetstream
-
Ask HN: What would be your stack if you are building an MVP today?
While I prefer python for everything else, I'd go with Laravel Jetstream[1] for an MVP, just like I did with the last one I had to build. It's laravel, you can use Vue (React or Svelte) for your views instead of the blade templating language that comes with the framework. Jetstream also comes with Auth, user login and subscription and other useful stuff.
And for the flavor, I'd just go with DaisyUI[2] again, since it's based on tailwindcss and it's what I've been using lately.
In my experience, I can build MVPs real fast with the stack described above.
- Admin panel with basic html css js
-
`npm run dev` not copying css or js files to public. Bug?
This legacy package is a very simple authentication scaffolding built on the Bootstrap CSS framework. While it continues to work with the latest version of Laravel, you should consider using Laravel Breeze for new projects. Or, for something more robust, consider Laravel Jetstream.
-
Controllers vs livewire components
Jetstream is not a bad place to start: https://github.com/laravel/jetstream/tree/2.x/src
- Jetstream - Allow personal teams to be optional
-
How Laravel Livewire works (a deep dive)
I get your point and this conversation might be as old as Laravel itself. I would like to point out a couple of things though:
The "hop in and be productive" part is directly related to Laravel being pretty opinionated. It's hard to have the one without the other. I think it's comparable to Steve Jobs, who had pretty strong opinions about certain things, too. The end result is a "product" that doesn't try to be the right fit for everyone.
Livewire, just like Jetstream[1] etc. is opt-in. When Jetstream was introduced, there was quite an uproar (by parts of the community) about Laravel forcing users into Livewire or Inertia[2]. The end result was (imho) a very healthy shift in communication around it (to emphasize the opt-in part), followed by the introduction of Breeze[3], which goes to show that Taylor does recognize the reservations some people may have about those new shiny toys.
It's a very natural thing that big projects like that will have an ever-growing feature set. That is an important part of keeping existing users excited. The Jetstream-discussion has been an important lesson for the team (I hope) and I'm glad it ended the way it did.
You can still build your Laravel app in a pretty similar fashion as you would have done 5 years ago and if you want, you can make use of the recent additions, so I think there's not too much to worry about to be honest. If you have outgrown the magic, isn't it pretty amazing that you can drop down one level of abstraction and just use symfony? Also, do you think you would've grasped many of the underlying features of symfony, if it wasn't for Laravel's opinionated wrapping in a nicer syntax (pardon my oversimplification)?
Nevertheless, I think it's good to keep up the warning signs and have this discussion from time to time. ;-)
-
Jetstream dropped support for translation/localization (?!)
The commit, the issue
They have good reasons to drop it, read the whole discussion under that commit, because it seems you didn't as those problems were discussed there.
-
Livewire Notifier
Make sure that Livewire and Alpine.JS are installed properly. The easiest way to do it is to install Laravel Jetstream with Livewire stack (post-install command php artisan jetstream:install livewire).
-
Implementing Laravel's built-in token authentication
More often than not when developing an application you're going to need some mechanism of authentication. Up until recently, Laravel shipped with a complete authentication toolbox: controllers, routes and views. Recently Laravel migrated a lot of its backend authentication functionality into Laravel Fortify and provided a frontend simple implementation using Breeze. There's also a more opinionated auth setup using JetStream which combines Fortify and other currently-popular frontend tools Livewire and (my personal favorite) Inertiajs.
django-unicorn
- Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
-
Coming to grips with JS: a Rubyist's deep dive
Then there are stack-specific libraries: StimulusReflex for Rails, Phoenix LiveView, Laravel Livewire, Unicorn and Tetra for Django, Blazor for .NET, … and the list goes on.
- Unicorn – A full-stack web framework for Django
-
Reflex – Web apps in pure Python
- you get one of the best ORMs in existence with great relationship handling and generated admins
https://www.django-unicorn.com/
Not 1.0 yet but I'm using it in production and omgosh is it easy to crank out UIs.
-
Django 4.2 Released
There's a brilliant project called Django Unicorn that aims to be the equivalent of Laravel Livewire for Django. You should take a look.
https://www.django-unicorn.com/
That and HTMX + Alpine.js are a strong combination.
(I also had a bash at building a similar tool for Django called Tetra but unfortunately haven't had the time needed to commit to it: https://www.tetraframework.com)
-
Launch HN: Pynecone (YC W23) – Web Apps in Pure Python
I think all LiveView frameworks should be part of this.
Here are two Python ones I've tried:
-
Frontend framework for django?
Django Unicorn is the closest thing that answers the question IMO. Personally, I've never used it since I don't want to lock myself into a Django-only way of doing things (at least, more often than I have to).
Have you looked into Django Unicorn?
-
Rails has Hotwire (which as I understand is an SPA-like integrated frontend with much reduced complexity), is there something analogous in Django? Is this what HTMX is? I really don't want to learn React or Vue..
When I was exploring the space, django-unicorn looked interesting also. But HTMX got me so far, so easily, that I didn't give unicorn a fair shake.
What are some alternatives?
breeze - Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind.
django-htmx - Extensions for using Django with htmx.
reflex - 🕸️ Web apps in pure Python 🐍
htmx - </> htmx - high power tools for HTML
PyWebIO - Write interactive web app in script way.
jwt-auth - 🔐 JSON Web Token Authentication for Laravel & Lumen
flet - Flet enables developers to easily build realtime web, mobile and desktop apps in Python. No frontend experience required.
Flask - The Python micro framework for building web applications.
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
inertia-laravel - The Laravel adapter for Inertia.js.
nicegui - Create web-based user interfaces with Python. The nice way.