Hi Linda, What tag of the Evergreen container are you using? I believe that the instructions under "Restarting Evergreen services" are only applicable to the "dev" tag (i.e. if you ran `docker run [...] mobiusoffice/evergreen-ils:dev`). If you don't specify a tag, it defaults to the "latest" tag, which doesn't contain the file-based restart/recompile methods.
I typically use the non-dev tags, using the following steps to restart apache. Theoretically, they should work if you are using the dev tag too, but I haven't tried them: 1. docker ps # this will show the name of the running container 2. docker exec -it [container_name] bash # this will provide a shell within the running container. For example, if step 1 had mentioned that the running Evergreen container is named "peaceful_spence", it would be `docker exec -it peaceful_spence bash` 3. apache2ctl restart # simply restarts apache. When I need to restart all services, I use `ansible-playbook /egconfigs/evergreen_restart_services.yml -e hosts="127.0.0.1"` instead. Hope this helps, -Jane El vie, 11 ago 2023 a la(s) 04:28, Linda Jansová via Evergreen-general ( [email protected]) escribió: > Dear all, > > We have just started experimenting with a Docker container ( > https://hub.docker.com/r/mobiusoffice/evergreen-ils), mainly to see > whether it could help us identify what causes i18n issues reported in a > separate thread (with a subject "Evergreen 3.11.0a not properly switching > into Czech in the staff client"). > > At this point we are a bit stuck as we would like to make appropriate i18n > changes to the eg_vhost.conf file and then make them visible both in the > OPAC and in the staff client. > > We have uncommented lines related to French translation (just to see if it > works before we would make a deep dive into Czech) and restarted Evergreen > as described at https://hub.docker.com/r/mobiusoffice/evergreen-ils > (under the heading "Restarting Evergreen services") but it doesn’t seem to > change anything in the OPAC. > > How exactly should we proceed? > > (Maybe a more specific piece of documentation that would answer our > question is available somewhere; in that case, sharing a URL would be great > :-).) > > Thank you in advance! > > Linda > > _______________________________________________ > Evergreen-general mailing list > [email protected] > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general >
_______________________________________________ Evergreen-general mailing list [email protected] http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
