Overview
Yellowfin is available for deployment on servers and on all major cloud environments. A variety of installation options exist to suit each environment.
You have probably already decided which environment you wish to deploy on, so we’ll skip the descriptions of the different cloud platforms and server choices and provide more details about Yellowfin deployments on each of those platforms.
In this section of the wiki, we’ll cover best practice for deploying Yellowfin to many of these environments.
Yellowfin formats for different deployments
The following table describes each type of Yellowfin offering and the situations it’s best suited to, such as proof of concept (POC) or production.
Yellowfin format | Quick description | Best used for... |
|---|---|---|
Yellowfin Application Installer | A traditional installation file, with options to install on Linux, Windows and MacOS. | Long-term instances on servers or in the cloud in non-containerized environments. |
Yellowfin All-In-One image | Pre-built image of Yellowfin software with a PostgreSQL database included, ready for container deployment. | Short-term instances (POCs or demos). Use if you don’t need to customize the Yellowfin defaults (apart from memory, which is configurable).
|
Yellowfin All-In-One Docker file | A file to build your own image of Yellowfin software with a PostgreSQL database included, ready for container deployment.
| Short-term instances (POCs or demos). Use if you need to customize the Yellowfin defaults (apart from memory), or if you would like to customize any CSS, JavaScript, libraries or drivers. |
Yellowfin App-Only image | Pre-built image of Yellowfin software, ready for container deployment.
| Long-term instances in a container environment. Use if you don’t need to customize CSS, JavaScript, libraries or drivers, but would like to customize your Yellowfin defaults. |
Yellowfin App-Only Docker file | A file to build your own image of Yellowfin software, ready for container deployment. | Long-term instances in a container environment that enable configuration of a variety of default environment variables, CSS, JavaScript, libraries and drivers. |
Yellowfin mobile app | End-user app available for iPhone and Android. | End-users accessing Yellowfin content. |
Component comparison
If you’re still not sure which Yellowfin offering to choose for your deployment, the table below lists the components of each Yellowfin format.
| Yellowfin format | Database included? | Environment configuration options | Clustered environment? | Available environments |
|---|---|---|---|---|
Yellowfin Application installer | HSQL (not recommended for use beyond evaluation phase) | Variety of system options, CSS, JS, libraries, drivers | Yes | Containerized and non-containerized |
All-In-One image | PostgreSQL | System memory only | No | Containerized |
All-In-One Docker file | PostgreSQL | System memory (with the option to add CSS, JS, libraries and drivers) | No | Containerized |
App-Only image | None | Variety of system options only | Yes | Containerized |
App-Only Docker file | None | Variety of system options (with the option to add CSS, JS, libraries and drivers) | Yes | Containerized |