| [03:27:12] | <shmida[m]> | thanks. it workes. does it matters where to unpack the module? inside the docker container filesystem? or inside my host computer silesystem where the docker is mounting the app? does it matter? or it will duplicate both ways? |
| [07:43:23] | <mstenta[m]> | Anything you want to persist must be outside the docker container mounted in as a volume |
| [07:43:47] | <mstenta[m]> | What are your volumes right now? |
| [07:44:02] | <mstenta[m]> | Did you use the example docker compose file? |
| [07:44:41] | <shmida[m]> | <mstenta[m] "Did you use the example docker c"> yes |
| [07:44:56] | <mstenta[m]> | Development or production example? |
| [07:45:06] | <shmida[m]> | dev |
| [07:45:50] | <mstenta[m]> | Ok then the whole farmOS codebase is outside the container, including the sites directory, which contains your settings, files, and modules |
| [07:46:17] | <mstenta[m]> | So you should be all set :-) |
| [07:46:50] | <mstenta[m]> | You can just work with the files outside the container |
| [07:47:30] | <shmida[m]> | grate! thanks |
| [07:49:26] | <shmida[m]> | is it ok to work on a dev composer file with my real data? or i should open a new prod composer file and envirament? |
| [08:02:47] | <mstenta[m]> | The dev image also comes with xdebug, which might be a performance hog and security risk |
| [08:02:57] | <mstenta[m]> | But otherwise it's the same |
| [08:03:34] | <mstenta[m]> | The volumes are different only because the dev one assumes you want the whole codebase outside of the container, which is fine, and is easy to backup |
| [08:52:18] | * farmBOT has joined #farmos |
| [09:37:12] | * antoine[m] has quit (*.net *.split) |
| [09:37:12] | * wombat83[m] has quit (*.net *.split) |
| [09:37:12] | * mstenta[m] has quit (*.net *.split) |
| [09:37:13] | * dazinism has quit (*.net *.split) |
| [09:38:58] | * mstenta[m] has joined #farmos |
| [09:40:31] | * antoine[m] has joined #farmos |
| [09:41:23] | * wombat83[m] has joined #farmos |
| [09:41:39] | * dazinism has joined #farmos |