rattail-fabric2/rattail_fabric2/deploy/luigi/restart-overnight.sh.mako

#!/bin/sh -e

cd ${envroot}

RATTAIL="bin/rattail --config=app/cron.conf"

$RATTAIL overnight -k ${automation.lower()} <%text>\</%text>
        --no-versioning <%text>\</%text>
        % if email_key is not Undefined and email_key:
        --email-key '${email_key}' <%text>\</%text>
        % endif
        --email-if-empty <%text>\</%text>
        --no-wait
Add generic Luigi install logic at least try to do what we can to reduce boilerplate 2022-01-28 15:29:32 -06:00			`#!/bin/sh -e`

Make each overnight script optional trying to phase out at least 1, maybe 2 of them... this also cleans up the 'restart' script to use 'rattail overnight' per recent changes. this seems the most useful to have around, in case of web app failure 2022-11-20 20:02:48 -06:00			`cd ${envroot}`
Add generic Luigi install logic at least try to do what we can to reduce boilerplate 2022-01-28 15:29:32 -06:00
Make each overnight script optional trying to phase out at least 1, maybe 2 of them... this also cleans up the 'restart' script to use 'rattail overnight' per recent changes. this seems the most useful to have around, in case of web app failure 2022-11-20 20:02:48 -06:00			`RATTAIL="bin/rattail --config=app/cron.conf"`

Must pass `-k` flag to `rattail overnight` command 2022-11-21 15:39:49 -06:00			`$RATTAIL overnight -k ${automation.lower()} <%text>\</%text>`
Make each overnight script optional trying to phase out at least 1, maybe 2 of them... this also cleans up the 'restart' script to use 'rattail overnight' per recent changes. this seems the most useful to have around, in case of web app failure 2022-11-20 20:02:48 -06:00			`--no-versioning <%text>\</%text>`
			`% if email_key is not Undefined and email_key:`
			`--email-key '${email_key}' <%text>\</%text>`
			`% endif`
			`--email-if-empty <%text>\</%text>`
			`--no-wait`