starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 16:56:02 +03:00

[GH-ISSUE #1283] Error due to front-end build in `koel:init` #734

New issue

Closed

opened 2026-02-26 02:34:07 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 02:34:07 +03:00

Owner

Originally created by @Hyzual on GitHub (Feb 21, 2021).
Original GitHub issue: https://github.com/koel/koel/issues/1283

Describe the bug
Hi, first of all I wanted to thank all contributors for v5.0.2 which is much easier to install now that ready-to-install zip file and tarball are built and delivered in the Release 😄. As maintainer of a docker image for Koel, it makes my life much easier.
There is however a minor annoyance left: when you run php artisan koel:init, it still tries to rebuild the front-end Javascript app and assets. I believe that now that there is a dedicated github Action to build and release those assets, this step appears to no longer be necessary in koel:init. When yarn is not installed on the system (it is the case in the Docker image I'm maintaining), running koel:init will produce the following error despite the fact that front-end assets are already present and installed.

The error:

Attempting to install or upgrade Koel.
Remember, you can always install/upgrade manually following the guide here:
📙  https://docs.koel.dev

App key exists -- skipping
Migrating database
Data seeded -- skipping
Now to front-end stuff
Oops! Koel installation or upgrade didn't finish successfully.
Please try again, or visit https://docs.koel.dev for manual installation.
😥 Sorry for this. You deserve better.

To reproduce
Using docker:

Download the following docker-compose file: https://github.com/Hyzual/docker-koel/blob/master/docker-compose.yml
Replace <koel_password> in the file by a password
Run docker-compose up -f docker-compose.yml -d (Assuming the downloaded file is named docker-compose.yml)
Replace koel_container_name in the following command by the container's name and run it: docker exec -it koel_container_name php artisan koel:init
The error will appear in your terminal

Without using docker:

Install koel on a new system without yarn installed
Run php artisan koel:init
The errror will appear in your terminal

Expected behavior
I would expect the "Now to front-end stuff" step to be omitted, since front-end assets are already built and optimized by Github Actions.

Screenshots
Not sure screenshots would help here, I can include some upon request.

Environment

Koel version v5.0.2
OS: Debian buster but I don't think that is relevant
Browser: Not applicable
PHP version v7.4.14
Node version: Not installed

Additional context
No additional context.
Thanks !

Originally created by @Hyzual on GitHub (Feb 21, 2021). Original GitHub issue: https://github.com/koel/koel/issues/1283 **Describe the bug** Hi, first of all I wanted to thank all contributors for v5.0.2 which is much easier to install now that ready-to-install zip file and tarball are built and delivered in the Release :smile:. As maintainer of a docker image for Koel, it makes my life much easier. There is however a minor annoyance left: when you run `php artisan koel:init`, it still tries to rebuild the front-end Javascript app and assets. I believe that now that there is a [dedicated github Action](https://github.com/koel/koel/actions/workflows/release.yml) to build and release those assets, this step appears to no longer be necessary in `koel:init`. When `yarn` is not installed on the system (it is the case in the Docker image I'm maintaining), running `koel:init` will produce the following error despite the fact that front-end assets are already present and installed. The error: ``` Attempting to install or upgrade Koel. Remember, you can always install/upgrade manually following the guide here: 📙 https://docs.koel.dev App key exists -- skipping Migrating database Data seeded -- skipping Now to front-end stuff Oops! Koel installation or upgrade didn't finish successfully. Please try again, or visit https://docs.koel.dev for manual installation. 😥 Sorry for this. You deserve better. ``` **To reproduce** Using docker: 1. Download the following docker-compose file: https://github.com/Hyzual/docker-koel/blob/master/docker-compose.yml 2. Replace `<koel_password>` in the file by a password 3. Run `docker-compose up -f docker-compose.yml -d` (Assuming the downloaded file is named `docker-compose.yml`) 4. Replace `koel_container_name` in the following command by the container's name and run it: `docker exec -it koel_container_name php artisan koel:init` 5. The error will appear in your terminal Without using docker: 1. Install koel on a new system without `yarn` installed 2. Run `php artisan koel:init` 3. The errror will appear in your terminal **Expected behavior** I would expect the "Now to front-end stuff" step to be omitted, since front-end assets are already built and optimized by Github Actions. **Screenshots** Not sure screenshots would help here, I can include some upon request. **Environment** - Koel version v5.0.2 - OS: Debian buster but I don't think that is relevant - Browser: Not applicable - PHP version v7.4.14 - Node version: Not installed **Additional context** No additional context. Thanks !

kerem closed this issue

2026-02-26 02:34:07 +03:00

kerem commented

2026-02-26 02:34:07 +03:00

Author

Owner

@Hyzual commented on GitHub (Feb 21, 2021):

While looking quickly in files I discover that there is a "no-assets" option which allows to skip that step. I did not know it existed, I'll try it.

Edit: it works well and does the job. I'll document the option for people using the docker image.

@Hyzual commented on GitHub (Feb 21, 2021): While looking quickly in files I discover that there is a ["no-assets" option](https://github.com/koel/koel/blob/5a611b9a0dc361bc92f518d841e50c6f45adabe8/app/Console/Commands/InitCommand.php#L257) which allows to skip that step. I did not know it existed, I'll try it. Edit: it works well and does the job. I'll document the option for people using the docker image.

kerem commented

2026-02-26 02:34:07 +03:00

Author

Owner

@phanan commented on GitHub (Mar 25, 2021):

You're right, that option is exactly for the case.

@phanan commented on GitHub (Mar 25, 2021): You're right, that option is exactly for the case.

kerem commented

2026-02-26 02:34:07 +03:00

Author

Owner

@phanan commented on GitHub (Mar 26, 2021):

Btw @Hyzual can you check your Twitter DM?

@phanan commented on GitHub (Mar 26, 2021): Btw @Hyzual can you check your Twitter DM?

kerem commented

2026-02-26 02:34:07 +03:00

Author

Owner

@Brancliff commented on GitHub (Mar 9, 2024):

Just a heads up, it seems that this is still the case, even after the switch from hyzual/koel to phanan/koel. --no-assets fixed it for me as well

@Brancliff commented on GitHub (Mar 9, 2024): Just a heads up, it seems that this is still the case, even after the switch from hyzual/koel to phanan/koel. --no-assets fixed it for me as well ![image](https://github.com/koel/koel/assets/22332774/061623af-6dc3-43ee-94a6-1fe871faeded)

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#734

No description provided.

Rows
Columns

[GH-ISSUE #1283] Error due to front-end build in koel:init #734

[GH-ISSUE #1283] Error due to front-end build in `koel:init` #734