Skip to content

Add Scripts to start single services #24

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

Closed
robinduerhager opened this issue Apr 16, 2023 · 4 comments
Closed

Add Scripts to start single services #24

robinduerhager opened this issue Apr 16, 2023 · 4 comments
Assignees
Labels
scope: all An issue that is meant for all projects

Comments

@robinduerhager
Copy link
Collaborator

robinduerhager commented Apr 16, 2023

Being able to start single services locally could help in debugging them. Currently we always deploy the whole Infrastructure to Docker, though, often only a single service like drilbur implements a bug which diffuses through the whole software stack to the frontend. Deploy the whole infrastructure takes time so a npm run dev:drilbur etc. script would be helpful.

Deeply connected with #23

@robinduerhager robinduerhager added the scope: all An issue that is meant for all projects label Apr 16, 2023
@ropfoo
Copy link
Owner

ropfoo commented Apr 17, 2023

Well technically there already is a manual way to start single services (see the README)

npx turbo run dev --filter=drilbur

@robinduerhager
Copy link
Collaborator Author

Yeah i just want to have a script that is basically an alias for that in the package.json so i can type npm run dev:drilbur :D

@robinduerhager
Copy link
Collaborator Author

npm i -D esbuild is somehow necessary for local windows builds, see evanw/esbuild#1646 (comment)

@robinduerhager
Copy link
Collaborator Author

Closed by #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: all An issue that is meant for all projects
Projects
None yet
Development

No branches or pull requests

2 participants