Existing Drupal project (online) should be fetched from remote to work on it locally (like drowl-init-from-existing) easily.
The Drupal Project typically consists of:
composer.json
config
content
files
settings.php (server-side configuration)
As config and content are both contained in the database and are up to date there, for a first step we should concentrate on the database instead of fetching configuration.
Steps after 9 are equal to drowl-init-from-existing so perhaps it might make sense to select the source in the first step of drowl-init-from-existing => From local files or From Remote?
Required information for fetching from remote:
SSH Login
Remote path to project
Database name (can be derived from remote settings.php)
Project URL
Steps to take (UX - pseudo):
Run drowl-init-from-existing-remote (difer)
Enter Remote Server Connection (user@host:[port])
Connect (using ssh key auth)
You are in directory XXX, enter the path to the project directory (absolute or relative)
/var/www/xz/123/abc/drupal
Check if composer.json is in directory and contains "name": "drupal/recommended-project" => Give success or error message
Read database name from settings.php => The used remote database name is "XXX", is this correct?
Fetch composer.json and database XXX from remote and import into project?
Do it... (proceed like in drowl-init-from-existing)
Further improvements (low prio):
Allow to update from remote (re-fetch composer.json, database or config)
Context:
Existing Drupal project (online) should be fetched from remote to work on it locally (like
drowl-init-from-existing
) easily.The Drupal Project typically consists of:
As config and content are both contained in the database and are up to date there, for a first step we should concentrate on the database instead of fetching configuration.
Steps after 9 are equal to
drowl-init-from-existing
so perhaps it might make sense to select the source in the first step ofdrowl-init-from-existing
=> From local files or From Remote?Required information for fetching from remote:
Steps to take (UX - pseudo):
drowl-init-from-existing-remote
(difer
)/var/www/xz/123/abc/drupal
Further improvements (low prio):
Out of scope