Closed (won't fix)
Project:
Drupal CMS development repository
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
21 Mar 2026 at 01:51 UTC
Updated:
23 Mar 2026 at 17:59 UTC
Jump to comment: Most recent
Problem/Motivation
A 'missing link' in the Drupal CMS Desktop Launcher is the ability to export your site to be deployed elsewhere.
A one-click button to do just that is in the long term plans, but may not be prioritized for some time.
Issue fork drupal_cms-3580604
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
hestenetComment #3
hestenetComment #5
phenaproximaThanks for submitting these docs. But we can, and must, do better than this.
I think we should do something more like this:
Write a new
drush site:archivecommand, which creates a self-executing phar file. That phar file contains:You FTP this file to the server and SSH in. Then you run
php my-site.phar mysql://my:password@dbserver/drupalThis extracts everything into the current directory, runs
composer installto install all dependencies, and thendrush site:install --yes --existing-config --config-dir=./config --db-url=mysql://my:password@dbserver/drupalBehold: that restores the Drupal site. With one effing command.
I think that'd be a hell of a lot better.
Comment #6
hestenetTo paraphrase what I said in chat:
Well sure! You could *just* make the documentation unnecessary. Haha.
But if you want some runway in terms of time before doing that, we could use the docs as a temporary step. (Once they're up to snuff anyway).
Comment #8
pameeela commentedWe had somewhat of a plan for this already, @phenaproxima and I were able to get a site from the launcher onto Upsun hosting relatively easily. But we don't plan to provide the documentation for how to do this from end to end, because it should live with the providers to ensure it is up to date.
I've linked the relevant issue for producing a modified export (we just used the existing
site:exportcommand in our testing). I've also deleted most of the IS because much of this info was incorrect and it doesn't really serve anyone for it to be out there and discoverable.And @phenaproxima's mad science may continue along the lines he was already pursuing but that should be done in separate issues with defined scope.