Dear sir;
I meet a problem when systemd start hypnotoad, detail follow:
systemctl status mojo_test.service
● mojo_test.service - My Mojolicious application
Loaded: loaded (/usr/lib/systemd/system/mojo_test.service; enabled;
vendor preset: disabled)
Active: failed (Result: exit-code) si
Am Mittwoch, 22. November 2017 17:27:51 UTC+1 schrieb Dan Book:
>
> When the auto_escape option is set on Mojo::Template, it reverses this
> behavior; auto_escape is set by default for the EPRenderer template
> handler, which the rendering guide is referring to. I agree it is a bit
> confusing b
Mojo::Template is used for many things, most do not generate HTML.
https://github.com/kraih/mojo/blob/master/lib/Mojolicious/Command.pm#L40
--
sebastian
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop
Hi all,
I was wondering about unleashing the following tutorial on the LPW this
weekend to get feedback. I have lost all objectivity on it, so I appeal
to the regulars to point out the most problematic areas.
https://github.com/duffee/Mojolicious_session_example
All comments welcome, from Great
Hi David,
I'm no expert with systemd, but this is my mojo.service file which runs the
application in /usr/local/manager-application and works for me. My
differences are in the Service tag.
mojo.service
[Unit]
Description=My Mojolicious application
Requires=network.target
After=network.target
>
> I was wondering about unleashing the following tutorial on the LPW this
> weekend to get feedback. I have lost all objectivity on it, so I appeal
> to the regulars to point out the most problematic areas.
>
> https://github.com/duffee/Mojolicious_session_example
>
> All comments welcome,
There is probably more relevant information higher in the log; the status
command is only showing you the end of the log. Try running: journalctl -u
mojo_test.service
-Dan
On Thu, Nov 23, 2017 at 4:24 AM, wrote:
> Dear sir;
> I meet a problem when systemd start hypnotoad, detail follow:
>
I would not recommend running hypnotoad as a Type=simple service with -f.
This will not allow you to use hot-restarts via systemctl reload.
-Dan
On Thu, Nov 23, 2017 at 10:13 AM, wrote:
> Hi David,
>
> I'm no expert with systemd, but this is my mojo.service file which runs
> the application in
On 23/11/17 16:14, Dan Book wrote:
> I would not recommend running hypnotoad as a Type=simple service with -f.
> This will not allow you to use hot-restarts via systemctl reload.
Naively, I _can_ hot-restart with systemctl reload servicename, but now
you've got me worried.
Any idea why it's not ad
Hi,
Type=forking should work just fine, I am not sure that with Type=simple you
will have all the functionallity you can get from systemd.
A couple of advices though:
1) to get more confortable with systemd, you probably want to replicate as
much as possible the example in Mojolicious::Guides:
The best practice IMO in regards to permissions for the run and log
directories is to make subdirectories of /var/run and /var/log owned by the
user that will be running hypnotoad, and put the pidfile/logfiles in there.
The other issue though is if you are running hypnotoad to listen on a
privileg
The way that hot-restart works is that the USR2 signal is sent to the
currently running manager, which itself will spawn a new manager and then
wait for it to be ready, then exit. I don't think that Type=simple will
correctly track the new process when this happens since the new process was
not spa
12 matches
Mail list logo
