backdrop-contrib / d2b_migrate

GNU General Public License v2.0
5 stars 6 forks source link

Streamline existing workflow steps #21

Closed quicksketch closed 6 months ago

quicksketch commented 8 months ago

As an alternative to https://github.com/backdrop-contrib/d2b_migrate/issues/16, which would require moving the import to the first step, we might want to keep the current workflow step order, but streamline the existing steps.

Here are the current steps:

  1. Start
  2. Source database
  3. Database analysis
  4. Database backup
  5. Backup files
  6. Migrate database

The idea here is that we keep using a set of database credentials. Steps 1 - 3 stays the same.

Step 4 we would change to not require the user to download the database backup file, instead we would directly save it to disk.

Step 5 stays the same (or is out of scope for this issue).

Step 6 we remove the option to upload a file and the option to select a specific backup. Instead we always use the backup created in step 4.

This would eliminate two of the more confusing steps. As a first-time user I was really thrown off where the database backup should be saved in step 3.

docwilmot commented 8 months ago

Pushed some changes to help navigation.

irinaz commented 8 months ago

I would love to see an option to upload db in addition to connecting to the host.

new source screen.

@docwilmot , thank you so much for adding configuration that shows that db is already connected, now we can see what is status for db connection in both states

d2b-database connected

It looks like db connection times out after 8(?)hours, but at the same time we have already copy of source db in manual downloads directory we might reuse this db if we can resolve #16

docwilmot commented 6 months ago

This is as streamlined as we can get I think. Closing.