Thanks for your reply. Yes, I executed the “./generate_local_ssl.sh” command and it generated a file in the certs directory but I’m not sure what I need to do with it beyond that.
After seeing the comment from @mBeierl, I searched “bash on windows” and came across the following article showing how to setup bash on a Windows machine, Windows Subsystem for Linux.
I was able to generate the “testing.key” and “testing.crt” file and can successfully start the boilerplate extension with “docker-compose up --build” command now and browse to viewer.html page by going to https://localhost:8080/viewer.html
Wanted to post this in case anyone else is having the same trouble getting started.
hey mrpurp, I’ve tried setting up the boilerplate using the Windows subsystem for Linux and bash. I’ve managed to generate the certs (needed to use dos2unix on generate_local_ssl.sh, for those wondering) but am unable to get “docker-compose up --build” with an “./entrypoint.sh: no such file or directory” error.
If you don’t want to bother with certs, you could always use ngrok for dev purposes. That’s what I did when making my extension and it worked perfectly. Not too hard to setup if you need help.
Thank you so much @mBeierl for the link to that new openssl req command and openssl.cnf file. I am running this on Windows 10 and my solution to this was to replace the openssl req command that’s given in the boilerplate example with the new one that @mBeierl provided. I was then getting the same ‘Subject does not start with ‘/’’ error that is described here on Stack Overflow (with solution).