c0c02eebd2
* Toggles the disabled state of auto_increment_prefix To insert a prefix you had to toggle the checkbox, save the settings and reload. With this script it is immediate. Fixes #1390 * Delete asset image: made checkbox more visible Related to #3153 * Added personal-access-token component * Created basic API testing configuration * First version of /components endpoind cest * On-the-fly bearer token generation * Completed testing of PATCH and PUT methods * Added /components/{id}/assets route with tests * Updated route and dataTable in view * Completed test assertion * Added links to assets in ComponentsAssets view * Linked Company in AssetView page * Fixed purchase_cost format expectation in ApiComponentsCest * Refactored api routes file Sorted all prefixes in alphabetical order, removed duplicate routes. For every prefix I placed first Route::resource and then any additional route in a Route::group. Expanded arrays for readability and consistency. Removed useless calls as create and edit everywhere. * Refactored and added one more test to ApiComponentsAssetsCest * Marked one test as incomplete, 404 response should return json * Fixed value expectation * Refactored getToken() * Added API debugging routes * Added more information to ValidationException reporting Now the payload contains the validation errors for each invalid attribute. * /apitests: refactored expectations in component assertions * Created ApiAssetsCest * /apitests: Cleanup in Exceptions/Handler * Reverted change to use * Marked two tests as incomplete, looking for solutions |
||
|---|---|---|
| .github | ||
| app | ||
| bootstrap | ||
| bower_components | ||
| config | ||
| database | ||
| docker | ||
| public | ||
| resources | ||
| routes | ||
| sample_csvs | ||
| storage | ||
| tests | ||
| .dockerignore | ||
| .env.example | ||
| .env.testing | ||
| .env.testing-ci | ||
| .env.tests | ||
| .gitattributes | ||
| .gitignore | ||
| .htaccess | ||
| .travis.yml | ||
| artisan | ||
| bower.json | ||
| c3.php | ||
| circle.yml | ||
| CODE_OF_CONDUCT.md | ||
| codeception.yml | ||
| composer.json | ||
| composer.lock | ||
| docker.env | ||
| Dockerfile | ||
| gh-changelog.php | ||
| gulpfile.js | ||
| index.html | ||
| install.sh | ||
| LICENSE | ||
| package.json | ||
| phpunit.xml | ||
| README.md | ||
| server.php | ||
| snipeit.sh | ||
Snipe-IT - Open Source Asset Management System
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 5.2.
Snipe-IT is actively developed and 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, and we have a Docker image available if that's what you're into.
Installation
For instructions on installing and configuring Snipe-IT on your server, check out the installation manual. (Please see the requirements documentation for full requirements.)
If you're having trouble with the installation, please check the Common Issues and Getting Help documentation, and search this repository's open and closed issues for help.
User's Manual
For help using Snipe-IT, check out the user's manual.
Bug Reports & Feature Requests
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.
Upgrading
Please see the upgrading documentation for instructions on upgrading Snipe-IT.
Announcement List
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.
Translations!
Please see the translations documentation for information about available languages and how to add translations to Snipe-IT.
Contributing
Please see the documentation on contributing and developing for Snipe-IT.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Security
To report a security vulnerability, please email security@snipeitapp.com instead of using the issue tracker.