You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Theoretically the container should work fine with farming since all incoming traffic arrives at the same vhost. However the Farmer plugin requires to set up its own config_cascade wich currently conflicts with the one needed by the docker container.
It's probably easiest to adjust the farmer plugin to recognize the docker environment and integrate itself nicely into the cascade. The docker image needs to detect the farmer plugin and load the farmcore since the farmer plugin can not write to inc/preload.php
The text was updated successfully, but these errors were encountered:
This makes adjustments so that farming will automatically work as soon
as the farmer plugin is installed. The setup step can be skipped and
instead the plugin is preconfigured to use /storage/farm as farm dir.
!bang based animals are supported, but of course it makes more sense to
use a host based setup with docker. With a reverse proxy in front of
this image, it should be easy to point different host names at this
image. However this has not been tested yet and might need additional
adjustments in the farmer plugin.
A merge should only happen after this has been tested.
Theoretically the container should work fine with farming since all incoming traffic arrives at the same vhost. However the Farmer plugin requires to set up its own config_cascade wich currently conflicts with the one needed by the docker container.
It's probably easiest to adjust the farmer plugin to recognize the docker environment and integrate itself nicely into the cascade. The docker image needs to detect the farmer plugin and load the farmcore since the farmer plugin can not write to inc/preload.php
The text was updated successfully, but these errors were encountered: