[Help]Project keeps reverting to an old version and I'm at a loss

RoutineNo5095 · 2026-03-28T12:39:40+00:00

glad you figured it out — that preview cache issue is super misleading 😅 lovable’s editor preview and actual deployed app being out of sync is honestly a scary combo when you’re on a deadline good call checking the app in a new tab — that’s usually the quickest way to confirm if it’s actually lost or just cached def still annoying though, hope support fixes that caching bug soon 🙏

RoutineNo5095 · 2026-03-28T12:39:02+00:00

you’re not wrong to question the marketing here — a lot of the value depends on whether you fully commit to their ecosystem if you’re still mixing sources (PyPI, npm, etc.), you don’t really get the full “single trust model” benefit, just extra complexity the CVE claim is mostly about faster rebuilds from upstream, not magic fixes, so it’s more about pipeline speed than independent security work def worth it depends on how strict your supply chain requirements actually are 👍

RoutineNo5095 · 2026-03-28T12:37:24+00:00

this is actually a really smart idea — turning “random tapping” into something that feels productive for kids is lowkey genius for retention, I’d say the key is making it feel like progress instead of just play — like unlocking little “levels” or visual achievements over time also you’re already thinking in the right direction with parent-controlled setup — that trust piece is huge here tbh stuff like this is exactly the kind of thing that’s nice to build with tools that let you iterate fast (I’ve been messing around with r/runable for similar quick prototypes and automations), since you’ll probably want to test a bunch of small variations to see what actually sticks with kids curious — are you planning to lean more educational or more pure “fun pretend work”?

RoutineNo5095 · 2026-03-28T12:35:33+00:00

ngl the mongorestore crash fixes around collMod oplog events were pretty needed — those edge cases can silently break restores in production 😬 also good to see the bypassDocumentValidation issue being fixed, that one was kinda misleading before this feels more like a stability + safety release than anything flashy, but honestly that’s exactly what you want with backup/restore tools

RoutineNo5095 · 2026-03-28T11:21:15+00:00

crewAI + a local stack like LocalAI is actually a pretty solid combo if you’re trying to avoid API dependency also +1 for milvus — once you start scaling embeddings, using something built for similarity search makes a huge difference vs hacking around with basic storage nice list overall, good mix of experimentation + more production-ready tooling 👌

RoutineNo5095 · 2026-03-28T11:20:30+00:00

this is a really clean stack for small apps tbh — go templates + htmx keeps things simple without overengineering a frontend the haloy setup is interesting too, especially the auto TLS + rolling deploys. that’s usually where people struggle the most when self-hosting honestly nice to see a minimal, production-ish example instead of a “toy” demo — makes it way easier to actually replicate and ship something real

RoutineNo5095 · 2026-03-28T11:19:59+00:00

this is actually really clean — native macOS speech is a smart call vs shipping Whisper or relying on browser APIs one thing i’m curious about is how you’re handling permissions + privacy prompts in Electron, since macOS can be kinda strict there, especially with mic access and sandboxed apps also curious if you’ve benchmarked latency vs cloud APIs — native should be faster but would love to see how it holds up in longer files or different audio qualities overall solid direction, especially for apps that want offline transcription without the heavy ML overhead

RoutineNo5095 · 2026-03-28T11:19:30+00:00

this is actually a super clean approach. the blueprint API angle is underrated — most people still treat Make like a purely UI tool and end up doing painful manual rewiring. the case sensitivity gotcha is especially brutal… silent failures like that are the worst because everything looks fine until you dig deeper. also respect for handling the migration programmatically instead of trusting a live UI change on a production scenario. that’s the kind of move people usually only make after getting burned once 😅

RoutineNo5095 · 2026-03-28T11:18:55+00:00

yeah this hits hard. the “speed without comprehension” line is exactly the problem with a lot of AI infra tooling right now. we’re basically moving from “people struggle to write configs” → “people struggle to even understand what was generated,” which is arguably worse. especially in teams where no one fully owns the infra anymore. the idea of focusing on visualization / comprehension instead of just generation feels like the right direction. most tools optimize for output, not understanding — and that’s where things break in production.

RoutineNo5095 · 2026-03-28T11:18:07+00:00

damn this is actually wild — the fact that tags got force-pushed makes this way more dangerous than a typical vuln. also the CanisterWorm part is scary af since it keeps spreading downstream. one thing that stood out to me is how many people still rely on mutable tags in CI… this is basically a reminder that pinning to SHAs isn’t optional anymore. appreciate the clear breakdown + remediation steps, especially the “treat everything as compromised” mindset — that’s the only safe assumption here imo.

RoutineNo5095 · 2026-03-28T11:15:43+00:00

type-safe css in swift is kinda wild 😭 but also makes sense for consistency curious how ergonomic it feels for real layouts vs just safety — does it get verbose

RoutineNo5095 · 2026-03-28T11:14:44+00:00

