Credentials not being displayed during the initial composer create-project on Windows OS
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.5k
- Forks
- 246
- Avg merge
- 19h 2m
- Merged PRs (30d)
- 7
Description
When running composer create-project wintercms/winter:dev-develop . on a Windows OS platform, all the interactive installation of tasks are run with their default values.
> @php artisan winter:install
.========================================================================.
db d8b db d888888b d8b db d888888b d88888b d8888b. ...
88 I8I 88 `88' 888o 88 `~~88~~' 88' 88 `8D ... ..... ...
88 I8I 88 88 88V8o 88 88 88ooooo 88oobY' .. ... ..
Y8 I8I 88 88 88 V8o88 88 88~~~~~ 88`8b .. ... ..
`8b d8'8b d8' .88. 88 V888 88 88. 88 `88. ... ..... ...
`8b8' `8d8' Y888888P VP V8P YP Y88888P 88 YD ...
`============================= INSTALLATION =============================
Database type [SQLite]:
[0] MySQL
[1] Postgres
[2] SQLite
[3] SQL Server
> Enter a new value, or press ENTER for the default
Application key [yzmncwviyS3Hz2R1ZgZQqjqvoAllJdhB] set successfully.
Migrating application and plugins...
INFO Migration table created.
The user is then not informed about the admin credentials created.
Possible workarounds:
- when creating a new Winter project on Windows, is to use WSL to get back interactives installation's tasks.
or - after installation is complete, run
php artisan winter:down --force && php artisan migrateand then get
...
INFO Migration complete.
INFO \Backend\Database\Seeds\DatabaseSeeder reported the following:
- The following password has been automatically generated for the "admin" account: ywh3enVGoVHbIOjyEyjlR7
What would be nice, is having the credentials for logging into the site administration in the installation summary.
Ex:
INFO WinterCMS installation completed.
- Application key [Mxi0QxErbH3ojNS6oaCQWa7QAqdiDS3x] set successfully.
- Backend access: [http://localhost/backend]
- Backend credentials: [admin/vTiX0p4NuCYjd8d9yr0tu6]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the reported composer create-project wintercms/winter:dev-develop . flow and follow the @php artisan winter:install entry point, especially on Windows. Identify where the installation summary is produced and ensure it reports the generated admin credentials and backend URL; verify the completed output matches the requested summary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100