Confluence 5.7 has reached end of life
Check out the [latest version] of the documentation
So, you want to try Confluence on an evaluation installation, then move to a production installation when you are ready? This page gives an overview of the steps to follow.
Assumptions:
If you are using Confluence Cloud to evaluate Confluence, please refer to the following guide when you want to move to an installed version: Migrating from Confluence Cloud to Confluence Server.
If you have already set up an evaluation Confluence site, you can skip this step.
Below is a summary of the installation and setup procedure, focusing on the choice of database.
To install Confluence:
To set up Confluence, including the database:
If you have finished evaluating Confluence, you can skip this step.
Depending on your choices during the Confluence setup, your evaluation site may include sample content. The example pages, blog posts and attachments are in the 'Demonstration space'. This space is present if:
You can update the sample content, and create more of your own. You can also invite people to join you on the site.
When you move to a production site, you can choose to copy the content and users to the new site.
To create content in your evaluation site:
To add users: Choose the cog icon then choose User Management.
For more tips about getting started, see Confluence 101.
If you have finished evaluating Confluence, you can skip this step.
Add-ons, also called plugins, provide additional features that you can install into your Confluence site. Some of them are provided free of charge. Many of the commercial add-ons are available free for an evaluation period.
You can browse and download add-ons on the Atlassian Marketplace. You can also find add-ons via the Confluence user interface, which interacts with the Atlassian Marketplace for you.
To find useful add-ons via the Confluence user interface:
When you are ready to move from an evaluation site to a production site, you need to migrate to a production-ready database. This involves installing a new Confluence site with a new database, and instructing Confluence to copy the data from your evaluation site to the new site. You will also need to check some important configuration settings, and define your backup strategy. The instructions below lead you through all the steps required.
Migrating your data to a production database:
Setting important configuration options on your production site:
Defining your backup strategy:
By default, Confluence will create daily XML backups of your content and user data. This is suitable when you are evaluating Confluence. When you move to a production site, you need more robust backup procedures and technologies. See Production Backup Strategy.