MailScheduler
WebsiteAll products
  • Prologue
    • MailScheduler
    • Release Notes
    • Changelogs
    • Architecture
  • Installation guide
    • Requirements
      • Windows
      • Linux
    • Getting started
      • Windows
      • Linux
    • Installation wizard
      • License
      • Repository database
        • SQL Server
        • MySQL
        • PostgreSQL
        • SQLite
      • Create a user
      • Email setup
      • URL & SSL Certificate
      • Run as a service
      • Summary
        • Running on Linux
    • Configuration panel
      • Home page
      • Domain & SSL Management
      • Repository Database
      • License Management
      • User Management
      • Email settings
    • Upgrade
      • Upgrade from 1.x to 2
      • Upgrade from 2.x
    • Update license
    • Moving to production
  • Product Guide
    • Getting started
    • Schedules
    • Tasks
    • Mailinglists
    • Recipients
    • Filtering
    • Monitoring
    • Config
    • API
  • Support
    • Troubleshoot
    • FAQ
Powered by GitBook
On this page

Was this helpful?

  1. Installation guide

Moving to production

When reaching the end of the testing phase there could be a desire to copy the whole setup from your test environment to the production environment. When doing this there are a few things to keep in mind.

Copy of the repository database

The repository database is the heart of MailScheduler and contains all the setup you did in the management console.

  • The repository database on your test environment needs to be cloned manually.

  • You need to do a fresh installation on the new production server.

    • Connect to the cloned database on step 3 of the installation to use that as the repository database

PreviousUpdate licenseNextGetting started

Last updated 11 months ago

Was this helpful?