I have gone thru the path for the local non-docker style development implementation straight into my WSL2/Ubuntu 20.04 on my Windows 10 machine.
When I run Q2 check everthing comes back green but when I run the server I get a login error during starting:
2021-11-05T08:58:01.651 q2_sdk.general INFO Calling invalidate on 1 HQs: ['https://stack.q2developer.com/sdk/elements/hq']
2021-11-05T08:58:01.652 q2_sdk.general INFO Sending HTTP request POST https://stack.q2developer.com/sdk/elements/hq/Q2API.asmx
2021-11-05T08:58:04.848 q2_sdk.general INFO Received HTTP response after 3195.04ms - OK
2021-11-05T08:58:04.850 q2_sdk.general ERROR Logon failure
2021-11-05T08:58:04.851 q2_sdk.general INFO Sending HTTP request POST http://dev-01.q2developer.com/sdk/elements/ardent/refreshCache
2021-11-05T08:58:05.041 q2_sdk.general INFO Received HTTP response after 189.84ms - OK
2021-11-05T08:58:05.042 q2_sdk.general INFO Ardent cache refreshed
The pages in online banking display correctly, but when my extension tries to set an item in cashe, there is a 500 error that fires:
ConnectionRefusedError: [Errno 111] Connection refused
2021-11-05T09:01:56.768 tornado.access ERROR 500 320d3f22a1794a88be7300ed75ffc365 POST
I've tried with both the environmental variables that are in the docs and also in updating the enviornmental variables to our DB port and SQL server name and still get the same errors. I'm trying out the non-Docker local environment because my Docker setup was running extremely slow compared to the response time I'm getting running directly in WSL.
Nice question, Justin!
I think we are going to go the route of supporting WSL as well for this. Setting all the environment variables is a challenge, but sounds like you are well on your way on that front. Regarding cache, you will likely need to run memcached directly on the box. Until we get a helper for it, you may try this:
sudo apt install memcached
memcached -d
