Yeah, changing the wp-config comes AFTER we copy over. And the 1? Is what you’re supposed to have That’s the new server on DreamPress.
And the domain being wrong (that is, with the folder) makes sense since that too is done via a WP command. BUT…
admin.php is NOT a normal WP file. You (or someone) edited the index.php because you were using WP in a subfolder. DreamPress runs everything out of root. I swapped the index.php file with the index.php_Standard one, turned off your caching plugin, changed the DB BACK to the -1 (which is correct for DreamPress, I know it’s weird), and now your site is loading. Of course, all your URLs are sans /blog/ so … this may not be what you expected.
I went back to your old server (mangano) and looked at your setup there. Strictly speaking, DreamPress is for WordPress only. Right now we’re not going to stop you if you copy over the old files. And if you wanted to move the WP instance back into a blog folder nor would we stop you from doing all those fancy things again. But it takes you outside the ‘norm’ of a WordPress setup, and puts a hell of a load on TS because now if you ever have any issues, we have to learn what you did to make WP special (a custom index.php etc) before we can fix it.
If you’re okay with JUST WordPress, then I think the only thing missing is your images folder, which I don’t see on DreamPress (which makes sense - we copy over your wp-content folder, the .htaccess, and wp-config.php, not the rest, and WP is a fresh install).