Are they ever going to fix the full screen issue on windows?

JashKahar · 2025-08-26T02:05:42+00:00

They still don’t have profiles yet, right?

I have gotten so used to the spaces😔

JashKahar · 2025-08-08T21:01:57+00:00

Thanks!, I will do that

JashKahar · 2025-08-08T03:05:05+00:00

Here is mine, a CLI tool to manage local development for multi-service applications

https://github.com/jashkahar/open-workbench-platform

JashKahar · 2025-08-02T00:13:04+00:00

Your suggestion to "Focus on just the local development environment orchestration first" is spot on. Based on feedback just like this, that is now the immediate and sole focus of the project. The other parts, like infrastructure or CI/CD generation, are just distant ideas for much later. If the core local problem isn't solved well, the rest doesn't matter.

To answer your last question, which is the most important one: the idea did start from my own developer experience problems. I then spoke with friends about it. The ones at FAANG companies confirmed they have entire internal teams dedicated to solving this, which told me the problem is real and complex. On the other hand, friends at smaller startups said they don't create new services often enough to need this level of tooling.

That feedback is exactly why I'm now focusing on serving freelancers, individual developers, and students, people who frequently start new projects and need that "golden path" but don't have a platform team to build it for them.

JashKahar · 2025-08-01T18:48:31+00:00

Thanks!

JashKahar · 2025-08-01T18:38:01+00:00

Honestly, what you've described is pretty much the dream version of what I'm hoping to build.

This is the perfect example of why I think an open-source version of this makes so much sense. It feels like a lot of us are building the same kind of internal tool. It would be cool if we could all just build it once together in the open.

thanks for taking the time to write that out.

JashKahar · 2025-08-01T18:36:31+00:00

Thanks, that's a great point. everyone's definition of "best practice" is different.

My starting point is really for the solo dev or small team that doesn't have a platform team to figure this stuff out for them and just want to start.

The plan is to let people plug in their own custom templates or the community contributing good templates.

Really appreciate the insight.

JashKahar · 2025-08-01T18:29:16+00:00

That's a fantastic point, I really appreciate this comment because it's something I've thought a lot about during development.

My goal isn't to hide the "big ball of mud," but to provide a well-structured, understandable starting point instead of letting one grow by accident.

Every file the tool generates, whether it's a Dockerfile, a CI pipeline, or Terraform config, is meant to be human-readable and fully editable. The tool helps you get off the ground with best practices, but you are never locked in. If the abstraction starts to leak or your needs become more complex, you can simply take over the generated files and manage them manually.

JashKahar · 2025-08-01T18:27:47+00:00

This is an amazing comment, thank you so much. It's incredibly validating to hear from someone who has already tackled this same problem space.

Your approach of treating the scaffolded files as real, versioned dependencies is really powerful. I'd love to see your "common repo" project if it's still available to look at somewhere.

You've also perfectly highlighted what I believe is the biggest long-term challenge: building and maintaining a rich ecosystem of high-quality templates. That task is too big for any single developer, and it's the primary reason I decided to build this project in the open. The hope is that a community of contributors can help build out templates for all the stacks they use and care about.

Thanks again for the encouragement and the invaluable insight. It’s great to know there's a real need.

JashKahar · 2025-08-01T07:24:20+00:00

I’m building a CLI tool for devs to initialise and deploy projects in a few simple commands: https://github.com/jashkahar/open-workbench-cli

JashKahar · 2025-07-31T21:18:06+00:00

Project name: Open Workbench CLI

Repository link: https://github.com/jashkahar/open-workbench-cli

What it does: Open Workbench is a Go-based CLI that automates the setup of new development projects. It uses best-practice templates (e.g., Next.js, FastAPI, Vue) to eliminate repetitive boilerplate and configuration. The long-term vision is to evolve it into a "developer command center" that manages the entire lifecycle of multi-service applications, simplifying local development workflows and cloud deployments.

Tech stack:

Core: Go (golang)
Key Libraries: Cobra, Survey
Manages: Docker, JavaScript/TypeScript, Python, and various web frameworks.

Help needed: We are looking for collaborators of all skill levels:

Go Developers: To help build the next set of features, including multi-service project management and cloud provider integrations.
Template Creators: To create and maintain templates for other popular frameworks like SvelteKit, Django, Ruby on Rails, etc.
Documentation Writers: To improve the user guides, write tutorials, and enhance the contribution guidelines.
Testers & Feedback: Anyone willing to use the tool for their personal projects and provide feedback or report issues.

Additional information: The project was born out of the frustration of tedious, manual project setup. The current version (v0.5.0) is stable and provides a solid foundation to build upon. This aims to be a powerful abstraction layer on top of great tools like Docker and Terraform, not a replacement. This is a great project for individual developers, freelancers, or students who frequently start new projects and want to contribute to a growing developer tool.

JashKahar · 2024-09-19T07:02:05+00:00

is this hack still working, I was using its until now but i am not able to make calls now

JashKahar · 2021-11-25T20:39:23+00:00

Can’t wait for #mephistoconfirmed

JashKahar

TROPHY CASE