by manual installation, I could cease the rails server to reload the config files. Is there something like the rails server within docker?
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.
This seems to work for me:
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.
why are you trying to do this, not following at all. Anyway here you go.
cd /var/discourse
./launcher enter app
sv restart unicorn
should we exit app after this step? I’m so new to this if it wasn’t obvious
/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?
UI에서 서버를 재시작할 수 있는 버튼이 있나요? 새 버전이 출시되면 업그레이드 버튼이 표시되는 것을 확인했는데, 이 버튼이 재시작을 수행하는 것 같긴 하지만, 재시작만을 위한 버튼은 찾지 못하겠습니다.
아니요, 없습니다. 왜 웹 서버를 재시작해야 합니까? 해결하려는 문제는 무엇인가요?
서버를 재시작해서 app.yml 변경 사항이 적용되는지 확인하고 싶었습니다. 재빌드도 필요한 것 같습니다. 관리자 페이지의 업그레이드 섹션 근처에 재빌드를 위한 UI 버튼을 추가하면 편리할 것 같습니다.
app.yml 파일에 대한 대부분의 변경 사항은 재빌드를 필요로 합니다. 재빌드는 UI에서 트리거할 수 없으며, docket 컨테이너 외부에서 서버 자체에 연결해야 합니다.
SMTP와 같은 설정은 yml 파일에서 업데이트할 수 있으며, 아래 명령을 통해 즉시 적용됩니다:
./launcher destroy app
./launcher start app
반면 플러그인 등 기타 항목은 재빌드가 필요합니다.
