There's now the option to power up more Compose Portals and we've made a recently introduced feature, Deleted Deployments, easier to work with - in this Compose Notes, we'll tell you all about them:
When we introduced the ability to see and recover your deleted deployments from backup, we added all your deleted deployments in a list underneath your existing deployments. We didn't realise how much of a distraction that could be so we've made a small change and hidden them by default. Now, if you look in your Compose console, at the bottom of your deployments list you'll find something like this:
This line tells you simply how many backups of previously deleted deployments are available to be restored. Clicking on the Show button will open up the list so it will appear like this:
Now you can select any deleted deployment backup and recover it. It makes bringing your deleted databases back from the dead easier and less distracting in day to day use.
We're working on something special when it comes to Compose access portals, and as part of making sure the foundations are solidly all in place, there's a little-big change happening in the Compose console - the ability to add more portals.
A quick refresher, for those who don't know - each Compose database deployment runs on its own private virtual encrypted network. The only way traffic gets in or out is through one of our access portals and there's generic portals for TCP connections and SSH tunnels and more specialized variants that know a bit more about the database they are working with, like the Mongo Router. There's a number of reasons for doing this, which we talk about in the recent article, Do you know why Compose proxies database connections.
The thing is, up until now, we've pretty much set in stone how many portals you can have, apart from the SSH tunnel. Well, that's what we're changing; you can now add as many portals as you think you may need. We're still enforcing minimum numbers of portals so you won't go below the number you need for high availability failover, but if you want an extra TCP portal or Mongo Router for your deployment then you can have one. Or two. Just so you know, each extra portal is $4.50 a month.
To get your extra portals, just visit the Security tab for your database in the Compose console.
Under each class of portal you'll see an Add button for that class - Add TCP Portal, Add SSH Portal, Add Mongo Router and so on. Click on the button and you get an extra portal. These extra portals will be identified in the Overview of the deployment's connection strings too. They are also identified in the portal list.
Each portal also now displays its short name, external DNS name which you can use in connection strings you create and the internal IP address for the portal on the private network so you can identify connections from that portal in the logs. If a portal isn't needed any more, then click the Remove button next to it in the list - only portals which aren't part of the required quorum of portals get the Remove button.
As we said, this is the foundation for some exciting new features. Currently, you can only have three of any portal class on a deployment, but that's one of the things we are working on. We'll let you know more about that, and the other things, when we are ready to unveil them, but rest assured they'll give you more control of your databases while letting you get on with developing your apps and running your business.
If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at firstname.lastname@example.org. We're happy to hear from you.