-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add a task to run manual tcb commands #284
Conversation
71e0237
to
b0abafb
Compare
OK, I had to add a custom bashrc file to properly source tcb-env-setup and make sure that the alias was available. This worked in my checked out sources. I'll try to modify my config to pull a fresh project from my fork to test the full workflow. |
I was able to test this from scratch creating a new project using my fork of the templates. From my POV this is good to go. |
Please add it also to update.json, so it gets updated with the |
@andreriesco I don't follow. What do you want me to list in update.json? |
Actually, this script is to be used exclusively with the TCB IDE template, or do you think that being able to call this task can be beneficial on any other template also? |
I was only thinking of the TCB template. I don't currently have any need for it in the other templates. |
I think it can be added to the |
@andreriesco I still don't understand. What is it I should add to |
This file is for the
And with this script at
|
OK. Done. |
Also, the |
…nabled. This task will clear DOCKER_HOST and automatically source tcb-env-setup.sh making it easy for users to run manual commands. Signed-off-by: Drew Moseley <drew@moseleynet.net>
@andreriesco anything else here? |
No, now it looks good to me. I will merge it, thanks |
This adds a task to launch a terminal with tcb-env-setup.sh already sourced and the DOCKER_HOST variable cleared.