Skip to content
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

How to watch in a docker container remotely #113

Open
UncleSamSwiss opened this issue Sep 8, 2021 · 2 comments
Open

How to watch in a docker container remotely #113

UncleSamSwiss opened this issue Sep 8, 2021 · 2 comments

Comments

@UncleSamSwiss
Copy link
Collaborator

i already added the icons dependency on adapter level.
now the build is working.
now i look for a solution for the watch command, because
i use a docker container on a remote machine (not wsl on windows)

Originally posted by @oweitman in ioBroker/adapter-react#22 (comment)

@UncleSamSwiss
Copy link
Collaborator Author

@oweitman What is exactly your setup and why do you need to run the adapter in a container on a remote machine?

@UncleSamSwiss UncleSamSwiss changed the title Hot to watch in a docker container remotely How to watch in a docker container remotely Sep 8, 2021
@oweitman
Copy link

oweitman commented Sep 8, 2021

I have various docker containers running on my nuc with a lot of main memory.
In addition to my productive iobroker, I also have my test iobroker running, with which I can quickly delete everything and start over again
i also have this as a development server, so that i can ideally develop the adapters in isolation from each other.

the development of the adapter part works perfectly with the help of the portainer console to start and stop the adapter in debug mode. I am currently still using chrome as a debugger but would like to switch to vs code
Half a year ago, I built a less than optimal solution for the adapter react part, in which the react build starts after each save and "iob uplod adapter name" is then automatically executed. that would be the part that I would like to optimize. the publish of the port 1234 did actualy not work, but have not yet investigated why. Maybe the ´dev web server is probably only available locally and the configuration must be adapted.

the development of the adapter in a docker container under wsl did not work, as you may have remembered, due to adverse circumstances and we did not find a solution together either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants