This is a FOSS project for asset management in IT Operations. Knowing who has which laptop, when it was purchased in order to depreciate it correctly, handling software licenses, etc.
It is built on Laravel 4.1 and uses the Sentry 2 package.
This project is being actively developed (at what seems like breakneck speed sometimes!) We're still in alpha release, so this is NOT recommended for production use yet, as many more things will likely change before v1.0-stable is ready - but we're releasing quite frequently. (Check out the live demo here.)
This is web-based software. This means there there is no executable file (aka no .exe files), and it must be run on a web server and accessed through a web browser. It runs on any Mac OSX, flavor of Linux, as well as Windows.
Installation and configuration documentation for this project has been moved to http://docs.snipeitapp.com. This provides a more easily navigated, organized view of the documentation, and is based off of the documentation branch in this repo. Contributions and bugfixes to the documentation are always welcome!
We'll be adding a long-overdue user's manual soon as well.
Feel free to check out the GitHub Issues for this project to open a bug report or see what open issues you can help with. Please search through existing issues (open and closed) to see if your question hasn't already been answered before opening a new issue.
We use Waffle.io to help better communicate our roadmap with users. Our project page there will show you the backlog, what's ready to be worked on, what's in progress, and what's completed.
To be notified of important news (such as new releases, security advisories, etc), sign up for our list. We'll never sell or give away your info, and we'll only email you when it's important.
- PHP 5.4 or later
- MCrypt PHP Extension
Whenever you pull down a new version from master or develop, when you grab the latest official release, make sure to run the following commands via command line:
php composer.phar dump-autoload
php artisan migrate
Forgetting to do this can mean your DB might end up out of sync with the new files you just pulled, or you may have some funky cached autoloader values. It's a good idea to get into the habit of running these every time you pull anything new down. If there are no database changes to migrate, it won't hurt anything to run migrations anyway.