mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #1310] Koel cannot connect to the database. #758
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#758
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yuis-ice on GitHub (Apr 24, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1310
After I followed the guide https://docs.koel.dev/#client , downloaded and unzipped the latest zip, did
composer install, and triedphp artisan koel:init --no-assetsbut I don't quite understand this part. I'd like to tell the Koel to create a new sqlite database and get started with the sqlite file, since I prefer sqlite for its simple accessibility, so I told the prompt "sqlite-e2e" and proceeded but the next prompt asked me "Absolute path to the DB file:", and I typed like "whatevertmp.db" and it failed, apparently the prompt need an existing database file ...? kindly tell me if I missed a concept of Koel. what can I do now?Environment
@ghost commented on GitHub (Apr 26, 2021):
I have seen your issue.
That way to solve this problem probably after next.
First, DB Connection making with you can be achieve by CLI "php artisan migrate".
Before CLI you should change DB name and DB propoties in .env of your project for the same of course.( in .env :
DB_DATABASE=your schema name
DB_USERNAME=your DB name
DB_PASSWORD=your DB password)
And next you can create new folder in your mind in your project folder , and cory your new folder Absolute path and
paste to your CLI.
So , all right.
Thank you.
@phanan commented on GitHub (Apr 26, 2021):
@kiryanovoselov Thanks, but that's incorrect. What @yuis-ice needs to do would be to create the database beforehand and supply the absolute path during installation. The installation process would then save this info into
.env, not the other way around.