sidewinder VS jetstream

7 months ago I posted here about my open source starter kit Sidewinder https://github.com/stribny/sidewinder. The goal was to create a kit that would come prepared with development and deployment tools, mainly to deploy a Django app to a single private virtual server.

You can have a look at https://github.com/stribny/sidewinder where I styled the most important pages (https://github.com/stribny/sidewinder/tree/master/templates/account) for email-based login (no social login).

If you are talking about end-to-end UI tests, then using Playwright you can write your tests in Python and execute them together with other tests that you run with pytest. I have exactly this in https://stribny.github.io/sidewinder/ starter kit.

You should probably really define what you need a bit better. I have a starter kit (https://stribny.github.io/sidewinder/) that has some good defaults out of the box (like using django-allauth). Pair it with e.g. https://github.com/paddle-python/dj-paddle for Paddle (or something similar for Stripe) and you have a good base.

Feel free to check my Ansible playbook (`deployment`) folder of my starter kit: https://stribny.github.io/sidewinder/

You can see it working in a Django project here: https://stribny.github.io/sidewinder/

Check out https://stribny.github.io/sidewinder/, maybe that's what you next project will need :D

My first choice if the product is a good fit would be old school Django deployed to a single VPS (no docker). I am creating a public starter kit that does exactly that, including the deployment part: https://stribny.github.io/sidewinder/

However, there are lots of use cases that would call for additional SPA (Vue/Nuxt), or other tech. So in that case I'd add it or replace the tech stack entirely. I'd probably avoid specialized cloud services, might consider something like https://supabase.com tho if the app doesn't need a complex backend.

For writing models I would suggest using Action Closes. One example of them can be found in Jetstream's sourcecode. Actions are great to test in isolation and link to user stories.

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.

[1] https://jetstream.laravel.com

A well-implemented example of this would be in Laravel Jetstream, where an Actions namespace is defined for performing user-oriented tasks in Laravel Fortify — such as updating the user profile.

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.

Laravel provide us with robust solutions and starter kits for authentication so let's start by creating a new Laravel 9 project and install Jetstram

In terms off bullet points you added, I've made something pretty similar using Laravel with : Laravel Jetstream(application starter kit with inertia + vue stack) https://jetstream.laravel.com/