nickbe
commented
8 years ago Some additionaly thoughts on this. The installer should be simply browser based with only a bare minimum number of choices:
- Let the user choose between a default database or a domain name based database. Then create the database file names completely internally and automatically.
Everything else including the first admins mail adress 'admin@tinyissue' and password could be generated automatically and changed later.
I thought these options COULD be shown when installing the system but they could as well be configured later.
- Let the user choose a title for the system (default: 'TINY ISSUE'). Later show this title in the title bar instead of the current 'TINY ISSUE' label.
- Let the user enter the first admins mail adress and set the default password to 'password' automatically. He can change everything else later.
I'd like to suggest a slightly different approach to the current installation/database.
Could we make it possible to automatically let the user confirm the creation a new database, or select the 'root' database on the first start when a new base URL is detected?
When called from bugsystem.com, tinyissue should simply create and point to the root database Let's assume the default database filename is default.issues.
But when called from a subdomain like mybugs.bugsystem.com, tinyissue would ask to choose either between creation of mybugs.issues or selecting the default database default.issues - if I'd just want to reach my default bugsystem via a different subdomain.
Also I think creation of a default admin user and password is better than the whole commandline installation process. Being able to simply upload and run tinyissue with only a tiny ;) installation page would be more fitting.