At start-up time 'rhoconnect start' command checks only presence of redis service by pinging it (host and port are defined in setting.yaml file). You can start redis-server as s service and forget about it for awhile. Only matters host and port values in yaml file. They should match settings of running redis server.
Apparently, you encountered limitations of rhoconnect resdis-start command. It assumes default location of redis at
"C:/". You can redefine it by setting env. variable 'REDIS_HOME' to "D:/"
Hi Alex, thanks for the insight... based on my setup/environment I had to enter the entire path for the REDIS_HOME variable... as shown below:
It works now!!!
Not to dwell on this issue of spanning across multiple drives, but I tried moving my Rho app pojects (workspace) to C drive so that everything is running off of the same drive... it rendered the same unfavorable results. The fact that Rhoconnect commad file was unable to find redis is unsual expecially when the redis path noted above was already in my System Path.
Anyway, the addition of REDIS_HOME variable did the trick.
It would be helpful to add this tidbit to docs.... cheers and thanks again!