@luceos can you explain in more details how the new functionality works and probably update the first post in this discussion? Currently the commands are in a post somewhere in this discussion and it's hard for me to find it among 2000+ posts (BTW, here's where load while scrolling for Flarum has its downsides, it's just too awkward and for some reasons while loading the browser skips some posts, so it's not even smooth).
In particular can you explain what the --map option does? My understanding is you should execute it only once after you upgrade to the new dev in order to map the existing files and posts (and the mapping will be stored in the database for future use), thus there will be no need for second execution of the --map, is that correct? If not, does that mean that I should always combine --map with --cleanup? If I execute only --cleanup with no --map, what will be the result? Are the files physically deleted from the corresponding storage, e.g. AWS? I remember there were some errors with aws-s3 vs aws_s3 in the DB or something like that and you said you're going to implement a proper migration. Is that ready now? Can I safely execute the cleanup logic on my prod forum or is that functionality still in beta?
Again, a better description of the algorithm and the commands would be very helpful since I am confused and still worried to use it. I haven't done so anyway, because of the DB discrepancies and the errors, as well as fear that the functionality is still in beta.
P.S. To add to the above, executing --cleanup without --map results in the following warning:
Are you sure you want to clean up without mapping first? (yes/no) [no]:
So, what's the difference, what will happen in the two scenarios, with and without mapping? Am I gonna lose posts/files?
P.P.S. So, I still get the In Manager.php line 85: No adapter configured for aws_s3. Is it safe to update my DB records? But I think this should have been a migration since I have been using only official releases of extensions. And besides, all my new uploads keep on using the aws_s3. What extension/code is inserting records in fof_upload_files table with upload_method set as aws_s3 and why is the extension expecting it to be aws-s3 instead? Not sure that's OK.
