I have a similar issue, but with morbo: web server doesn't watch for
changes.
So I'd like to renew discussion about dockerizing mojolicious apps.
Below is my docker-compose.yml file
version: '2'
services:
web:
image: pavelsr/kayako-dashboard-dev
container_name: kayako-dashboard
volumes:
- ${PWD}:/root/www/
working_dir: /root/www
command: [ "morbo", "-v", "-w", "dashboard_server.conf",
"./script/dashboard_server" ]
ports:
- "3000:3000"
links:
- db
db:
image: mongo
container_name: kayako-dashboard-mongodb
ports:
- "27017:27017"
If I want to check results after updating the source code I need to do
docker-compose down && docker-compose up each time. It's a little bit
annoying.
Is there any solution ?
четверг, 29 января 2015 г., 17:10:37 UTC+3 пользователь Alexander Karelas
написал:
>
> As far as I know, docker containers require their processes to be
> foreground processes, so that a TERM signal is sent to them gracefully
> when docker is shutting down (because the host server itself might be
> shutting down).
>
> However if I run:
>
> hypnotoad -f app.pl
>
> ...then, when I try to do "hot deployment" (by running hypnotoad -f
> app.pl again), the new hypnotoad process is not a foreground one anymore.
>
> How do we solve this problem?
>
> Should I forget about "hot deployment" when working in Docker containers?
>
> Thanks,
>
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
