The command "bin/rails s -p 3000 -b 0.0.0.0" is working fine but in the development environment even with the custom domain name.
While trying to run the rails in production with the command "bin/rails s -e production -p 3000 -b 0.0.0.0", everything fails even though the env variables are set to production in the .env file.
"WARNING: table: "settings_communities" does not exist or not database connection,
Settings::Community.community_name fallback to returns the default value.
WARNING: table: "settings_rate_limits" does not exist or not database connection,
Settings::RateLimit.user_considered_new_days fallback to returns the default value.
/home/ubuntu/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:19:in `exec': PG::UndefinedTable: ERROR: relation "tags" does not exist (ActiveRecord::StatementInvalid)
LINE 8: WHERE a.attrelid = '"tags"'::regclass
[Note: the settings_communities and other table names displayed in the error messages are there available in the database; and the db connectivity is good if I just run the command "bin/rails s -p 3000 -b 0.0.0.0".
Any guidance how to run the local installation to production?