Download the PHP package sammyjo20/lasso without Composer
On this page you can find all versions of the php package sammyjo20/lasso. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sammyjo20/lasso
More information about sammyjo20/lasso
Files in sammyjo20/lasso
Package lasso
Short Description Lasso - Asset wrangling for Laravel made simple.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package lasso
# Lasso
### Asset wrangling for Laravel made simple.
[](//packagist.org/packages/sammyjo20/lasso) [](//packagist.org/packages/sammyjo20/lasso) [](//packagist.org/packages/sammyjo20/lasso)
[](https://img.shields.io/github/actions/workflow/status/sammyjo20/lasso/tests.yml?label=tests)
Introduction
Deploying assets in Laravel can be a nightmare. One problem developers have is dealing with their built assets (created by Webpack/Laravel Mix or Vite). Do you store them in version control? Do you deploy them on the server? What if I'm working with a team? Each of these solutions for assets can cause headaches for the developer, including merge conflicts and slowing down servers.
Lasso is a Laravel package designed to take the headaches out of deploying assets to your servers. It works great on load balanced environments too.
What does Lasso do?
Lasso compiles your assets on your local machine or within Continuous Integration (e.g GitHub Actions) and then uploads the assets to one of your Laravel Filesystems. This harnesses the power of your local machine which is likely much more powerful than the server.
During deployment, Lasso will then download your assets from the filesystem. It uses Git to keep track of the last asset bundle created, as well as automatically cleans old bundles.
Installation
Lasso supports Laravel 9+ and PHP 8.1 or higher. To install Lasso, simply run the composer require command below:
After that, run the command below to create the lasso.php config file:
Configuration
Now make sure to configure the lasso.php config file in your app/config directory. Make sure to specify a Filesystem Disk you would like Lasso to use.
If you have multiple projects, make sure to change the "upload_to" path, otherwise you may have asset conflicts in your applications.
Getting Setup
Make sure to add all of your public assets that are created by Webpack/Laravel Mix to your .gitignore file. Make sure to also add the ".lasso" directory to your .gitignore file.
Example:
The .lasso folder is a temporary directory created by Lasso to keep assets while they're being zipped up. This folder is automatically created and deleted, but it's good to ignore this directory anyway, just in case Lasso falls over before it reaches the cleanup phase.
Vite Support
Lasso supports Vite with a few config changes. In config/lasso.php, change compiler.script to yarn run build, compiler.excluded_files to ['hot'] to exclude Vite's "hot" file and compiler.output to disable (progress bar output is not yet supported for Vite).
Recommended Usage
Lasso comes with two commands that should be used by your project/deployment process. The recommended usage is to run the "publish" command on your local machine, which is likely much more powerful than Continuous Integration or compiling on the server.
Publish
The publish command should be executed when you would like to upload/publish new assets to your application. Lasso will run the provided script (e.g npm run production) and then zip up the files created by the compiler (e.g Webpack).
After running this command, Lasso will create a "lasso-bundle.json" file in your application's root directory. This is the recommended approach as when you commit the file, Lasso will use this to download the latest bundle relating to your commit. If you don't use Git, for example if you are compiling assets within Continuous Integration, you can add the --no-git flag to the command.
Warning: When using the --no-git flag, versioning will be limited as the lasso-bundle.json is stored in your Filesystem, rather than your repository. Using Git is the recommended approach.
If you use git, and want to easily keep track of which bundle file is for what commit, use the --use-commit flag. It will ensure the bundle zip file name is the first 12 characters of the commit hash. This also adds the advantage of publishing the bundles during your CI pipeline, without having to make a new commit, whilst giving the versioning benefits of using git.
Pull
The pull command should then be executed on your deployment script, or on the servers which will require the assets to be on. Simply run the command below. If you are using Laravel Forge, add this command to your deployment script. If you are using Laravel Envoyer, add this to the list of hooks during your deployment. It should be run on every server.
Use the --use-commit flag when pulling, if you are publishing the bundles with the --use-commit flag.
Usage within Continuous Integration (CI) e.g Github Actions
To use Lasso during continuous integration, it's recommended to run the php artisan lasso:publish command, and then commit the "lasso-bundle.json" file which is created. If you aren't able to commit files during your CI process, use the --no-git flag on the command, e.g: php artisan lasso:publish --no-git
Read this excellent blog post by Alex Justesen on how to integrate Lasso with your CI/CD pipeline: https://dev.to/alexjustesen/laravel-cicd-pipeline-w-lasso-and-github-actions-53gm
Multiple Environments
Out of the box, Lasso supports multi-environment applications. If your application has a staging environment, for example - you can use the LASSO_ENV environment variable to set the current environment. On your web servers:
Webhooks
Lasso can also trigger webhooks when a command has been executed successfully. Simply list the URLs in the "webhooks" array in the lasso.php config file.
Cleanup
Lasso will automatically try to keep your Filesystem clean, and will automatically delete old bundles. You can increase/decrease the amount of Bundles Lasso will keep per enviroment by setting the max_bundles configuratiion variable in the config/lasso.php file.
Excluded files/directories
Lasso will copy the public directory during it's publish process. If you have any files or directories that you would like Lasso to ignore during this process, specify them in the excluded_files and excluded_directories configuation variables in the config/lasso.php file.
Thanks
Special thanks to @codepotato for the logo! ❤️
Security
If you find any security related issues, please send an email to [email protected]
And that's it! ✨
This is my first Laravel package, I really hope it's been useful to you, if you like my work and want to show some love, consider buying me some coding fuel (Coffee) ❤
All versions of lasso with dependencies
ext-json Version *
ext-zip Version *
illuminate/console Version ^10.0 || ^11.0
illuminate/filesystem Version ^10.0 || ^11.0
illuminate/support Version ^10.0 || ^11.0
symfony/finder Version ^6.0 || ^7.0
symfony/process Version ^6.0 || ^7.0
league/flysystem Version ^3.0