#nameko — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nameko, aggregated by home.social.
-
Wise words for Josh
(from Mushroom Dig for Android: https://play.google.com/store/apps/details?id=jp.co.beeworks.nameko.hkt)
#MushroomDig #AndroidGames #Nameko #funghi #nnf #MobileGames
-
Wise words for Josh
(from Mushroom Dig for Android: https://play.google.com/store/apps/details?id=jp.co.beeworks.nameko.hkt)
#MushroomDig #AndroidGames #Nameko #funghi #nnf #MobileGames
-
Aufgeklärt: Das „Stockschwämmchen“ in Konserven und Tiefkühlwaren
Das (echte) Stockschwämmchen und das chinesische Stockschwämmchen sind genetisch nicht verwandt und haben geschmacklich nichts miteinander zu tun. Das wildwachsende echte Stockschwämmchen soll nur von Kennern gesammelt werden.
👉 https://www.cvuas.de/pub/beitrag.asp?subid=1&Thema_ID=2&ID=4092
#Pilze #Vergiftungsgefahr #Nameko -
Years ago at #HockenberryCottage we inoculated a bunch of logs with #mushroom spawn. They haven't been the most successful so far, but sometimes the answer is just to be patient. Today I found a big flush of #nameko from one of our slighly buried inoculated log stacks!
-
Years ago at #HockenberryCottage we inoculated a bunch of logs with #mushroom spawn. They haven't been the most successful so far, but sometimes the answer is just to be patient. Today I found a big flush of #nameko from one of our slighly buried inoculated log stacks!
-
@dalbuschat
For (stateless) microservices I completely agree, we mostly deal with user facing webapps. Loads of generated form handling, grids an all that webby stuff that web2py & py4web do way better than fastapi (for me). Since I work a lot with interns and depend on them I have to consider the overhead of another framework.But fastapi is definitely on my radar!
Eventlet I've mostly used with #nameko iirc. Really like that framework as well.
Next stop is trying #faust
-
CW: 🤯 Wooot Finally solved a long standing issue with decentralized #cache invalidation!
I'm so excited; it took me roughly 5 years to get to a working solution, struggling through #redis, #nameko, #diskcache (and a slew of others) in my #python #microservices environment. Solved using a centralized #postgres database, which automatically triggers removal of items which depend on some data in the mutated row along with dependency registration in the application layer.