Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
Server admin can set up a webdis[webd.is] backend for cross-ark chat support by specifying the URL in settings. No configuration needed on backend side.
webdis is a HTTP wrapper for redis[redis.io], so if setting it up yourself redis must also be installed.
There are docker and other conainers available that is more or less click and play.
Basicly you set up a redis+webdis server.
I set up a lxc debian container and installed them manually, but on of the docker solutions will work just fine.
Since I do not use docker myself I have not checked which ones work and not.
If you know how to make docker containers there is info on how to do it yourself on https://github.com/nicolasff/webdis
If not there are ready made ones out there.
If you get stuck on anything, feel free to ask.
edit: looked a bit more, this is likely the best docker container: https://hub.docker.com/r/nicolas/webdis
Thats the point i would know
Have you any experience in setting up a docker instance or other virtual machines?
I don't have the time right now, but later I can try to write up a guide of sorts specific to using docker to set up a webdis backend for Chat Evolved as that is probably the easiest for the less experienced :)
The only thing that are not specified was if the whole mod work without webdis or not.
But i think a guide for mod to setup is a good idea.
which was actually specified in the description:
Server admin can set up a webdis backend for cross-ark chat support by specifying the URL in settings. No configuration needed on backend side.
I altered it to be more precise:
To enable cross-ark chat server admin can set up a webdis[webd.is] backend and specify the URL in settings. No configuration needed on backend side.