You can always head to the list of sites in a workspace by clicking the 'Sites' button.

From Moss you can manage each of your sites.

  • Check the DNS record needed for your site to be reachable.
  • Add or remove additional domain names (aliases).
  • In case your site is bound to a git repo, you may manage your deployments. This includes triggering a deployment after git push and setting up zero-downtime deployments.
  • If your plan allows it, you can check the health of your website.
  • If your site employs a framework that Moss supports natively, you can manage your environment file.
  • For back-end applications, you may manage worker processes that run in the background.
  • You may also schedule cron jobs that run at specific times.
  • You can manage the certificate of your website, e.g. you may tell Moss to issue and renew free Let's Encrypt certs automatically.
  • If your site uses a database, you may manage it here.
  • You can fine-tune other configuration options.

There are also different actions you may perform on your site:

  • Deploy your site. This option is only available if your website is linked to a git repo.
  • Unbind your site. This tells Moss to stop managing your site. It won't be removed from your server, but Moss won't be aware of it any more.
  • Delete your site. This tells Moss to remove your site from the corresponding server.
  • Provision your site. This tells Moss to set up your site, just like he did the first time you created the site with Moss. This action makes web servers (Nginx, Apache) reload their configuration, so this is something you may need to do if Nginx and/or Apache configs have changed.

What's next?

By now you should have an idea of the things you can do with Moss. If you haven't done it yet, it's time to get started with Moss by adding a server.

Did this answer your question?