To make our package available to others, we just need to initialize the Git repository inside our folder of /packages/laraveldaily/laravel-permission-editor and push the code to GitHub, then register that repository on Packagist.
So, step by step...
Struggled a bit following the tutorial in places, but with some determination and lots of faff I actually released my first ever Laravel package! It won't set the world alight, but it will let you generate website thumbnails using the url2png API :) Feel free to have & any offer any recommendations :) https://github.com/gkimpson/url2png-laravel https://packagist.org/packages/gkimpson/url2png-laravel
It was probably more to do with me doing new concepts than anything you did wrong - although one part of chapter 5 - the PermissionEditorServiceProvider.php boot() method changes somewhat (the ->as('permission-editor'); is removed for instance - after a while I realised this is needed. It was still a very good tutorial and the final chapter with the information regarding the releasing the packages was super useful as this was a first for me :)
I think a good way would be to do a very basic package initially & then have this permissions-editor package as a more advanced package (as its involves other dependencies, routes, views etc..), similar to how you have done the Laravel Testing in two courses (one for beginners and one advanced).
Either way, I did a thing and made a package for the first time so i'm happy with that :) Keep up the good work Povilas!
so should we install our package dependencies like spati-permissions, before install our package ?
can we just dirctly install our package with it dependencies ?
thank you mr Povilas
Hey Mr.Modestas, so what if i publish new package depends on another packages with spesfic versions maybe......
can i let the end user when install my package download all dependencies of my package with right versions dirctly without write them on composer.json by him and without install them by him ?
because maybe the end user install wrong version, or maybe even don't relize that my package depends on another packages
Hi Povilas, congratulations to you and your team for this great tutorial.
I was wondering if the github repository has to be public in order to publish it in packagist. What if I have a modular application that works with multiple packages thatn can be optionally installed and those packages work only for that particular app? For example the main application has its core module that could be cloned from github, but then you could install other modules by requiring packages.
Since this packages only work with the core module, can they be a sort of private packages?
In case you need private packages (which it sounds that you do) - you need to use private packagist:
Image is missing in the following line:
Thanks for the notice, fixed!