Moss blog

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-10-17

Changelog 2018-10-17

- - Changelog

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.
Web hosting models for software development agencies

Web hosting models for software development agencies

- - Articles

In order to choose a web hosting solution for a project, what criteria do you take into account? Prefer managed or unmanaged services? Shared or dedicated environments? In this article I explore the alternatives from the viewpoint of a web development agency and argue why a website per cloud server is our preferred option as of this writing.

Changelog 2018-10-08

Changelog 2018-10-08

- - Changelog

This week we’ve been doing a major update. We’ve deployed new features, bug fixes, and upgrades to our infrastructure. Here you can find a summary of user-facing changes.

Users

    • Server user management. You can create and delete server users from Moss. For each user you can also manage the associated SSH public keys. This means that public keys are not bound to servers any more, but to server users.
    • Custom user per website. You can leverage the aforementioned users to isolate the websites hosted on a same server between each other. Choose the user as you create the website in Moss or change the user afterwards.

Workers

    • Worker logs are now within folder /home/<site-user>/sites/<site-name>/logs/workers/

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