laravel-boilerplate VS Snipe IT

laravel-boilerplate

cd /opt/bitnami/ mkdir projects && cd projects git clone https://github.com/rappasoft/laravel-boilerplate cd laravel-boilerplace cp .env.example .env composer install npm install npm run prod php artisan key generate php artisan storage:link sudo chown -R daemon:daemon /opt/bitnami/projects/laravel-boilerplate/storage sudo chown -R daemon:daemon /opt/bitnami/projects/laravel-boilerplate/bootstrap

So you don't think I did all this because I didn't make it open source? It wasn't meant to be an open source project, I said I built a blog for myself. If you want some open source projects, I · have · a · few.

If you need a rather basic setup boilerplate I can recommend https://github.com/rappasoft/laravel-boilerplate aswell as the standard "Jetstream" which comes in v8. I currently use that + Orchid as a admin panel for any new smaller project.

Snipe-IT for Asset Management

At work I use snipeIT to manage our asset inventory, it's fairly quick to spin up with docker and it's quite customisable https://snipeitapp.com/

Another great open source asset management system to check out is Snipe-IT. https://github.com/snipe/snipe-it

I have used it for years both self hosted and with them hosting and it's been a great low cost solution for asset management.

If you like the IT method of asset management, then Snipe-IT is what you want. If you want something more inventory-y and parts-y, then check out PartKeepr or Inventree.

We use SnipeIT

I very strongly disagree, use serial numbers if at all possible, set up Snipe-IT, and you'll never have to change labels again. As long as you are the one handling provisioning, repairs and such, or those who do is allowed access, you'll always know the location, status and ownership of everything in there.