Providing an auto-updating functionality for your self-hosted Laravel application.

2.1.2 2019-04-05 21:23 UTC


Latest Stable Version Total Downloads Build Status StyleCI Codacy Badge codecov composer.lock

This package provides some basic methods to implement a self updating functionality for your Laravel 5 application. Already bundled are some methods to provide a self-update mechanism via Github.

Usually you need this when distributing a self-hosted Laravel application that needs some updating mechanism, as you do not want to bother your lovely users with Git and/or Composer commands ;-)

Install with Composer

To install the latest version from the master using Composer:

$ composer require codedge/laravel-selfupdater

This adds the codedge/laravel-selfupdater package to your composer.json and downloads the project.

Register the package

Since Laravel 5.5 auto-discovery can be used to register packages - this is supported by this package. So if you run Laravel >=5.5 the steps [1] and [2] are not needed.

You need to include the service provider in your config/app.php [1] and optionally the facade [2]:

// config/app.php

return [

    'providers' => [
        // ...
        Codedge\Updater\UpdaterServiceProvider::class, // [1]
    // ...
    'aliases' => [
        // ...
        'Updater' => Codedge\Updater\UpdaterFacade::class, // [2]


Additionally add the listener to your app/Providers/EventServiceProvider.php [3]:

// app/Providers/EventServiceProvider.php

 * The event handler mappings for the application.
 * @var array
protected $listen = [
    // ...
    \Codedge\Updater\Events\UpdateAvailable::class => [
    ], // [3]
    \Codedge\Updater\Events\UpdateSucceeded::class => [
    ], // [3]



After installing the package you need to publish the configuration file via

$ php artisan vendor:publish --provider="Codedge\Updater\UpdaterServiceProvider"

Note: Please enter correct value for vendor and repository name in your config/self-updater.php if you want to use Github as source for your updates.

Running artisan commands

Artisan commands can be run before or after the update process and can be configured in config/self-updater.php:


'artisan_commands' => [
    'pre_update' => [
        'updater:prepare' => [
            'class' => \App\Console\Commands\PreUpdateTasks::class,
            'params' => []
    'post_update' => [
        'postupdate:cleanup' => [
            'class' => \App\Console\Commands\PostUpdateCleanup::class,
            'params' => [
                'log' => 1,
                'reset' => false,
                // etc.

Notifications via email

You need to specify a recipient email address and a recipient name to receive update available notifications. You can specify these values by adding SELF_UPDATER_MAILTO_NAME and SELF_UPDATER_MAILTO_ADDRESS to your .env file.

Config name Description
SELF_UPDATER_MAILTO_NAME Name of email recipient
SELF_UPDATER_MAILTO_ADDRESS Address of email recipient


To start an update process, i. e. in a controller, just use:

public function update()
    // This downloads and install the latest version of your repo
    // Just download the source and do the actual update elsewhere
    // Check if a new version is available and pass current version

Of course you can inject the updater via method injection:

public function update(UpdaterManager $updater)

    $updater->update(); // Same as above
    // .. and shorthand for this:
    $updater->fetch() // Same as above...

Note: Currently the fetching of the source is a synchronous process. It is not run in background.

Using Github

The package comes with a Github source repository type to fetch releases from Github - basically use Github to pull the latest version of your software.

Just make sure you set the proper repository in your config/self-updater.php file.

Using Http archives

The package comes with an Http source repository type to fetch releases from an HTTP directory listing containing zip archives.

To run with HTTP archives, use following settings in your .env file:

Config name Value / Description
SELF_UPDATER_REPO_URL Archive URL, e.g. http://archive.webapp/
SELF_UPDATER_PKG_FILENAME_FORMAT Zip package filename format
SELF_UPDATER_DOWNLOAD_PATH Download path on the webapp host server

The archive URL should contain nothing more than a simple directory listing with corresponding zip-Archives.

SELF_UPDATER_PKG_FILENAME_FORMAT contains the filename format for all webapp update packages. I.e. when the update packages listed on the archive URL contain names like,, ... then the format should be webapp-v_VERSION_. The _VERSION_ part is used as semantic versionioning variable for MAJOR.MINOR.PATCH versioning. The zip-extension is automatically added.

The target archive files must be zip archives and should contain all files on root level, not within an additional folder named like the archive itself.

Extending and adding new source repository types

You want to pull your new versions from elsewhere? Feel free to create your own source repository type somewhere but keep in mind for the new source repository type:

  • It needs to extend AbstractRepositoryType
  • It needs to implement SourceRepositoryTypeContract

So the perfect class head looks like

class BitbucketRepositoryType extends AbstractRepositoryType implements SourceRepositoryTypeContract

Afterwards you may create your own service provider, i. e. BitbucketUpdaterServiceProvider, with your boot method like so:

public function boot()
    Updater::extend('bitbucket', function($app) {
        return Updater::sourceRepository(new BitbucketRepositoryType);

Now you call your own update source with:

public function update(UpdaterManager $updater)


Please see the contributing guide.


Just a quickly sketched roadmap what still needs to be implemented.


The MIT License (MIT). Please see Licence file for more information.