starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 08:46:00 +03:00

[GH-ISSUE #154] Document koel upgrade procedure #106

New issue

Closed

opened 2026-02-26 02:32:09 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 02:32:09 +03:00

Owner

Originally created by @TwizzyDizzy on GitHub (Dec 28, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/154

Hi @phanan,

thanks for koel so far - I like it a lot :) - in the near feature I will contribute some ideas as to what features might be interesting to implement for koel, but let's start with the basics before that:

I was wondering, what a generic update procedure might be if the initial install was something like:

git clone [koel-repo] [target]
cd [target]
git checkout tags/release-tag
npm install
composer install
php artisan init

In my imagination (partly tested) the upgrade might be something like:

cd [target]
git checkout master
git pull
git checkout tags/release-tag
npm update
composer update

The composer-update then, in turn, invokes artisan which is responsible for executing the scripts defined in composer.json:

php artisan clear-compiled
php artisan optimize
php artisan cache:clear

Please tell me, if the above running order is what needs to be done.

As for my current installation of koel: I'm running on Debian 8, PHP 5.6, MySQL 5.5.

Unfortunately, when running composer update I get the following errors:

$ php artisan clear-compiled
[Symfony\Component\Console\Exception\CommandNotFoundException]
Command "clear-compiled" is not defined.

$ php artisan cache:clear
[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "cache" namespace.

My goal is to have some bullet-proof update procedure - maybe even with some help on how one might do a rollback. This could then be used for the wiki.

Cheers so far
Thomas

Originally created by @TwizzyDizzy on GitHub (Dec 28, 2015). Original GitHub issue: https://github.com/koel/koel/issues/154 Hi @phanan, thanks for koel so far - I like it a lot :) - in the near feature I will contribute some ideas as to what features might be interesting to implement for koel, but let's start with the basics before that: I was wondering, what a generic update procedure might be if the initial install was something like: ``` git clone [koel-repo] [target] cd [target] git checkout tags/release-tag npm install composer install php artisan init ``` In my imagination (partly tested) the upgrade might be something like: ``` cd [target] git checkout master git pull git checkout tags/release-tag npm update composer update ``` The composer-update then, in turn, invokes artisan which is responsible for executing the scripts defined in composer.json: ``` php artisan clear-compiled php artisan optimize php artisan cache:clear ``` Please tell me, if the above running order is what needs to be done. As for my current installation of koel: I'm running on Debian 8, PHP 5.6, MySQL 5.5. Unfortunately, when running composer update I get the following errors: > $ php artisan clear-compiled > [Symfony\Component\Console\Exception\CommandNotFoundException] > Command "clear-compiled" is not defined. > > $ php artisan cache:clear > [Symfony\Component\Console\Exception\CommandNotFoundException] > There are no commands defined in the "cache" namespace. My goal is to have some bullet-proof update procedure - maybe even with some help on how one might do a rollback. This could then be used for the wiki. Cheers so far Thomas

kerem closed this issue

2026-02-26 02:32:09 +03:00

kerem commented

2026-02-26 02:32:09 +03:00

Author

Owner

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

Have you checked the upgrade guide under doc/upgrade? It should have these stuff covered.

@phanan commented on GitHub (Dec 29, 2015): Have you checked the upgrade guide under `doc/upgrade`? It should have these stuff covered.

kerem commented

2026-02-26 02:32:09 +03:00

Author

Owner

@TwizzyDizzy commented on GitHub (Dec 29, 2015):

Well... that's embarassing. Gonna check it out and close the issue above if everything went well.

Thanks & sorry
Thomas

@TwizzyDizzy commented on GitHub (Dec 29, 2015): Well... that's embarassing. Gonna check it out and close the issue above if everything went well. Thanks & sorry Thomas

kerem commented

2026-02-26 02:32:09 +03:00

Author

Owner

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

One rule of thumb is, never run composer update in your production env.
Just commit composer.lock from development env (which Koel already did),
and run composer install.

On Tue, Dec 29, 2015 at 9:14 AM, Thomas Dalichow notifications@github.com
wrote:

Well... that's embarassing. Gonna check it out and close the issue above
if everything went well.

Thanks & sorry
Thomas

—
Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/154#issuecomment-167689626.

@phanan commented on GitHub (Dec 29, 2015): One rule of thumb is, never run `composer update` in your production env. Just commit composer.lock from development env (which Koel already did), and run `composer install`. On Tue, Dec 29, 2015 at 9:14 AM, Thomas Dalichow notifications@github.com wrote: > Well... that's embarassing. Gonna check it out and close the issue above > if everything went well. > > Thanks & sorry > Thomas > > — > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/154#issuecomment-167689626.

kerem commented

2026-02-26 02:32:09 +03:00

Author

Owner

@TwizzyDizzy commented on GitHub (Dec 29, 2015):

Everything went well :). Sorry for the fuzz!

@TwizzyDizzy commented on GitHub (Dec 29, 2015): Everything went well :). Sorry for the fuzz!

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

No description provided.

Rows
Columns