Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@adamkasper
Copy link
Contributor

@adamkasper adamkasper commented Dec 14, 2025

related issue #700

@vercel
Copy link

vercel bot commented Dec 14, 2025

@adamkasper is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

@adamkasper adamkasper force-pushed the neon-serverless branch 3 times, most recently from 2351514 to 46c0815 Compare December 14, 2025 08:09
@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 14, 2025

npm i https://pkg.pr.new/@nuxthub/core@713

commit: 52b26d3

@adamkasper
Copy link
Contributor Author

adamkasper commented Dec 14, 2025

@atinux Hey, I have another question about this. In the code, I noticed that during the build, the connection string is taken directly and its value ends up hardcoded in the final build output. Wouldn't it be better if it just used something like process.env.DATABASE_URL instead?

Of course, it would need to be implemented in a universal way (not just process.env.DATABASE_URL), but it doesn't seem ideal to me to have the actual connection string value baked right into the build. For a while, I was confused when I did a local build and deployed Nuxt locally via Wrangler to CF Workers — in the code, I had the local connection string, and I couldn't figure out why it wasn't working with the DATABASE_URL set in CF Worker Secrets.

Snímek obrazovky 2025-12-14 v 11 19 03

@vercel
Copy link

vercel bot commented Dec 15, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
nuxthub Ready Ready Preview Dec 15, 2025 11:19am

@atinux atinux merged commit c7f983b into nuxt-hub:main Dec 15, 2025
3 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants