Drizzle Kit Studio inaccessible in cloud development environments
Description:
I'm encountering an issue with Drizzle Kit Studio when developing in cloud-based environments. The problem persists across multiple platforms, including Gitpod, GitHub Codespaces, and Project IDX.
Environment:
Next.js version: 14.2.5
Drizzle Kit version: 0.23.0
Cloud environments tested: Gitpod, GitHub Codespaces, Project IDX
Issue:
When running the Next.js development server, it's accessible via a URL like https://3000-user-project-nntl5ty9mky.ws-eu115.gitpod.io/.
Drizzle ORM functionality works as expected within the application.
When attempting to run Drizzle Studio, it provides a https://local.drizzle.studio URL.
Clicking on this URL results in a "waiting to connect" message with no progress.
Checking opened ports in the cloud environment reveals a different URL (e.g., https://3000-user-project-nntl7f96mky.ws-eu115.gitpod.io).
Accessing this URL results in a 404 Not Found error.
Expected Behavior:
Drizzle Kit Studio should be accessible and functional when developing in cloud environments.
Steps to Reproduce:
Set up a Next.js project in a cloud development environment (Gitpod, GitHub Codespaces, or Project IDX).
Install and configure Drizzle ORM and Drizzle Kit.
Attempt to run Drizzle Studio.
Additional Information:
This issue occurs consistently across all tested cloud environments.
I've been unable to find any relevant information online regarding this specific problem.
Questions:
Is Drizzle Kit Studio designed to work in cloud development environments?
Are there any known workarounds or configuration changes needed for cloud environments?
I've attached screenshots illustrating the problem. Thanks for any help in advance!!!
![No description](https://cdn.answeroverflow.com/1265718026821697646/image.png)
![No description](https://cdn.answeroverflow.com/1265718027123560448/image.png)
4 Replies
👋 I guess it will be solved by #gateway
Thanks for responding, do I need to repost it there?
Ah sorry I mean that a new product will be launched next week or so (code name: gateway)
Ooh I see, so there's currently no way to fix it.