79367642b1
* Added AWS url to example env * Upgrader - added check for new storage path and attempt to move * Ignore symlink * Updated paths for models * Moved copy methods * Added AWS_URL support For some reasin, Flysystem was generating the wrong AWS url (with a region included) * Switch to Flysystem for image uploads * Nicer display of image preview * Updated image preview on edit blades to use Flysystem * Twiddled some more paths * Working filesystems config * Updated Asset Models and Departments to use Flysystem * Janky workaround for differing S3/local urls/paths * Try to smartly use S3 as public disk if S3 is configured * Use public disk Storage options for public files * Additional transformer edits for Flysystem * Removed debugging * Added missing use Storage directive * Updated seeders to use Flysystem * Default logo * Set a default width We can potentially override this in settings later * Use Flysystem for logo upload * Update downloadFile to use Flysystem * Updated AssetFilesController to use Flysystem * Updated acceptance signatures to use Flysystem * Updated signature view to use Flysystem This isn’t working 100% yet * Use Flysystem facade for displaying asset image * Set assets path Should clean all these up when we’re done here * Added Rackspace support for Flysystem * Added Flysystem migrator console command * Added use Storage directive for categories * Added user avatars to Flysystem * Added profile avatar to Flysystem * Added the option to delete local files with the migrator * Added a check to prevent people from trying to move from local to local * Fixed the selectlists for Flysystem * Fixed the getImageUrl method to reflect Flysystem * Fixed AWS copy process * Fixed models path * More selectlist updates for Flysystem * Updated example .envs with updated env variable names * *sigh* * Updated non-asset getImageUrl() methods to use Flysystem * Removed S3 hardcoding * Use Flysystem in email headers * Fixed typo * Removed camera support from asset file upload We’ll find a way to add this in later (and add that support to all of the other image uploads as well) * Fixed path for categories * WIP - Switched to standard handleImages for asset upload. This is currently broken as I refact the handleImages method. Because the assets store/create methods use their own Form Request, the handleImages method doesn’t exist in that Form Request so it wil error now. * Fixed css URL error * Updated Debugbar to latest version (#6265) v3.2 adds support for Laravel 5.7 * Fixed: Missing CSS file in basic.blade.php (#6264) * Fixed missing CSS file in basic.blade.php * Added * Changed stylesheet import for authorize.blade.php * Updated composer lock * Added AWS_BUCKET_ROOT as env variable * Use nicer image preview for logo upload * Removed AssetRequest form request * Removed asset form request, moved custom field validation into model * Added additional help text for logo upload * Increased the size of the image resize - should make this a setting tho * Few more formatting tweaks to logo section of branding blade preview * Use Flysystem for asset/license file uploads * Use Flysystem for removing images from models that have been deleted * Enable backups to use Flysystem This only handles part of the problem. This just makes it so we can ship files to S3 if we want, but does not account for how we backup files that are hosted on S3 * Use Flysystem to download license files * Updated audits to use Flysystem |
||
|---|---|---|
| .github | ||
| .public/css/dist | ||
| ansible/freebsd | ||
| app | ||
| bootstrap | ||
| config | ||
| database | ||
| docker | ||
| public | ||
| resources | ||
| routes | ||
| sample_csvs | ||
| storage | ||
| tests | ||
| .all-contributorsrc | ||
| .dockerignore | ||
| .env.example | ||
| .env.testing | ||
| .env.testing-ci | ||
| .env.tests | ||
| .env.unit-tests | ||
| .gitattributes | ||
| .gitignore | ||
| .htaccess | ||
| .php_cs.dist | ||
| .travis.yml | ||
| artisan | ||
| bower.json | ||
| c3.php | ||
| CODE_OF_CONDUCT.md | ||
| codeception.yml | ||
| composer.json | ||
| composer.lock | ||
| CONTRIBUTING.md | ||
| crowdin.yml | ||
| Dockerfile | ||
| gh-changelog.php | ||
| index.html | ||
| install.sh | ||
| LICENSE | ||
| npm-shrinkwrap.json | ||
| package.json | ||
| phpmd.xml | ||
| phpunit.xml | ||
| README.md | ||
| server.php | ||
| snipeit.sh | ||
| upgrade.php | ||
| Vagrantfile | ||
| webpack.mix.js | ||
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.4.
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 has already been answered before opening a new issue.
PLEASE see the Getting Help Guidelines and Common Issues before opening a ticket, and be sure to complete all of the questions in the Github Issue template to help us to help you as quickly as possible.
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.
Libraries, Modules & Related Projects
Since the release of the JSON REST API, several third-party developers have been developing modules and libraries to work with Snipe-IT.
- Python Module by @jbloomer
- SnipeSharp - .NET module in C# by @barrycarey
- InQRy by @Microsoft
- SnipeitPS by @snazy2000 - Powershell API Wrapper for Snipe-it
- jamf2snipe by @ParadoxGuitarist - Python script to sync assets between a JAMFPro instance and a Snipe-II instance
As these were created by third-parties, Snipe-IT cannot provide support for these project, and you should contact the developers directly if you need assistance. Additionally, Snipe-IT makes no guarantees as to the reliability, accuracy or maintainability of these libraries. Use at your own risk. :)
Contributors
Thanks goes to all of these wonderful people (emoji key) who have helped Snipe-IT get this far:
This project follows the all-contributors specification. Contributions of any kind welcome!
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.