-
Notifications
You must be signed in to change notification settings - Fork 171
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
Does it works on replit? #277
Comments
Hi there. I'm not familiar with replit, so I can't completely offer any advice on what may be going on there. What output do you see if you run
|
so i create a file check-gl.js to test it on replit which is a linux platform too.
and i run the script with:
and the result is "ctx null" |
Have you made sure to install the relevant dependencies for your system?
Note: these dependencies vary by system, and I'm not familiar with the replit environment, so I can't advise more specifically. |
I have installed all the necessary packages through replit.nix. Without these installations, the node-gyp build phase would not complete successfully.
|
So, I am considering leaving it as is and migrating to another hosting site. Do you have any suggestions for hosting sites that might support these packages? |
I just moved to DigitalOcean, and it works now. Thanks for your help, bro! |
Glad you were able to get it to work. Generally, it shouldn't depend on a specific hosting provider – it more so depends on the environment that you're trying to get it to work in, and what complications/restrictions it imposes. It's possible with more work you might have been able to get it set up in Replit/Nix, but it seems like there were an unknown number of obstacles in the way. |
I also try to running with below scripts:
xvfb-run :99 -screen 0 1280x1024x24 & export DISPLAY=:99; npm run start:live
xvfb-run :99 -screen 0 1024x768x24 & export DISPLAY=:99; npm run start:live
xvfb-run -s "-ac -screen 0 1024x768x24" npm run start:live
xvfb-run --auto-servernum --server-num=1 -s "-ac -screen 0 1280x1024x24" npm run start:live
with gl version: "^6.0.2",
Errors:
THREE.WebGLRenderer: Error creating WebGL context.
file:///home/runner/frame-cube/node_modules/three/build/three.module.js:28929
throw new Error( 'Error creating WebGL context.' );
^
Error: Error creating WebGL context.
at new WebGLRenderer (file:///home/runner/frame-cube/node_modules/three/build/three.module.js:28929:13)
at CubeView.initScene (file:///home/runner/frame-cube/src/utils/rubik/cube-view.js:34:21)
at new CubeView (file:///home/runner/frame-cube/src/utils/rubik/cube-view.js:12:10)
at Rubik.renderToBase64 (file:///home/runner/frame-cube/src/utils/rubik/index.js:23:17)
at renderFrameUnsolvedRubik (file:///home/runner/frame-cube/src/controllers/rubik-controller.js:32:18)
at startSession (file:///home/runner/frame-cube/src/controllers/rubik-controller.js:72:5)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
The text was updated successfully, but these errors were encountered: