[GH-ISSUE #1] .env not created in installation process. #2

Closed
opened 2026-02-26 02:31:45 +03:00 by kerem · 4 comments
Owner

Originally created by @juliusvdijk on GitHub (Dec 13, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/1

In the installation instructions there is an entry that you need to modify the .env file with the database info and account info.

However this file does not exist after cloning the git repo and running composer install.
Currently you need to manually copy the .env.example file to .env and edit the details.

Originally created by @juliusvdijk on GitHub (Dec 13, 2015). Original GitHub issue: https://github.com/koel/koel/issues/1 In the installation instructions there is an entry that you need to modify the .env file with the database info and account info. However this file does not exist after cloning the git repo and running composer install. Currently you need to manually copy the .env.example file to .env and edit the details.
kerem closed this issue 2026-02-26 02:31:45 +03:00
Author
Owner

@phanan commented on GitHub (Dec 13, 2015):

You're right. I'll update the instruction as such. Thanks!

<!-- gh-comment-id:164254731 --> @phanan commented on GitHub (Dec 13, 2015): You're right. I'll update the instruction as such. Thanks!
Author
Owner

@juliusvdijk commented on GitHub (Dec 13, 2015):

You could also add a composer script to copy the example to .env automatically.

<!-- gh-comment-id:164255075 --> @juliusvdijk commented on GitHub (Dec 13, 2015): You could also add a composer script to copy the example to .env automatically.
Author
Owner

@phanan commented on GitHub (Dec 13, 2015):

That's true, and as a matter of fact Laravel has it as a post-root-package-install script. I'd like to make it obvious here though.

<!-- gh-comment-id:164255196 --> @phanan commented on GitHub (Dec 13, 2015): That's true, and as a matter of fact Laravel has it as a `post-root-package-install` script. I'd like to make it obvious here though.
Author
Owner

@phanan commented on GitHub (Dec 13, 2015):

But given it a second thought, it sounds like a better idea to make it a script... I'll add it in a next commit 👍

<!-- gh-comment-id:164255255 --> @phanan commented on GitHub (Dec 13, 2015): But given it a second thought, it sounds like a better idea to make it a script... I'll add it in a next commit :+1:
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#2
No description provided.