r/vercel

Used eve to build this. Marketers are loving it.

Hey everyone, I am back in my journey to try and quit smoking again I’ve tried multiple times now through going cold turkey but I just suck terribly at it, so I thought of lowering the cigarettes day by day.

I did this as a fun project with the help of AI it’s just a web app, non commercial no data tracking just pure use, i’ll provide the link for you to test if you want to give it a go. (If you want to actually save data locally and give it a go u can just click share > add to home screen (on IOS) and it should work.

Basically it has a few features i thought of: implement a timer between cigarettes that u can adjust on settings, where the app refuses the cigarette with an animation which u can override.

A breathing stabilization to try and control the cravings and a few other features you can see yourself.

P.s i think the photos aren’t loading properly.

Here is the link: https://ember-six-wheat.vercel.app

just would appreciate some feedback

Hi everyone, I need help with my web application deployment.

I deployed my Next.js web app on Vercel. The deployment is successful, but when I open the live website, I get a server error.

My database is MySQL and it is hosted on Railway. I already added the database connection URL/environment variables in Vercel, but the app still shows a server error.

Can anyone guide me on how to debug this properly?

Details:

* Frontend/Backend: Next.js on Vercel

* Database: MySQL on Railway

* Problem: Server error after deployment

* Local project works, but deployed version has an issue

What should I check first: Vercel environment variables, Railway database connection, build logs, or API routes?

Not a promo, just a genuine thank-you to Vercel.

A few months ago, I started Tabularis, an open-source desktop database client, mostly out of late-night frustration with the existing tools. Today, I got the email accepting it into the Vercel Open Source Program.

I’ll be honest: I’ve been a Vercel fan for years, so this one hit a little differently.
The part that made me smile is what gets supported: the site itself.

tabularis.dev (docs, blog, changelog, plugin pages) is an open-source Next.js app, static export, deployed on Vercel. So it ended up being an open-source database client with an open-source website, both backed by the same program.

How this actually helps the project:

• Next-level preview deploys: Since the site is mostly Markdown, being able to review every docs change or blog post, including dynamic OG cards, exactly as it will look live has already saved me from shipping so many typos.
• Zero-friction staging: It makes it incredibly easy to experiment with the "boring-but-important" stuff I've been pushing off, like custom search indexing and performance tweaks, without breaking production.
• Automated workflow: It just automates the whole deployment pipeline, meaning I can spend less time wrestling with DevOps and more time actually building the DB client.

Anyway, a huge thanks to the Vercel OSS team for backing a young project. It genuinely means a lot.

• The full story: tabularis.dev/blog/vercel-open-source-program
• The project (GitHub): github.com/TabularisDB/tabularis

Drop any questions about the DB client or the setup below, happy to chat!

woke up to a massive surge in edge function execution costs on our production build and ngl im completely losing my mind right now. Turns out some random scraping bot farm found our unauthenticated api endpoint and just spent 48 hours spamming parallel requests

The worst part is we were using a basic checkbox captcha but modern headless browsers just breeze right through them anyway. Its so frustrating that small dev teams have to tank unexpected cloud infrastructure bills just because malicious automated traffic is incredibly cheap to run nowadays

Im looking into completely refactoring how we protect our endpoints. Been reading up on gating critical api routes with decentralized proof-of-human protocols, like hooking up an Orb auth flow to completely wall off scripts before they can even trigger a serverless run. anyone else dealing with insane automated traffic spiking their deployment usage lately? literally about to set up hyper-aggressive rate limiting but it always ends up blocking legit users