98f37c2482
The installer now prompts for and validates a custom admin username and email, updating migrations and SQL placeholders accordingly. Login now accepts either username or email, and the login form and installer views have been updated to reflect these changes. Additional logging and migration handling improvements were made for better installation and authentication workflows.
Database Migrations
Fresh Installation (v1.1.0+)
For new installations, use the consolidated schema:
000_initial_schema_v1.1.0.sql- Complete database schema for v1.1.0
Install via: Web installer at /install
Incremental Migrations (v1.0.0 → v1.1.0)
If upgrading from v1.0.0, these incremental migrations will be applied:
001_create_tables.sql- Core tables (domains, groups, channels, logs)002_create_users_table.sql- Users table003_add_whois_fields.sql- WHOIS data fields004_create_tld_registry_table.sql- TLD registry005_update_tld_import_logs.sql- Import logs updates006_add_complete_workflow_import_type.sql- Workflow import type007_add_app_and_email_settings.sql- Application settings008_add_notes_to_domains.sql- Domain notes field009_add_authentication_features.sql- Authentication system010_add_app_version_setting.sql- Version setting
Upgrade via: Web updater at /install/update
Migration System
The installer automatically:
- Detects if this is a fresh install or upgrade
- Uses consolidated schema for fresh installs
- Uses incremental migrations for upgrades
- Tracks executed migrations in
migrationstable - Prevents re-running completed migrations