How I could restart the web server in docker

Support Self-hosting

AI-generated summary

The discussion revolves around restarting the web server in Docker. berniegao initially asked if there’s a way to restart the web server similar to reloading config files in a manual Rails server installation. watchmanmonitor suggested using ./launcher stop app and ./launcher start app, but berniegao clarified that this method restarts the entire Docker container.

sam then provided the correct method: ./launcher enter app followed by sv restart unicorn. Jared_Smith1 asked if exiting the app is necessary after this step.

The conversation also touched on troubleshooting issues, such as SpaceMonkey encountering an error when trying to run ./launcher enter app, which Stephen helped resolve.

Additionally, trusktr asked if there’s a UI button to restart the server, and jomaxro explained that there isn’t one. trusktr suggested that a UI button for rebuilding would be convenient.

jomaxro clarified that most changes to the app.yml require a rebuild, which cannot be triggered from the UI. Stephen added that some settings, such as SMTP, can be updated and picked up immediately by running ./launcher destroy app and ./launcher start app, while others require a rebuild.

1

by manual installation, I could cease the rails server to reload the config files. Is there something like the rails server within docker?

@sam

2

This seems to work for me:

3

doing so will restart the entire docker container. what I trying to do is to restart the web server without touch the container, such as using “rails server” and then stop it without utilizing docker.

4

why are you trying to do this, not following at all. Anyway here you go.

cd /var/discourse 
./launcher enter app
sv restart unicorn
5

should we exit app after this step? I’m so new to this if it wasn’t obvious

6

I have discourse installed via docker. After upgrading yesterday my discourse has been down. I am trying to run ./launcher enter app
from
/var/www/discourse/
I am getting the error ./launcher: No such file or directory Is there way for me to search the correct directory for this command?

image
image738×187 2.63 KB

7

/var/www/discourse doesn’t exist outside the app, if you can see that path you’re already inside discourse.

Type exit - does that end the ssh connection, or bring you back to /var/discourse?

8

¿Hay un botón para reiniciar el servidor desde la interfaz de usuario? Veo un botón para actualizar cuando sale una nueva versión, lo cual creo que incluye un reinicio, pero no veo un botón solo para reiniciar.

9

No, no lo hay. ¿Por qué necesitas reiniciar el servidor web? ¿Qué problema estás intentando resolver?

10

Quería reiniciar el servidor para ver si los cambios en app.yml surtían efecto. Supongo que también es necesario volver a compilarlo. Quizás sería conveniente añadir un botón en la interfaz de usuario (cerca de la sección de actualización del panel de administración) para eso.

11

La mayoría de los cambios en app.yml requieren una reconstrucción. Las reconstrucciones no se pueden activar desde la interfaz de usuario; necesitas conectarte al servidor en sí, fuera del contenedor de docket.

12

Configuraciones como SMTP se pueden actualizar en el archivo yml y se detectarán inmediatamente mediante:

./launcher destroy app
./launcher start app

Mientras que otros elementos, incluidos los complementos, requerirán una reconstrucción.