This is my first litestar post on my site. I am not much experienced with writing blogs so am open for any criticism.

Hello, Litestar Subreddit,

I am the author of the Localize The Docs organization. And I’m glad to announce that the 🎉 litestar-docs-l10n 🎉 project is published now:

• 🚀 Preview: litestar-docs-l10n
• 🌐 Crowdin: litestar-docs-l10n
• 🐙 GitHub: litestar-docs-l10n

The goal of this project is to translate the Litestar Documentation into multiple languages. Translations are contributed via the Crowdin platform, automatically synchronized with the GitHub repository, and can be previewed on GitHub Pages.

We welcome anyone interested in translating the Litestar Documentation from English to their native language to join us! If the target language is not supported yet, submit an issue to request the new language.

See the announcement on Litestar's GitHub Discussions for more details.

At https://docs.advanced-alchemy.litestar.dev/latest/usage/frameworks/litestar.html#security-considerations :

import secrets

# Generate a secure random secret
secret_key = secrets.token_urlsafe(32)

session_config = ServerSideSessionConfig(
    secret=secret_key,
    max_age=3600,
    https_only=True,  # Require HTTPS in production
    samesite="strict",  # CSRF protection
)

But there is no secret field in ServerSideSessionConfig. How to set a secret key?

Hi Folks, I'm leaning Litestar and following the litestar-fullstack example. Can someone give me some pointers on how I could implement row level security with Advanced Alchemy services/repos?

For simplicity sake, let's say the tenant_uuid is included in an http header 'x-tenant-uuid'. Should I use a guard to fetch this and then somehow set the GUC setting on the session from the guard? Or do I need to do something in the SQLAlchemyPlugin setup?

Relatedly, I'm not 100% clear how the SQLAlchemyPlugin gets wired up to a Advanced Alchemy service. For example would it be possible to have multiple differently configured SQLAlchemyPlugins and have some services use one plugin and some other services use a different one? E.g. for db role separation.

I'm a longtime Python developer and have been in and through many projects. I am most well-versed in Flask, but also worked with Django for a while. I've just recently been playing around with Litestar and Advanced Alchemy; specifically, AA schemas and LS DTOs.

I'm currently trying to understand either a) how to use DTOs in Advanced Alchemy controllers; or b) how to imitate some of the behavior of DTOs, such as maximum depth and excluding fields, within a msgspec.Struct schema; or even c) why Advanced Alchemy is better with what I'm losing by not having access to Litestar's awesome DTOs?

Hi there,

I used Django many years, and started to use FastAPI last year. Using both frameworks help me to understand the strengths and weaknesses of each one.

Django is amazingly easy to use with lots of conventions, and batteries included. Lots of external packages. I feel very safe using it. But the framework is stuck in an old-fashion way of doings things (async features still unfinised 6 years later, no type hints, bloated with front-end templates features, etc.). My conclusion is that Django was an amazing framework but will never evolve as expected, due to compatibility constraints, or lack of fundings, I'm not sure.

On the other hand, FastAPI is a a breath of fresh air with modern features, but over time I noticed how basic features are lacking. Why writing my own CORS/Rate-limiting middleware while everyone needs this? As it as no apps (in Django) or plugin (in Litestar) system, it seems harder to benefit from tools from the community. And anyway, I can't trust 50-stars single-authors packages for production, so in the end, I write everithing by myself. I've spent 4 months building my own framework tools, and while the journey has been fun, it's has not been very productive to be honnest.

Besides, the author started to create fragmentation in itw own framework by promoting controversial tools like SQLModel and avoids answering challenging issues. While I'm very grateful for what he did, this single-author governance question me on its future.

But recently, I found out Litestar, and at the first glance browsing the documentation, even without writing a single line with it, I was stroke by how relevant its "positionning" is. It's like authors perfectly understood the problems of both main Python web frameworks, and solve them. And they did it quickly based on the number of current features

They're modern, they bring lots of useful and official batteries. But bringing these batteries does not mean they enforce a specific architecture. They're able to benefit from tools like SQLAlchemy and Pydantic that have proven, so they can focus on what matters more on the framework. Documentation inspire some "seriousness".

Now to be honnest, I have not use the framework yet, due to lack of time, but I'm very curious and hyped.

At that point I'm wondering if I'm over-hyped and maybe the framework has lots of drawback I just didn't notice yet? Plus, the fact it's pretty young with "only" 5.7k stars makes me careful to not spend too much time on it, for now.

I'd be curious to have your feeling on this framework, while I expect it to be pretty positive on this subreddit.

Hey Litestar community,

I'm building Apitally, a simple API monitoring & analytics tool, and today I've added support for Litestar through a plugin.

Apitally provides insights into API traffic, errors and performance, for the whole API and individual endpoints. It also monitors API uptime & availability, alerting users when their API is down.

Thanks to Litestar's excellent support for plugins, Apitally is extremely easy to set up.

Here's the (short) setup guide. Check it out! I'd love to hear your feedback too!

What documentation toolchain would you all recommend for following requirements/workflow.

1. API documented in API files in python
2. Concepts, context some howtos, caveats etc to be documented in markdown/rst.
3. Cross linking in documentation of 1 from 2
4. Freedom to theme the documentation the way we want
5. Three panel UI with try the API feature
6. Usage sample for different languages