search

NikolaySuslov / livecodingspace

LiveCoding.space
MIT License
27 stars 7 forks source link

luminary branch #5

Open lazydino opened 4 years ago

lazydino commented 4 years ago

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..

image

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?

NikolaySuslov commented 4 years ago

Hello Reggie,

Sorry for awaiting an answer and thank you for your interest! Happy to announce, that Luminary full is now available just at master branch to try out. It is the functional prototype, comparing to the previous Summer's 2019 one. Also, there is no plans to continue development of luminary_partial branch anymore. There will be just one - Luminary full. To run by yourself, just be sure to use the latest master from GunDB lcs-storage and master from livecodingspace. Also want to mention, that all Reflector's related code is available and working in the same branch, so that users could choose the connection method. But, these methods can not work together for synchronising peers.

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

  1. setup GunDB storage / start lcs-storage locally
  2. setup LCS application / start locally
  3. turn on "Krestianstvo Luminary" switch on index page in web browser and check connection settings for proper lcs-storage url (localhost:8080/gun by default)
  4. start any virtual world instance from the list
  5. open another web browser (check/turn on "Krestianstvo Luminary" switch), locate World card with generated instance link, open it

More instructions and info about Luminary features will be in the near future.

Best regards, Nikolay

lazydino commented 4 years ago

Thanks for the instructions, GunDB Storage server still complains "Operations not permitted. ." I also noticed that the new LCS wouldn't serve anything under /setup where I used to set PUB KEY and initialize local cache.. Should I do /setup before enabling luminary via /setting ?

image

lazydino commented 4 years ago

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...

image