Download the PHP package navari/laravel-auto-deploy without Composer
On this page you can find all versions of the php package navari/laravel-auto-deploy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 laravel-auto-deploy
Laravel Autodeploy.
Save yourself the stress of ssh-ing into your server everything you make a push to your
production or staging branch. Simply, have your servers, pick up the changes and run your deployment or
update scripts. It is as simple as echo "Hello World. This package only works for Github version control systems.
Installation guide.
Require you having PHP and composer installed on your machine, and any Unix/Linux (or Mac) shell.
-
Require the latest version of the package with composer
-
After installation, if you are using Laravel 7.0+, you can move on unto the next step, otherwise you will have to add the Service Provider manually. Open the file
config/app.phpand find theprovidersarray. Add the line below to the end of the array: - You want to publish the configuration file (and maybe the auto deploy script we provide by default), run laravel artisan script
When ran, you will see two files created for you, the config/laradeploy.php and laradeploy.sh. You can delete or
modify the laradeploy.sh if you have your own script to run anytime the server pull some changes from your repository.
You will look into config/laradeploy.php to change the default settings we put in there.
Configurations.
Note that any changes you will want to make will always go into the file config/laradeploy.php.
Web Hooks
We support one VCS for now, Github. Your setup webhook on either one will be listed in the routes array:
Email Notifications
If you want to get notified anytime the server(s) pick up changes from
your repositories, you will have to change the subscribe key to true
and list email (or some emails) to send notifications to, in the config file.
You can list as many email as you want, and you can also change the template
(view) that will be sent as email.
It is worthy to note that we leverage your Laravel SMTP settings, which means you must have configured your Mail settings working before enabling this feature.
Security
Guarding your Web hooks, simply means that you have set a default token to be identified with
Github or Bitbucket request to your web hook endpoint on the server — and we encourage this.
It will limit the endpoint to only authorized party. If you have a SECRET_TOKEN set up, add them to your
.env file as either:
Any request made with mismatch token validation will be simply, rejected.
