Moss blog

Changelog 2018-08-14

Changelog 2018-08-14

- - Changelog

SITES

    • Deploy logs. The output of your deployment scripts is stored within folder logs/deploy/ of the corresponding site. In this way you can check what happened in your latest deployment at any moment.
Changelog 2018-07-19

Changelog 2018-07-19

- - Changelog

SITES

    • Alias support. If you want to serve different domains from the same application, now Moss gives you everything you need. E.g. you can create the website main.com (maybe a custom PHP app, a WordPress Multisite, or whatever) and make it also serve alias1.com and alias2.com.

UX

    • Server and website provisioning is faster now.
    • Moss checks the server OS is supported before it tries to provision it.
    • Bug fix: server names that start with a digit are allowed.
    • Many other minor improvements in the Moss’s web app.
Certificate Transparency for domain owners

Certificate Transparency for domain owners

- - Articles

Certificate Transparency (CT) provides a means to detect certificates that are mistakenly or maliciously issued by a Certification Authority (CA). As a domain owner, you should care about this for two different reasons: i) You can detect if an attacker is issuing certificates to impersonate your websites; and ii) browsers like Chrome and Safari mark your website as “insecure” if your certificate doesn’t comply with their CT policy.

Want to know the details? Please keep reading ?

Changelog 2018-06-29

Changelog 2018-06-29

- - Changelog

SITES

    • Custom shared paths per site. If you use Moss to deploy a website via git, now you can tell Moss the folders and files that must persist across deployments (e.g. user uploads, application logs, configuration files, etc). Before this feature, Moss knew what files to persist in Laravel and Symfony websites. Now you can customize such configs and also specify persistent paths for any kind of website (in a git repo) that you deploy with Moss.
Changelog 2018-06-20

Changelog 2018-06-20

- - Changelog

UX

  • When a website linked to a git repo hasn’t been deployed yet, you’ll see a more meaningful message now.
  • All relevant Type A DNS records for a website are shown now. This includes www and wildcard records if they apply.
  • Prevent some website configs that don’t make sense – e.g. don’t allow you to create a redirection for www.www.domain.com.
  • Don’t allow you to create a database user called root, since that would overwrite the permissions of the MySQL’s root user.

Don’t miss a post! Subscribe to the Moss Blog