The goal for this is to give a simplified way to get the git hash from your code. This hash can be showed in the admin interface, added to your logs, and used for everything you can imaging.

The basic installation is adding this project with composer: composer require tjvb/laravel-githash.

If you disable the package discovery you need to add TJVB\LaravelGitHash\GitHashServiceProvider::class, to the providers array in config/app.php

The package provides a way to add the githash to add the hash and the short hash to the logs. This is enabled by default.

This package adds a default blade component that you can use with <x-githash></x-githash> to show the short and githash on your (admin) pages. This has the option add a version statement short or long to only show on of the versions. <x-githash version="short"></x-githash>

If the Laravel about command is available it will add information about the hash and the cache status. This can be disabled in the config.

There ar a lot of options to add the hash to other parts in your application. This can be done with injecting the \TJVB\LaravelGitHash\Contracts\GitHashLoader, this provides the getGitHash function that returns a TJVB\GitHash\Values\GitHash value object that provides the hash() and short() function.

use TJVB\LaravelGitHash\Contracts\GitHashLoader;

public function example(GitHashLoader $gitHashLoader)
{
    echo $gitHashLoader->getGitHash()->hash();
} 

After publishing the config file with php artisan vendor:publish you can change the bindings for the different classes.
It is important to have the cache file pointed to a place that isn't shared between your deployments.

In the default configuration there are different ENV variables that can be used.

This package use tjvb/githash to provide the hash. This has different finders available. You can fill a specific finder to use. If you leave it empty it will add the default finders. (With the default factory it means all the finders from that project.)

After publishing the blade file php artisan vendor:publish you can change the blade. The location after publishing will be resources/views/vendor/githash/githash.blade.php here you can edit the blade how you want it.

It is possible to overwrite the different classes, this can be done by implementing the interfaces and update the config file. The config file contains the implementations and has a comment to point to the correct interface to implement.

This package uses a file to cache the hash. The cache with a file is used because this should be faster than getting the cache every time it is wanted. (Also depending on the finder and the repository size). It doesn't use the building Laravel cache to prevent the usage of a shared cache. With this file cache it is possible to see that by example one queue runner use another code version than the other runners. This can be helpful in debugging any problems.

Depending on the way you deploy your application it is possible that you don't have the repository information available. For this it will also be useful to write the hash to the cache file.

If you use Envoyer you don't have the git repository on your server. And the full storage dir will be shared between your deployments. That needs some customization.
First update your configuration to have a cache file outside the shared directory.

// in config/githash.php
    'cache_file' => base_path('githash.cache'),

Then add a new deployment hook that will be executed before you install your composer dependencies to place the hash in the cache file:

cd {{release}}

echo {{sha}} > githash.cache

With these changes you will have the cache file without the need to have the repository on the server and can use the hash on the wanted locations.

We (try to) document all the changes in CHANGELOG so read it for more information.

You are welcome to contribute, read about it in CONTRIBUTING

The MIT License (MIT). Please see License File for more information.