This will probably involve adding a configuration parameter for the "backend URL" (i.e. secure.clientcomm.org) and then making the logged-out homepage use that URL instead. In development, the config param would just be empty and the value would fall back to "/login" on localhost.
This will probably involve adding a configuration parameter for the "backend URL" (i.e. secure.clientcomm.org) and then making the logged-out homepage use that URL instead. In development, the config param would just be empty and the value would fall back to "/login" on localhost.