php artisan migrate:refresh
solved the problem. But somebody let me know why this happened.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I pushed my project for the first time using Digital Ocean and Laravel Forge.
One thing that I notice is that in production, the users table columns are different than the one I created.It seems like the table is the default Laravel users table.
It all works fine with Laravel Homestead(Vagrant)/
Why is this happening?
Im expecting this to be my table but

What I have is
<?php
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
class CreateUsersTable extends Migration
{
/**
* Run the migrations.
*
* @return void
*/
public function up()
{
Schema::create('users', function (Blueprint $table) {
$table->increments('id');
$table->string('name')->unique();
$table->string('token')->nullable();
$table->boolean('verified')->default(false);
$table->string('email')->unique();
$table->string('password', 60);
$table->rememberToken();
$table->timestamps();
});
}
/**
* Reverse the migrations.
*
* @return void
*/
public function down()
{
Schema::drop('users');
}
}
Looks like the I have screen is the default migration. It may have run that migration before the changed migration was actually set.
Please or to participate in this conversation.