Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure production neon db to use Cloudflare Warpdrive #116

Open
1 task
rak3rman opened this issue Mar 13, 2024 · 0 comments
Open
1 task

Configure production neon db to use Cloudflare Warpdrive #116

rak3rman opened this issue Mar 13, 2024 · 0 comments
Assignees
Labels
backend Related to the hono backend chore Updating package.json, etc; no production code change

Comments

@rak3rman
Copy link
Member

rak3rman commented Mar 13, 2024

Description

Follow the tutorial below to get Cloudflare Warpdrive configured with the production Neon database instance. If you're feeling adventurous and it is possible, explore automatically standing up hyperdrive on staging environments and how these configurations impact development environments (shouldn't have to use hyperdrive).

https://developers.cloudflare.com/hyperdrive/examples/neon/

Acceptance Criteria

Generated by Zenhub AI

  • Scenario: Configure production neon db to use Cloudflare Warpdrive
  • Given the production Neon database instance is set up
  • When the Cloudflare Warpdrive is configured with the production Neon database instance
  • Then the database should be able to use Cloudflare Warpdrive for storage and performance
  • And the development environment should not be impacted by this configuration
@rak3rman rak3rman self-assigned this Mar 13, 2024
@rak3rman rak3rman added chore Updating package.json, etc; no production code change backend Related to the hono backend labels Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Related to the hono backend chore Updating package.json, etc; no production code change
Projects
None yet
Development

No branches or pull requests

1 participant