jangxx/VRC-Avatar-Remote-Server

Outdated Packages

Opened this issue · 9 comments

Deleted user commented

When Im using docker I get stuck on the npm install. I have to do npm install --force in order to download the packages but then when I try to use docker after it. It just doesn't go past package 7/10

jangxx commented

Sorry, I fixed that a while ago but didn't merge it until now. I merged it now together with a new groupable control feature. Let me know if it works.

Deleted user commented

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: zod-express-middleware@1.4.0
npm ERR! Found: express@5.0.0-beta.1
npm ERR! node_modules/express
npm ERR! express@"^5.0.0-beta.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer express@"^4.17.1" from zod-express-middleware@1.4.0
npm ERR! node_modules/zod-express-middleware
npm ERR! zod-express-middleware@"^1.4.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: express@4.18.2
npm ERR! node_modules/express
npm ERR! peer express@"^4.17.1" from zod-express-middleware@1.4.0
npm ERR! node_modules/zod-express-middleware
npm ERR! zod-express-middleware@"^1.4.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\isuki\AppData\Local\npm-cache_logs\2023-03-03T19_35_19_182Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\isuki\AppData\Local\npm-cache_logs\2023-03-03T19_35_19_182Z-debug-0.log

Deleted user commented

Also documentation is confusing on how to run the server.

jangxx commented

Ah sorry, you need to run npm install --legacy-peer-deps, I still need to update the readme.

jangxx commented

Also I'm not sure what's confusing about it? The readme clearly lays out three ways of running it, including all commands you need to run.

Deleted user commented

C:\Users\isuki\Downloads\Remote Server\client>node ./ ./config.yml ./icons
node:internal/modules/cjs/loader:1063
throw err;
^

Error: Cannot find module 'C:\Users\isuki\Downloads\Remote Server\client'
at Module._resolveFilename (node:internal/modules/cjs/loader:1060:15)
at Module._load (node:internal/modules/cjs/loader:905:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at node:internal/main/run_main_module:23:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}

jangxx commented

You're in the wrong folder. Don't run this in /client but in the top level of the repo.

Deleted user commented

I think I did the setup wrong but I'll show log.

Where is the server being hosted at for instance localhost:8080?

C:\Users\isuki\Downloads\Remote Server>node ./ ./config.yml ./icons
Running first time setup
Are you running in docker right now? [y/N] y
You need to set an admin password before using this tool. Please enter it now.
Password: Error: canceled
at Interface. (C:\Users\isuki\Downloads\Remote Server\node_modules\read\lib\read.js:66:13)
at Interface.emit (node:events:512:28)
at [_ttyWrite] [as _ttyWrite] (node:internal/readline/interface:1131:18)
at ReadStream.onkeypress (node:internal/readline/interface:271:20)
at ReadStream.emit (node:events:512:28)
at emitKeys (node:internal/readline/utils:357:14)
at emitKeys.next ()
at ReadStream.onData (node:internal/readline/emitKeypressEvents:64:36)
at ReadStream.emit (node:events:512:28)
at addChunk (node:internal/streams/readable:324:12)

C:\Users\isuki\Downloads\Remote Server>node ./ ./config.yml ./icons
You need to set an admin password before using this tool. Please enter it now.
Password: ********

Retype password: ********

Admin password has been set successfully! You can now start the server again with the config file that was just created.

C:\Users\isuki\Downloads\Remote Server>node ./ ./config.yml ./icons
Server is listening on 0.0.0.0:8080
OSC messages will be sent to host.docker.internal:9000
OSC server is listening on 0.0.0.0:9001

jangxx commented

Why did you answer the question about docker with "yes", when you're not running inside of docker?

The first time you launch the server you are asked if you are currently running in a docker container. Answer this question with n

If you answer this with y it will write host.docker.internal as the OSC destination address instead of 127.0.0.1. But you can of course change this back in the config file.

Where is the server being hosted at for instance localhost:8080?

Yes, that's why the output says Server is listening on 0.0.0.0:8080.