Hiya,
When I search by "Laravel App Distribution" I find some deploy methods to get Laravel running on a shared / private / local / production server. But my point is diferent.
Laravel is a great famework to develop applications. In example, I've coded a DNS Management application. I'd like people, without any coding experience, could download and install my app.
Laravel, traditional approach, needs to run composer install, bower install... and before of this, be able to install it on a server. I'd like to be able to download a tar / zip, upload to my server, create a database and then run an install script.
Some questions have come in mind:
In order to not use bower, can I copy AdminLTE CSS / JS to public folders?
In order to not use composer, can I tar / zip all code including vendor folder?
What do you think about?
@pacoorozco If you’re wanting people to just be able to download your files, and upload them to their own service, then yes, you’re going to need to bundle compiled assets and vendor files.
As for the installation process, you’re going to need to create that. You could have a middleware class that checks for an .env file. If it doesn’t exist, display a form that asks for things like database credentials, and write them to an .env file on submit. So you’ll also need to check the script has “write” permissions, too.
