Tips for deploying for production
If you're planning to deploy an instance of the authoring tool for use in a production environment, there are a few things you should think about to avoid disaster.
Note: none of the below are specific to Adapt or the authoring tool, and should all be familiar features for your resident Node.js/MongoDB sysadmin.
We've put this first, as it should always be at the top of your list of considerations when handling any kind of data, and should not be taken lightly.
It's important to note that MongoDB in particular has practically no security enabled by default, so it would be very foolhardy to continue with an install before seeking the advice of an expert (if you don't believe us, read a couple of stories of extortion and ransomware).
Before you start investing money scaling vertically or horizontally, you'll want to make sure your initial set-up is fully optimised so you can squeeze as much performance out of your hardware as you can. The following are tips you should try before you consider improving your hardware.
Once you've got your instance up and running, you'll want to keep it that way. The following tips are related to system administration tasks such as: handling server crashes, error logging and more.
