-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
luminary branch #5
Comments
Hello Reggie, Sorry for awaiting an answer and thank you for your interest! To "verify that the GunDB P2P messaging is actually replacing the original vwf reflector" - just don't setup or start / connect to any Reflector server
More instructions and info about Luminary features will be in the near future. Best regards, |
I deployed the gundb storage project to WSL 2 today, and the storage server is not complaining. This looks like a platform issue of GunDB on Windows... However, I still could not, or don't know how to run a demo for the current codebase... I thought I will start with a two collaborators session, with user 'admin' signing to the sever launching an A-Frame app, and a second user 'reggie' joining the session via clicking the session id of the app on the proto list. I could not even gain the app list to perform this simple task... How can I get 'Default World Protos' work again like the current livecoding.space website? On local test, when user is login, clicking on 'DEFAULT WORLD PROTOS' button renders the page awaits some result with the top bar blinking... Clicking 'MY WORLD PROTOS' won't produce the app list unless I login as 'admin' ( in this case, it actually produced the 'DEFAULT WORLD PROTOS' )? I suspect the website is not initialized correctly as before with '/setup' dialog? Is livecoding.space allowing new user registration? I have problem signing up with new user names to do live tests... |
Hi Nickolay,
I've read the materials you posted at Kristinstov blog , below is some questions regarding to the luminary branch.
Not finding special instructions about luminary branch, so I start up the three servers as if I am
trying the master branch. I run the storage server, the reflector and the main livecoding vwf apps server with config and/setup properly updated like before as you instructed. I have no idea what I am running with the codebase, but it reported a few errors (invalid graph?) for storage server..
It seems I won't get any visible differences for rendering with the luminary branch visiting VWF apps served from localhost:3007. Besides looking into the source files, could one verify that the GunDB P2P messaging is actually replacing the original vwf reflector? Does luminary_partial branch need to participate in the shared session?
The text was updated successfully, but these errors were encountered: