The user can run the artisan command, generate the package folder with the config and create the environment folder inside package, but sometimes, it's easy for the user to just create the config file in the config folder with the several environments and keep this file versioned. And in this way, it gets easier because the user doesn't have to remember another artisan command when deploy the project.
I hope it helps ... and thanks for sharing this oAuth Class!
Thanks for that...but base on your proposition i will build smth else... you will be able to use both ways of configuration... i will work on that during a weekend
The user can run the artisan command, generate the package folder with the config and create the environment folder inside package, but sometimes, it's easy for the user to just create the config file in the config folder with the several environments and keep this file versioned. And in this way, it gets easier because the user doesn't have to remember another artisan command when deploy the project.
I hope it helps ... and thanks for sharing this oAuth Class!