Last Updated: November 2021
A production installation, sometimes called deployment, is an installation of Tethys Platform that is configured to for being hosted on a live server. This guide provides an explanation of the difference between Production and Development installations and provides several methods for installing Tethys Platform in production.
Here are the primary differences between the development installation you have been using to develop your apps and a production installation:
Production Grade Servers: The development server (
tethys manage start) is not efficient nor capable of handling the traffic a production website receives, so a combination of the NGINX and Daphne servers are used for production installations.
Database Engine: The default database engine used in development is SQLite. SQLite may not be a good fit for use in your production site (see Appropriate Uses For SQLite). Consider using an alternative database backend such as PostgreSQL.
Changes Are Not Automatically Loaded: When changes are made to a production installation, such as installing new apps or changing settings, the Daphne server must be restarted manually to load them. It does not restart automatically like the development server.
Debug Disabled: Debug mode is turned off to prevent sensitive information from being leaked through the detailed error messages produced by debug mode.
Secure Credentials: The internet is a hostile place, so secure passwords and unique usernames are used for all admin and database accounts, instead of the default usernames and passwords used for development.
Static Files Collected: The files in the
staticdirectories of apps are collected to one location to be served more efficiently by NGINX.
Workspaces Collected: The files in the app workspaces are collected to one location so they can be more easily backed up.
Permissions: NGINX must be given permission to access the static files and workspaces to be able to serve them.
There are several approaches to installing Tethys Platform in a production environment that are listed below. Read through the brief description of each approach below to learn about their pros and cons.
Manual installation means installing Tethys Platform from scratch and performing all of the production configuration steps manually. The process can be time consuming and tedious and it requires familiarity with Linux command line. The major advantage of performing a manual installation is that it gives you the most control over how Tethys Platform is installed and configured.
If you have not performed a manual installation before, we recommend going through the process using a virtual machine on your computer first before attempting to do the installation on the production server. Even if you don't plan to use the manual installation method, performing a manual installation on a local virtual machine can be very informative and increase your understanding with what is going on behind the scenes in the other methods.
This method involves creating a new virtual machine on a commercial cloud service using a virtual machine image that has Tethys Platform installed already and configured for production use. The advantage of this approach is that you can get a running Tethys Platform production installation up and running in only a few minutes. There are a few configuration steps that need to be performed after installation such as changing the default passwords, but other than that it is ready for installing your apps. They primary disadvantage is that the VM images are not produced for every version of Tethys Platform, so you will need to update Tethys to get the latest version.
We currently have images for the following commercial cloud providers:
This method involves using Docker to package and automate the deployment of a Tethys Portal with that has your apps pre-installed. The advantage of this approach is that the process of installing Tethys Platform and your apps is automated in the Docker image. The other major advantage is portability, the Docker image can be deployed to any Linux server with Docker installed. The disadvantage is that there is a learning curve to get started using Docker for the first time. However, the investment of learning Docker is very much worth your time as most modern web applications are deployed using Docker or a similar container technology.