LaunchPal
  • Introduction
  • Changelog
  • Welcome
    • Introduction
    • How to sign up
    • Get Support
    • Key Concepts
    • What's new
  • Getting Started
    • Whats a Project
    • Create your first Project
    • Uploading files and pages
    • Optimizing pages
    • Automatic SSL / HTTPS
    • Domains
      • DNS Only Mode
      • CNaming Domains
      • Virtual Domains
    • Change servers
    • Templates
    • Make backups
    • SSH Access
    • Restarting
    • Destroying
    • Bulk Project Creation
  • Billing
    • Pricing
    • My Account
    • FAQ
  • Applications
    • About Applications
    • Landing Page Server
    • Wordpress
    • FunnelFlux
    • Noipfraud
    • OpenVPN
    • Page Ripper
  • Hosts
    • About Hosts
    • Digital Ocean
    • Vultr
    • Linode
    • Sub accounts
  • Troubleshooting
    • Update wordpress / php on your project
    • DigitalOcean API Key Update
    • Dropbox
    • Project Errors
    • How to check & delete duplicate servers
    • Old AWS Accounts & EC2-Classic
    • How to install multiple apps on 1 project
    • Server root access
    • Guide for 3rd Party Support Teams
    • Reset your Wordpress password
    • Amazon Web Services
Powered by GitBook
On this page
  • When to use Change Server
  • Example
  1. Getting Started

Change servers

PreviousVirtual DomainsNextTemplates

Last updated 4 years ago

One of the great benefits of launchpal is that you can change your projects with a few clicks, without any downtime.

Now most hosting companies have this.

But LaunchPal is special.

Because you can move your entire project to a different host with a few clicks.

  • No changing DNS, we take care of that

  • No syncing files, we take care of that

  • No pausing traffic, because we switch the domain only when the new server is ready

  • So No click loss

When to use Change Server

Change Server function is similar to and , so it may be useful to understand when its best to use Change Server.

Change Server is best when you want to change your existing project so it:

  • has a new fresh IP

  • move it to a different geo location

  • scale the server up or down

It starts a new server, copies settings and files, moves domains and decommissions the old one.

When your looking to save a standard setup that you want to use for creating other projects - is best.

Example

Lets say I want to move & scale the server for an existing project.

This is my current project - a 512MB droplet in AMS2 using Drag & Drop to sync files:

Now lets say I need to move it to London, and its needs to be 1GB:

Click on the project name and then click on the Change server button in the top right corner.

First you select your host - in this case I will keep it on DigitalOcean

Next I select london as the location:

And lastly I increase the size to 1GB:

Then click NEXT which will start the process to change your server

It will create the new server and copy the files across.

Note that it will not switch over DNS until the new server is finished and working.

After 5 to 10 minutes it should be ready.

Like this one:

As you can see it is now 1GB, the IP has changed, and its in London.

The domains that I had assigned are now pointing to the new IP address and when I open the domain in my browser - the site is still there like it was in AMS2.

Like magic!

If you need to test a change that may cause issues, or roll back to a previous state - then is the tool for you.

Backups
Templates
using templates
Backup