Author: Moss

SITES

• • Fix: When Moss is monitoring a website and the corresponding domain name changes, Moss’s health-checks must be targeted at the new domain name.
  • Optimization: Don’t upload an SSH key onto a git provider (GitHub, GitLab, or Bitbucket) if such key already exists on the user’s account at the provider. This behavior existed before but a regression introduced this “bug”.

SITES

• • PHP 7.3 is fully supported. You can create new PHP 7.3 websites or upgrade your existing applications to PHP 7.3.

In addition to lots of internal improvements, today’s release includes the following user-facing enhancements.

UX

• • The admin of the Moss account can see (and delete) the pending invitations they sent to other developers.
  • The name of your Public SSH Keys must be unique from now on.

Sites

• • Full GitLab support. Native integration with GitLab – link your GitLab account and let Moss deploy your web applications easily. This enables push-to-deploy in all your GitLab repositories.

Servers

• • Default HTTPS site. Requests for websites that don’t exist on the server will be directed to a default (blank) page. This behavior was already implemented for HTTP, now it also applies when the website is requested over HTTPS. Existing users may force this configuration by provisioning an existing site or creating a new one on the server.

UX

• • Several minor bug fixes and improvements in the web application.

Servers

• • Override Postfix configs with user-provided files. If you need any custom Postfix configuration and don’t want Moss to override it, just put your configuration files under /home/moss/.override/postfix/ and Moss will use such configurations instead of its own’s.