Upgrading your website to PHP 7.3 with Moss is quite a simple thing: Just choose the new version in the settings of your site(s). However, there are some things to consider before jumping into 7.3. Like with every release, some features come in and others go out. Let’s see how to safely upgrade your application without unpleasant surprises.
- 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.
- 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.
When you host multiple websites on a same server, your server needs a way to know the website it must return when an HTTP request arrives. The most widespread solution is to rely on the
Host: header the client (usually the web browser) includes in the request. When HTTPS is involved, the SNI extension (Server Name Indication) is used to determine the certificate that must be used to secure the connection. The web server will employ the given hostname to serve the appropriate website.
The former implies that the hostname must resolve to the IP address of your server. But what if you’re creating the website on your local development machine? What if you’re just testing a tool like Moss to see if it fits your needs? Most likely you don’t want to create new DNS records yet, so there must be a more convenient solution.
Meet wildcard DNS services for IP addresses. A domain name like
www.10.0.0.1.xip.moss.sh resolves to IP address
10.0.0.1. You don’t have to set up anything, just choose the appropriate domain name based on the IP address of your server. We encourage our users to use a wildcard DNS service while they’re trialing Moss, because it’s the fastest way to get started.
In the remainder of this article I’ll briefly review and compare the most relevant free wildcard DNS services you can use when you don’t want to mess with the DNS records of your own domain yet.
Last week we supported GitLab as a first-class citizen in Moss. If you host your application code in GitLab.com repositories, you can now enjoy all Moss features that previously were only available for GitHub and Bitbucket. As in the latter cases, you just have to authorize Moss to access your GitLab account and it’ll be able to deploy your GitLab-hosted repos.
In this way you can trigger automatic deployments after pushing your code, or deploy manually with just one click. In either case, your websites will benefit from a zero-downtime process. Want to know the details? Please keep reading 😀