Add clinic@windows setup instructions #206
Conversation
- Update k8s development values to follow latest changes in charts.
- There's no need for separate statements. - Adds sql that just cleans symmetric db.
- Updates certs generation scripts to work across systems. Problems were identified when running from windows.
mateuszkrasucki
force-pushed
the
add-windows-clinics
branch
from
aa46b8f to
14a5027
Compare
docs/windowsClinic.md
Outdated
|
|
||
| ``` | ||
| docker-machine stop | ||
| vboxmanage sharedfolder add default --name "iryo" --hostpath "${PWD}" --automount |
There was a problem hiding this comment.
When virtualbox is installed with Docker Toolbox vboxmanage executable is not found on $PATH.
Error thrown:
vboxmanage: the term 'vboxmanage' is not recognized as the name of a cmdlet ...
To fix user should run the following script in command line:
$regPath = 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment'
$currentPath = (Get-ItemProperty -Path $regPath -Name PATH).path
$newPath = $currentPath+';c:\Program Files\Oracle\VirtualBox'
Set-ItemProperty -Path $regPath -Name PATH -Value $newPath
docs/windowsClinic.md
Outdated
| Run in powershell (as admin) while being in IRYO WWM dir: | ||
|
|
||
| ``` | ||
| docker-machine stop |
There was a problem hiding this comment.
in my setup docker-machine stop failed to actually stop the VM running inside VirtualBox. docker-machine's state put the "machine" to stopped mode and lost an ability to manage VMs in virtualbox.
There was a problem hiding this comment.
This setup with virtualbox feels very fragile to me. I was only able to run the vboxmanage ... comand after manually opening the vbox file located in ~/.docker/machine/machines/default/default/default.vbox. After that, the VM actually got listed in virtualbox's UI and was available to vboxmanage. I mean it's not something we can't work around, but does feel broken.
There was a problem hiding this comment.
For now I've changed this description to just set it up in Virtual Box GUI when using Windows Home. This seems to work when you do not touch anything after initial Docker Toolbox installation. I've also added Windows Pro setup.
- Makes local symmetric configurable using environment variables to easily specify configuration when running with docker-compose.
- updates Dockerfile of postgres to make it work as well when running docker toolbox on windows.
- Adds avahi docker spec to allow for full deployment on windows laptop to be accessible with hostname.
- Adds preliminary docs and config for running full clinic deployment on Windows.
mateuszkrasucki
force-pushed
the
add-windows-clinics
branch
from
14a5027 to
9fa379b
Compare
- Adds more values to be configurable through environment variables. Defaults are set in .env files.
mateuszkrasucki
force-pushed
the
add-windows-clinics
branch
from
1a9e298 to
def82c2
Compare
- Adds support for cloudSymmetric endpoints basic auth.
mateuszkrasucki
force-pushed
the
add-windows-clinics
branch
from
def82c2 to
ea14481
Compare
- Updates the script to take the path to IRYO WWM DIR from env variable.
| ports: | ||
| - 80:80 | ||
| - 443:443 | ||
| - 8080:8080 |
There was a problem hiding this comment.
please add restart: always to all services
There was a problem hiding this comment.
I tested it on windows pro and the services are started automatically after reboot
| sed -i -e "s#^http.basic.auth.username=<CLOUDSYMMETRIC_BASIC_AUTH_USERNAME>##" /opt/symmetric/engines/local.properties | ||
| sed -i -e "s#^http.basic.auth.password=<CLOUDSYMMETRIC_BASIC_AUTH_PASSWORD>##" /opt/symmetric/engines/local.properties | ||
| sed -i -e "s#^http.basic.auth.username=<CLOUD_SYMMETRIC_BASIC_AUTH_USERNAME>##" /opt/symmetric/engines/local.properties | ||
| sed -i -e "s#^http.basic.auth.password=<CLOUD_SYMMETRIC_BASIC_AUTH_PASSWORD>##" /opt/symmetric/engines/local.properties |
There was a problem hiding this comment.
I thought symmetric handled those environment variables :)
No description provided.