Best Practice for reviewing each workspace and launching project from each workspace. #7
Replies: 1 comment
-
|
Leaving an update on this. After having a deeper look at the .conductor/ I was able to get a better idea of how to use each branch. I then used the built in terminal in each workspace and launched my app from there (after moving the .env, creating a .venv, uv sync, then on the frontend installed the npm modules and then I was able to launch it. I think I saw something about a setup script but couldn't find that in the settings. is there a reason that the worktree are connected to a github clone, rather then my local app where everything is already set up? ---- Aside for figuring that stuff out, The app was a joy to work in. really nice. Thanks. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I've just downloaded and have been trying out conductor. It looks really nice and has been super smooth so far connecting my projects repo and spinning up two workspaces to address two difference issues. My app is a FastAPI backend + React frontend. I have a MakeFile that kills any existing ports and fires up my backend server on localhost:3000 and my frontend on localhost:573*. My question is this, when the two workspaces each have their own branch but if I open my project in vs code. I don't see these branches, so I'm wondering what you recommend as the best workflow for seeing each agents work and launching my project with those branch changes. Sorry if this is obvious but I've never used worktrees before. Thanks
Beta Was this translation helpful? Give feedback.
All reactions