Database migrations seem to point to a nonexistant class about vaos

[BossOfGames]

What version is this? 1.0.3a? 2.0.0b2 is being released today, which resolves this. New schema.

[lilopkins]

I was lazy and just git clone'd the repository... (master branch, latest)

Also, from the laravel.log file:

[2018-08-22 16:37:43] local.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Class '104Update' not found in /home/va/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:410

not sure if that helps at all!

[lilopkins]

I can confirm having git checkout 2.0dp1 that it works as expected.

[BossOfGames]

Just a heads up since it's going to be relevant. You will need to drop your entire db between dp1 and b2. There's a few schema fixes I back edited in the migration files.