Tag: ux

Changelog 2018-11-19

Changelog 2018-11-19

- - Changelog

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.
Changelog 2018-10-31

Changelog 2018-10-31

- - Changelog

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.
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.
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