Closed EMREOYUN closed 3 years ago
As of v1.1, KockaLogger expects Redis to be running, so the Redis server needs to be started up with redis-server redis.conf
(on Linux, ./redis.sh start
). Does that work for you?
Also, since you're trying to start up KockaLogger, I need to cite this part of the README:
After Fandom decided to forbid WikiaActivityLogger on 25th June 2018, they provided an alternative solution to wiki activity logging that does not consume as much server (and bot) resources. This solution, however, is not publicly available and therefore KockaLogger cannot be used by any Fandom user like WikiaActivityLogger could.
Have you obtained the necessary configuration? If you haven't, you might be interested in a solution such as RcGcDw instead.
As of v1.1, KockaLogger expects Redis to be running, so the Redis server needs to be started up with
redis-server redis.conf
(on Linux,./redis.sh start
). Does that work for you?Also, since you're trying to start up KockaLogger, I need to cite this part of the README:
After Fandom decided to forbid WikiaActivityLogger on 25th June 2018, they provided an alternative solution to wiki activity logging that does not consume as much server (and bot) resources. This solution, however, is not publicly available and therefore KockaLogger cannot be used by any Fandom user like WikiaActivityLogger could.
Have you obtained the necessary configuration? If you haven't, you might be interested in a solution such as RcGcDw instead.
.sh files cannot be run because i'm using Windows Server
Yeah, as I said, you can run redis-server redis.conf
from the project directory to start up the Redis server on Windows (or use something like Cygwin, WSL or Git Bash to run them).
Yeah, as I said, you can run
redis-server redis.conf
from the project directory to start up the Redis server on Windows (or use something like Cygwin, WSL or Git Bash to run them).
It can't. Redis installed(i mean externally installed) for another project and since config made for Linux, Windows Version Redis can't run unless i need remove half of config(it does not work with this way also).
If you're running Redis for another project, you can change the socket path in include/client.js
to have KockaLogger connect to it. Since it's probably not running on a Unix socket, you can change it to something like:
this._cache = redis.createClient({
host: '127.0.0.1',
port: 6379
})
If you're running Redis for another project, you can change the socket path in
include/client.js
to have KockaLogger connect to it. Since it's probably not running on a Unix socket, you can change it to something like:this._cache = redis.createClient({ host: '127.0.0.1', port: 6379 })
This code resolved my issue. Thank you.
Closed #39
Description
Redis can not be startable and npm start command fails because of Redis not found.
Reproduction steps
Steps to reproduce the behavior(Windows only):
Expected behavior
Redis should up and no errors happen about Redis
Media
Notes
Windows Server 2012 R2 with Redis(Windows Version) Installed.