upgrade(WIP): litestar2.0 ,

[v3ss0n]

… yaml to 5.3.1 to make poetry happy

Pull Request Checklist

• New code has 100% test coverage
• Pre-Commit Checks were ran and passed
• Tests were ran and passed

Description

• upgrade: litestar 2.0
• upgrade: pydantic 2.2
• downgrade: pyyaml:5.3.1
• refactor: lib's dependencies and service , replaced with @cofin 's fullstack.
• upgrade: settings to pydantic 2.x using pydantic-settings

Close Issue(s)

[mbeijen]

Hi, I ran into issues with Poetry, which would be fixed by this PR. However the PR is failing I guess because you did not install and run pre-commit?
Can you maybe change that so this can get merged? If you have no interest or time anymore I can also do that, just let me know

[v3ss0n]

I am not sure decision on this,

We have a much full featured litestar-fullstack now . @peterschutt what do you think about this repo , will this be archived?

[JacobCoffee]

@peterschutt what do you think of this or this repo in general? plans to slim it down or?

[JacobCoffee]

it'd be cool to use our docker hosting we got sponsored from Docker to host free images

[peterschutt]

This was the last conversation about this repo that I'm aware of: https://discord.com/channels/919193495116337154/1154552571025956985/1154552571025956985

From that discussion it seems as though there is a place for an example that doesn't require the cognitive load that fullstack requires to get around it.

Whatever the future holds, this repo needs love and leaving it "unmaintained" doesn't do us any favors. We should probably make it private for the time being and assess.

[darinkishore]

This was the last conversation about this repo that I'm aware of: https://discord.com/channels/919193495116337154/1154552571025956985/1154552571025956985

From that discussion it seems as though there is a place for an example that doesn't require the cognitive load that fullstack requires to get around it.

Whatever the future holds, this repo needs love and leaving it "unmaintained" doesn't do us any favors. We should probably make it private for the time being and assess.

Just a quick bit of feedback, I started trying to implement litestar instead of flask, got like 3 hours into implementing the things from the fullstack repo, couldn't take the cognitive load, and decided to not go with litestar ATM (probably going to try again later, also have django background!)

this repo DEFINITELY has a place, a simple working example with the basics (ie: SQLAlchemy, maybe non-class based controllers, etc..) would be amazing for getting people onboarded a lot quicker. with django, you can set it up and start working and it doesn't feel like there's a whole lot to do to start productionizing, but here, it felt really overwhelming! just a little bit of feedback, hope provides some perspective.