You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set a save location for the download, if you want it elsewhere than the cache for extracting assets manually (--directory)
Only download files or database. (--only-files, --only-db)
Additionally, a progress bar should be added so you know how far along your download is. Especially since some of these snapshots can be many gigabytes in size, it can be beneficial for the user to see how far along the download is.
The text was updated successfully, but these errors were encountered:
I can see how these things would be useful but it would prevent WP Snapshots from completing a pull if you only had files or the db. At that point, it's really just storage which is solved by many other tools.
The thought is to add those options to the download command. It could solve some scenarios:
No longer have to go looking for files if they're in a directory user specifies (in practice, this could be a symlink or similar back to the cache in .wpsnapshots). Allows the possibility to stay more organized with project files in a single location, don't have to look up an ID matching a snapshot.
Make it easier to clean up old snapshots
Project is already set up and you only need a content/database update or files in the snapshot are out of date
These are probably more edge case scenarios but might still be helpful for completeness.
It occurs to me that download progress should probably be a separate issue from the flags.
Ideas for some additional options/flags:
Additionally, a progress bar should be added so you know how far along your download is. Especially since some of these snapshots can be many gigabytes in size, it can be beneficial for the user to see how far along the download is.
The text was updated successfully, but these errors were encountered: