⌘K
Phil Wolstenholme Looks cool :) How does this fit in with https://github.com/vercel/next.js/discussions and https://github.com/vercel/vercel/discussions?
Amy Egan Hey @philwolstenholme! At the moment we've moved https://github.com/vercel/community/discussions and https://github.com/vercel/vercel/discussions to this new site since they're both entirely Vercel projects. The open source repos, like https://github.com/vercel/next.js/discussions, affect groups that span a bit outside of Vercel. So we'll coordinate with the folks running each of those open source projects to determine the best plan to suit their needs in the future. Everyone is also welcome to chat about our projects here!
Dikozimpact Clearing the cache helped. Is there no other option to force cache clearing with versel so that it doesn't have to be done by everyone who visits the site?
Amy Egan Cache-Control headers let you control browser caching of your site. The default is `cache-control: public, max-age=0, must-revalidate` so the browser shouldn't cache, but some frameworks or individual project might set it differently. I recommend digging into the cache-control headers and framework configuration options of your site to make sure it's set up to behave the way you want.
Jino Sabu 1) When using v0 in mobile phones, selecting a chat from sidebar menu opens the preview of that app or site that created in that chat first instead of showing the chat section. It's very much annoying. Fix it please. 2) Add a drag handle or something in the top of the preview section when viewed in mobile phones to understand it can be dragged to bottom to view its chat section. Now, it's not easy to drag to the bottom. Please consider these issues and make v0 user friendly as soon as possible. Thank you
Amy Egan Thanks for the feedback! I shared it with the team
Amy Egan Can you share a screenshot of what's going wrong? Trying to understand if it's not saving changes, affecting only certain file types, or preventing manual changes entirely.
ADALIGO Thanks for sharing this **Amy Egan** 🙌 Super helpful guide. I’ve only been here a few days but already learned a lot — the community is really active and easy to navigate 👍
Belty6979 5979 Thanks for putting this together! I was new to the Vercel Community, and this guide made it much easier to understand where everything is and how to get started. Looking forward to learning more and being part of the discussions. Appreciate the effort!
Amy Egan Glad to have you here!
Joeyouss Hey @pbzona , great video! I couldn't join it live but just viewed. However, I do have a couple of questions: - For applications that require regional compliance, is WAF-based geo-fencing recommended, or are there other methods for redirecting specific regions? - Since billing is based on provisioned memory and execution time, does CPU adjustment impact costs? Thank you in advance!
Phil Zona Thanks! Great questions, and as you might expect...it depends :) WAF based geo-fencing is a great option for simple use cases where you just need to redirect users without any additional logic. Depending on what you're trying to comply with, I'd probably recommend managing these rules with Terraform: https://registry.terraform.io/providers/vercel/vercel/latest/docs/resources/firewall_config The alternative is to handle it in edge middleware. This gives you a lot more flexibility because you can execute whatever logic you need (if any). Depending on which version of Next you're using, you can access geolocation data directly on the request via `req.geo` (version <=14) or by using the `geolocation()` helper in `@vercel/functions` (version 15). Example for <=14: https://github.com/vercel/examples/blob/main/edge-middleware/geolocation-country-block/middleware.ts Example for 15: https://vercel.com/docs/functions/vercel-functions-package#geolocation Keep in mind that middleware is a billable resource - it is low cost and not something I've ever seen cause significant billing problems, but you would likely incur an invocation for every page since you mentioned this is a compliance use case. You can ballpark what your costs would be by assuming most edge requests you receive will also incur a middleware invocation. Check here for pricing: https://vercel.com/docs/functions/edge-middleware/usage-and-pricing#billing-information One way to mitigate this is by excluding things like static assets and favicon using a matcher - example: https://vercel.com/docs/functions/edge-middleware/middleware-api#match-based-on-a-negative-lookahead Re: CPU time, yes, thank you for flagging this - I should have mentioned it in the video. The CPU does indeed scale up and down when you adjust your memory allocation, even though it's not explicit in the config object. This can have a significant effect on CPU-bound workloads as they will have less resources, run more slowly (increasing function duration), and potentially throttle. Finding the right balance of performance and cost-efficiency is more art than science, but our solution for this (still in beta) is the observability tab: https://vercel.com/changelog/application-aware-observability-in-limited-beta If you're using our monitoring product, you should have access to this, so feel free to play around and let me know what questions you have. Docs are a bit sparse at the moment because it's being worked on so actively, but if you have feedback or anything that you'd like to see included in those views, we're always open to ideas. I hope this helps!
