I'm also helping Jonathan Ehwald as talk manager for his session at PyCon Italia.

Jonathan is presenting "What I learned migrating @FastAPI & Friends to uv", sharing lessons learned while migrating FastAPI, Typer, SQLModel and other projects to uv.

As someone who maintains libraries himself, it's great to hear practical advice from somebody who has already done the migration work at scale.

#PyConItalia #Python #uv #PyCon #FastAPI #Typer #SQLModel

#python #sqlmodel
How do you make a many-to-one relation ship while the one-part requires the relationship to be always set at creation?

🛢️🐍 #SQLModel - бібліотека для взаємодії з #SQL базами даних через #Python об'єкти. Розроблена командою #FastAPI для спрощення роботи з реляційними БД.

Ключові можливості:
• Інтуїтивний синтаксис на основі Python типів
• Повна сумісність з FastAPI та Pydantic
• Автоматична генерація SQL схем

⚡️ Технології: Python, SQLAlchemy, Pydantic
🛠 Платформа: Cross-platform

🔗 https://github.com/fastapi/sqlmodel

New blog post! I've been making great strides with my refactor, and now I'm on #SQLModel and #Svelte 5!

https://blog.blasphemess.com/build-one-to-throw-away/

It was so totally worth it to rewrite my game before launching it. Even if launching is the goal I'm rushing towards, I got enough feedback that necessitated a rewrite.

Build One To Throw Away

Building a prototype just to throw away all that code? It can be a good idea.

Blasphemess

I need to learn more about how databases work and the best way to setup relationships in SQLModel. I was working on Rack Root tonight and am still running into an issue with some circular dependencies I'm having between various tables. I need these relationships to enhance the data/utility of the app, but might need to rethink how I'm actually putting them together.

The other fun part of this is that I'm learning that the way I test the app and the way I run the app isn't always the same. The tests will run fine the first time against my test Postgres container, but subsequent runs don't work because of how I tell the test DB to drop all data before running the tests. It's complaining about the relationships, but really I think I need to tell it to either cascade delete or just ignore something.

#homelab #rackroot #programming #webdev #fastapi #sqlmodel #databases #alwayslearning

fastmeshapi: a fast, persistent Meshtastic web app (intro)

https://www.youtube.com/watch?v=UrFJZPjfopA

#meshtastic #lora #fastapi #sqlmodel #svelte

- YouTube

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

I am probably holding them wrong!

This time I tried writing a web app not in #php but #fastapi + #sqlmodel (python) and #vue3 ( javascript). It kind of works well but refactoring is a nightmare.

In the beginning, it felt like I was having the best of both worlds -- Python and Vue3. Dev speed was good. Now maintaining and refactoring make me feel like I am having the worst of both worlds.

As a single dev, I should have stayed with #php!

New blog post is up!

How I handled tracking DHCP ranges in Rack Root, some things I ran into along the way, and how I improved my pytest output.

https://medium.com/@a.j.longchamps/rack-root-devlog-tracking-dhcp-ranges-c8272001fe3a

#pytest #homelab #rackroot #devlog #blogging #fastapi #backend #databases #sqlmodel #programming #blogging

Rack Root DevLog — Tracking DHCP Ranges - Aaron Longchamps - Medium

In a recent blog post, I announced Rack Root to this side of the internet. As I write this, I am working through how I want to handle DHCP ranges, and this is some of my thought process. Rack Root is…

Medium
Primeiro Keynote confirmado para a #PythonBrasil2025 @tiangolo criador do #FastAPI #Typer e #SQLModel dentre outras ferramentas. Essa Python Brasil, como todas as outras, está imperdível.

Tonight's dev log update for Rack Root

I finally finished my refactor from sqlalchemy with sqlite over to SQLModel with PostgreSQL and refactored much of my code. I had a mixture of snake_cake and camelCase which has since been fixed to be all camelCase.

I adjusted many of my imports, classes, database tables, database foreign key relationships, and testing to fit the new design. I also had to adjust some of my tests because my IDs were off by one.

This database focused refactor also gave me all the structure and space I needed to build out the basic IPAM features. When a new network is added, all the associated IP records are created, and marked as 'Available'. If a gateway is set, that gets changed to 'Gateway' and when I implement DHCP ranges, that will be set to 'DHCP'.

I still have some things to do such as make sure the IP records cascade delete when a network is deleted, and fun stuff like that.

Now that the backend is (re)designed, I can get back to the front end side of things.

If you're curious to check out my code for this refactor, it's all up on my GitHub here:

https://github.com/alongchamps/rack-root/commit/0fc99dfcf10bf3ab6a5dfdc348894fe7e6221acd

#devlog #programming #rackroot #homelab #python #fastapi #sqlmodel #pytest #refactor #postgresql #backend

Merge pull request #1 from alongchamps/testing-sqlmodel · alongchamps/rack-root@0fc99df

Refactored the database layer, added IPAM features

GitHub