snipe-it

A free open source IT asset/license management system

AGPL-3.0 License

Downloads
392
Stars
10.5K
Committers
302

Bot releases are hidden (Show)

snipe-it - v0.3.10-alpha

Published by snipe over 10 years ago

Minor update release.

  • Bug fixes
  • Improved language localizations

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v0.3.9-alpha

Published by snipe over 10 years ago

Minor update release.

  • Added ability for users to see assets checked out to them

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v0.3.8-alpha

Published by snipe over 10 years ago

  • Fixed some minor XSS issues
  • Added Suppliers section to assets
  • Added draft changelog

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v.0.3.5-alpha

Published by snipe over 10 years ago

  • Fixed a bug in the licensing system
  • Fixed a missed default for folks using MySQL in strict mode

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v.0.3.4-alpha

Published by snipe over 10 years ago

Added asset name display as a setting in the Settings menu.

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v.0.3.3-alpha

Published by snipe over 10 years ago

Bugfixes and improved internationalization strings.

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v.0.3.2-alpha

Published by snipe over 10 years ago

  • Improved admin-only functionality

IMPORTANT: If you're upgrading from v.0.3.0-alpha or earlier, make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v.0.3.1-alpha

Published by snipe over 10 years ago

  • Fixed CSV export
  • Upgraded to Laravel 4.1 to fix dependency

IMPORTANT: Make sure to update your hostname information in bootstrap/start.php, per the new requirements in Laravel 4.1.

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

If you run into a weird error like

Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::registerCoreContainerAliases() in /var/www/  
html/vendor/laravel/framework/src/Illuminate/Foundation/start.php on line 106 

Then try removing bootstrap/compiled.php and your vendors dir, and re-running php composer.phar update.

snipe-it - v0.3.0-alpha

Published by snipe over 10 years ago

Added QR codes, bugfixes

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

snipe-it - v0.2.0-alpha

Published by snipe almost 11 years ago

Bugfixes, upgraded to Bootstrap 3

snipe-it - v0.1.2-alpha

Published by snipe almost 11 years ago

Lots of bug fixes, improved responsive design (although still some work to do for full responsiveness on data tables.)

snipe-it - v0.1.1-alpha

Published by snipe almost 11 years ago

This release fixes some issues that users with mysql running in strict mode would have encountered while trying to seed the database for initial setup.

Please don't forget to run:

php composer.phar dump-autoload
php artisan migrate

.. from the project root after pulling the latest release to make sure your autoloader and database are up to date.

snipe-it - Initial alpha

Published by snipe almost 11 years ago

This is the initial pre-release of the Snipe IT asset management system. While this has been reasonably stable on our test systems, it's still going through additional QA, and probably shouldn't be considered viable for production until v1.0.0.

Package Rankings
Top 14.88% on Packagist.org
Top 3.53% on Proxy.golang.org
Badges
Extracted from project README
Crowdin Docker Pulls Twitter Follow Codacy Badge Tests All Contributors Discord