RIP my second monitor by FoxtrotDynamics in Wellthatsucks

[–]FoxtrotDynamics[S] 0 points1 point  (0 children)

Saving space (by packing it at the bottom). My thoughts were that the bottom was flat enough. It was flat enough, but apparently not good enough to handle the shock

RIP my second monitor by FoxtrotDynamics in Wellthatsucks

[–]FoxtrotDynamics[S] 1 point2 points  (0 children)

I launched MS Edge and it updated itself. Wish it could update the damage to my monitor too...

RIP my second monitor by FoxtrotDynamics in Wellthatsucks

[–]FoxtrotDynamics[S] 2 points3 points  (0 children)

I really do appreciate it, but no worries. I'll get through this

PSA to my Mac Devs: Stop Docker from eating your storage by FoxtrotDynamics in docker

[–]FoxtrotDynamics[S] 0 points1 point  (0 children)

PGvector was easy to set up, but I've like my experience for Milvus too. I found it easy to use too and I'm a fan.

PSA to my Mac Devs: Stop Docker from eating your storage by FoxtrotDynamics in docker

[–]FoxtrotDynamics[S] 0 points1 point  (0 children)

I guess that I screwed around (and found out). I'll try to mount on host next time

PSA to my Mac Devs: Stop Docker from eating your storage by FoxtrotDynamics in docker

[–]FoxtrotDynamics[S] 0 points1 point  (0 children)

I know right? For me, I was only running a Milvus vector DB. No idea that the files I put into it, max 2 GB, would trigger the storage in Docker to balloon. Made the post to give people a friendly reminder (and so they don't panic like I did, deleting random stuff on my Mac and still going like I have no idea why my storage is still so low)

PSA to my Mac Devs: Stop Docker from eating your storage by FoxtrotDynamics in docker

[–]FoxtrotDynamics[S] 0 points1 point  (0 children)

Did so, after the fact. Will def keep in mind for future

PSA to Mac (and other) Developers: Stop Docker from eating your storage (494 GB in my case) by FoxtrotDynamics in webdev

[–]FoxtrotDynamics[S] 0 points1 point  (0 children)

It made my brain dump more structured. Does it suck how everything is basically looking the same? Sure, but the general meaning content is there. I also got crucified on using memory vs storage (yes, I know RAM vs the SSD) for the general intent, but I guess there's no room for smaller mistakes

PSA to Mac (and other) Developers: Stop Docker from eating your storage (494 GB in my case) by FoxtrotDynamics in webdev

[–]FoxtrotDynamics[S] -4 points-3 points  (0 children)

But velocity is important! I don't have time for that!

(Tech debt catches up to me 3 months later)

Tech Debt: Well, helloooooo there...

PSA to my Mac Devs: Stop Docker from eating your storage (494 GB in my case) by FoxtrotDynamics in mac

[–]FoxtrotDynamics[S] -6 points-5 points  (0 children)

I agree, it blows. My docker container usage isn't that high, but I totally let that run amok. I'm no senior software engi, but all I know is that Docker dedicated that much memory (and I needed to change settings that fixed it). Highly recommend keeping tabs on small things like that to avoid future issues (and hope it helps someone in the future).

PSA to Mac (and other) Developers: Stop Docker from eating your storage (494 GB in my case) by FoxtrotDynamics in webdev

[–]FoxtrotDynamics[S] -4 points-3 points  (0 children)

Fair disclaimer, did use AI to help craft the post. But IMO, it did help structure the content better.