self-host-csmm-support

very simple indeed..

yeah mine too other wise they wouldn't have migrated. etc'

yeah im going to assume its something simple, but i looked at your suggestions earlier and my redis is fine

yeah im at now the same stage your at discord chat bridge

yeah i gave up for the time being. even tried the docker and that compiled and ran but then ran into errors inside that

ignore that.. my ftp wasn't uploading the .env file only just figured it out

ive created one now granted ownership and flushed still getting the same message

thats what i did the first time

so you didnt create the db?

did you create another db? or just run the npm ci again after doing that?

mysql> DROP DATABASE csmm;
ERROR 1008 (HY000): Can't drop database 'csmm'; database doesn't exist
mysql> ALTER USER 'csmm'@'localhost' IDENTIFIED WITH mysql_native_password BY 'myverysecretepassword-noreal';
Query OK, 0 rows affected (0.18 sec)

mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.07 sec)

yeah still getting the same message

gonna try docker again

i just reset it all and did you flush privilegs after?

ive alter user and changed the pass

delete and reset? or clear table?

at first yes but once i dropped the csmm database and reset the password for the user csmm all was fine

@User 28138655 did you get this error at all>ERROR: Access denied for user 'csmm'@'localhost' (using password: YES)

just got the some error again.

yeah looking at those now

@User 28138655 maybe this?
https://discord.com/channels/336821518250147850/557233260200198166/1139774798621331497

maybe of some use?

```[app] info: Initializing custom hook (

discordChatbridge

)
[worker] error: undefined {"code":"E_HOOK_TIMEOUT"}

this is the first thing after sails on startup

cant even get that far lol

bot on the server?

it looks like a discord issue but ive reset everything and double checked tokens

there maybe something before it as thats just an echo like comment to say if it doesn't get what its looking for then throws that message out

no everything matches up

token?

something with discordchatbridge it doesnt like

from redis status

             └─709 "/usr/bin/redis-server 127.0.0.1:6379"

from .env

REDISSTRING=redis://127.0.0.1:6379

so that looks ok

ahh right so how do i get around this and get csmm to run?

There's a good blog post about it from one of the react creators: https://overreacted.io/npm-audit-broken-by-design/

Okay so the audit fix thing you do not want to run. It updates packages in a way that's untested and could very easily break things

this is my read out from npm after using the -audit fix

npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated codecov@3.8.3: https://about.codecov.io/blog/codecov-uploader-deprecation-plan/
npm WARN deprecated bull-board@2.1.3: 2.x is no longer supported, we moved to use @bull-board scope
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'csmm@2.2.0',
npm WARN EBADENGINE required: { node: '12' },
npm WARN EBADENGINE current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

npm WARN deprecated getting that alot :/

npm ci install --only=prod like this?

Ah yikes, should def be npm ci insteal of install there :(

initially i used the npm install --only=prod command via the docs but still gave me the same error

I'll mess with the self host when I get home see if I can get past that. Gives me something to tinker with

ahh right let me try this method then

Ohh that may have been the unraid image? I don't have much experience with that one tbh