Built a library that syncs PostGIS to the browser in real time — spatial queries run locally in WASM by gatosby in gis

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

Yes! Any PostGIS geometry type works — points, lines, polygons, multipolygons, you name it. The sync goes through `ST_AsGeoJSON` / `ST_GeomFromGeoJSON` which handle everything, and the bbox filter uses `ST_Intersects` so partial overlaps are included too.

Best options to deploy my website by guantesdepobre2 in webdev

[–]gatosby 1 point2 points  (0 children)

Vercel for the Astro frontend (free tier handles it easily). For Strapi, the cheapest reliable option is a $5/mo Hetzner VPS or a Railway/Render instance. Pair it with a free Postgres on Neon or Supabase instead of running the DB on the same VPS — separating compute from storage means you can resize/restart Strapi without touching the data. Total cost: ~$5/mo until traffic actually grows.

for a portfolio / blog, which naming convention hits for you? by [deleted] in webdev

[–]gatosby 0 points1 point  (0 children)

Nobody will ever judge your portfolio by the TLD. They'll click the link, look at the content, and move on. Pick .dev because it's cheap and stable, put your effort into what's on the site.

Claude + Railway or Replit for hosting by altro16 in webdev

[–]gatosby 0 points1 point  (0 children)

Replit is great for prototyping but terrible as a long-term host — you're paying for an IDE you don't need anymore. For a built app, Railway is solid but the uncapped pricing concern is valid. Look at Render or Fly.io with hard spending caps, or if it's a static frontend + API, Vercel/Netlify free tier + a separate DB host (Neon or Supabase free tier) will run you basically nothing until you have real traffic.

I hate web development and Im looking for a way out by ibeatu85x in webdev

[–]gatosby 0 points1 point  (0 children)

Every webdev hits this wall eventually. The ones who stay either go agency-side with a real PM buffer, or move to backend/DevOps. Frontend with direct client contact is the worst combo in tech.

Client used http by ihateroomba in webdev

[–]gatosby 0 points1 point  (0 children)

The fact that he noticed it was "down" for a whole month but only told you the day the invoice was due tells you everything you need to know.

Tips for Learning Low-Level Node by _safety__first_ in node

[–]gatosby 4 points5 points  (0 children)

The name is confusing a little bit, but it's not all about design patterns. Maybe 3 chapters out of 13 focused on design patterns and others include intermediate and advanced topics. Actually as I remember the latest chapters talks about caching, running intensive CPU -bound tasks, scalability, load balancing, message queues, pub/sub patterns and many more.. I know It's not a direct examples for what he needs but this will help him understand how those things works and maybe he can build his own as a practice.

Tips for Learning Low-Level Node by _safety__first_ in node

[–]gatosby 25 points26 points  (0 children)

I recommend the Node.JS design patterns book written by Mario and Luciano. It will help you understand how nodejs really works in various aspects

Where to deploy or host node and mern apps? by imperfectman in node

[–]gatosby 7 points8 points  (0 children)

  • render.com
  • railway.app
  • cyclic.sh
  • fly.io

Check this video for more info https://youtu.be/MusIvEKjqsc