-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deploy front end connected to demo network #56
Comments
goal: 1 URL that's clearly working. @jimscarver notes http://rhobot.net:8888/ is close but lacks SSL. |
ssl is now supported at https://rgov.rhobot.net We are also creating a separate instance at demo.rhobot.net specifically for official demonstrations. |
seems like we're supposed to use http://demo.rhobot.net:8888/ |
demo rehearsal with http://demo.rhobot.net:8888/ was successful; that's what we plan to use. |
I note https://rgov1.netlify.app/ is now up-to-date. It doesn't default to the demo rchain network, but it does have SSL. I expect it's sufficiently reliable for the demo, but since it's not what we rehearsed with, I'm not sure we should switch now. On the other hand, http://demo.rhobot.net:8888/ isn't up-to-date with master (it still has 2 ToDo lists at the bottom and I suspect it's missing the fix for #57 ). So something should change. |
We're at T-2hrs and this is still open. Are we doing the demo
|
we went with http://demo.rhobot.net:8888/ |
I gather this is in progress; http://rhobot.net:8888/ https://rgov.rhobot.net/ have a rhobot network option.
When I first went to https://rgov.rhobot.net/ I ran into:
Perhaps this part is actually working. But reportedly "everything broke" and it's not clear to me whether the problem was in the back end network (#55) or this one.
@jimscarver @Bill-Keuntje is it clear who has the ball on this? Would you please nominate someone by assigning them?
The text was updated successfully, but these errors were encountered: