Release 6538: hypernode-oom-protect uses correct cwd, hypernode-ssl-config-generator handles multiple DNS names

  • Home / Changelog / Release 6538: hypernode-oom-protect uses correct cwd, hypernode-ssl-config-generator handles multiple DNS names
  •  in Changelog
  • , by Rick

In this release we have updated some of the tools in our Python bundle of system utilities.

hypernode-oom-protect will now report the correct current working directory

before:

app@1fos4q-dennisv-magweb-cmbl:~/magento2$ hypernode-oom-protect pwd
/data/web
app@1fos4q-dennisv-magweb-cmbl:~/magento2$ pwd
/data/web/magento2

after:

app@1fos4q-dennisv-magweb-cmbl:~/magento2$ hypernode-oom-protect pwd
/data/web/magento2
app@1fos4q-dennisv-magweb-cmbl:~/magento2$ pwd
/data/web/magento2

hypernode-ssl-config-generator can now handle multiple DNS names in the dehydrated domains.txt

Example:

#example.hypernode.io
erikhyperdev.hypernode.io
www.erikhyperdev.nl www2.erikhyperdev.nl

Resulting NGINX config before:

grep server_name www.erikhyperdev.nl.conf 
        server_name www.erikhyperdev.nl;

Resulting NGINX config after:

grep server_name www.erikhyperdev.nl.conf 
        server_name www.erikhyperdev.nl www2.erikhyperdev.nl;

Changes will be deployed over the course of this week.