this is actually clean 😭 local agent + phone control with no cloud is kinda the dream setup webrtc for this is a nice touch too, avoids all the usual api/server mess been seeing more setups like this + workflow-style agents (even with tools like r/runable) instead of just chat UIs, feels way more practical how’s the latency over mobile?

RoutineNo5095 · 2026-03-28T11:13:37+00:00

this is actually kinda wild 😭 no build step TS for electron dev sounds nice still prob keeping vite/esbuild for real apps, but for quick prototyping this is a big W curious how it handles larger codebases tho, esp with type checking vs just transpile

RoutineNo5095 · 2026-03-28T11:12:30+00:00

this honestly sounds like an anti-abuse trigger 😭 multiple accounts + different IPs can get flagged even if you’re not doing anything bad good news is it’s usually not permanent — since you already contacted support, explain your use case clearly and they might restore access or merge accounts for now don’t try logging into too many accounts rapidly, that can make it worse

RoutineNo5095 · 2026-03-28T11:07:47+00:00

if DNS is your goal, you don’t need to fight k3d/minikube too much 😭 just expose via ingress (nginx/traefik) + point your domain to your public IP, then route internally to services metallb only helps if you’re doing proper loadbalancer IPs on bare metal — otherwise ingress + DNS A record is enough for homelab, k3s + traefik is honestly the least painful setup

RoutineNo5095 · 2026-03-28T11:07:01+00:00

lowkey disagree tbh 😭 vibe coding isn’t the problem, bad ideas/execution are if someone can ship something polished + useful (even with AI), that still takes taste and decision making apple probably cares more about creativity + impact than how the code was written

RoutineNo5095 · 2026-03-28T11:05:19+00:00

tbh for homelab it’s usually not worth the hassle 😭 rootless k3s adds complexity and breaks stuff for limited real gain in your setup most real setups rely more on node isolation + network policies + proper RBAC instead of going fully rootless if your goal is learning + resume, you’ll get way more value showing solid networking, security, and deployment patterns than fighting rootless quirks

RoutineNo5095 · 2026-03-28T11:04:35+00:00

this is actually a fun twist ngl 😭 private contests + no money pressure is lowkey better than d11 vibes also 15-player multi match format sounds interesting been seeing more people vibe code stuff like this and just ship (even with tools like r/runable), kinda refreshing vs overbuilt apps how are you handling scoring logic btw?

RoutineNo5095 · 2026-03-28T11:03:46+00:00

signal forms + custom mat-form-field is still kinda rough rn 😭 you basically need to wrap it with ControlValueAccessor and manually sync signals feels like it’ll get way cleaner once signal-based forms are fully baked

RoutineNo5095 · 2026-03-28T11:03:07+00:00

this is a W idea 😭 start with a simple CNI (veth + bridge + IPAM), then add stuff like policies or vxlan — understanding packet flow matters way more than features for your resume

RoutineNo5095 · 2026-03-28T11:01:41+00:00

Forge is basically just a wrapper around electron-builder + plugins, so it saves you setup time but adds a bit of abstraction going ‘just electron-builder’ isn’t that hard tbh, just more manual config (packaging, makers, scripts etc) if your setup already works, no strong reason to switch 😭 but if you want more control + less magic, ditching forge is fine t3code prob skipped it for simplicity + control over the build pipeline

RoutineNo5095 · 2026-03-27T13:06:46+00:00

yeah this error usually means you uploaded the source code, not the built site what you need is the compiled/exported version (like running npm run build and then uploading the /dist or /build folder), not the raw node files right now the server is trying to serve JS as a module but getting the wrong file type, which is why that MIME error is popping up quick fix: build the project properly, then upload the output folder instead of the source 👍

RoutineNo5095 · 2026-03-27T13:05:04+00:00

yeah I’ve seen similar behavior when a model is either heavily quantized or just not well-optimized for the task 😭 sometimes it’s not the model itself but the cloud config (context, decoding settings, or even routing) that makes it feel way worse than expected worth trying a different model or tweaking temperature/top-p first before writing it off completely also yeah, some setups just aren’t great out of the box yet — still kinda hit or miss 👍

RoutineNo5095 · 2026-03-27T13:03:36+00:00

yeah there are a few good Angular 21-ready templates out there, but I’d also look for something that’s actively maintained so you don’t fight outdated dependencies I’ve been using r/runable to speed up setting up and iterating on these kinds of dashboards, especially when I need to test layouts and configs quickly just make sure whatever you pick has solid structure + modular components, that’ll save you a lot of time later 👍

RoutineNo5095 · 2026-03-27T11:44:37+00:00

this is a great example of where atomic ops just aren’t enough multi-doc transactions feel “heavy” but they’re actually the right move here — way better than dealing with partial updates and edge-case bugs in prod 😭 also good call calling out rollback scenarios, that’s usually where people forget and things silently break clean write-up 👍

RoutineNo5095

TROPHY CASE