laravel-backup | A mysql database backup package for laravel | Continuous Backup library

I have deployed a laravel application in Elastic Beanstalk with Load Balancing. I have to backup my database daily and store it in s3 bucket so I am using Laravel-backup-server package. And I have set up cronjob using Nginx. When I manually run php artisan schedule:run in my local machine it works fine but when I deploy to Aws it's not running the cron job. My setup looks something like this

.ebextensions/cron-setup.config

I have my composer.json with Guzzle 6.5.2 with Laravel Framework 6.20.30

But when I run composer install or composer update, it install the Guzzle 6.5.5, Why? If I am saying that it's 6.5.2?

Am using https://spatie.be/docs/laravel-backup/v7/introduction for backup and I tried to backup database using php artisan backup:run but i got these errors:

Hi I am unable to install Laravel backup package spatie laravel backup

Showing below error massages

Problem 1 - Root composer.json requires spatie/laravel-backup ^7.6 -> satisfiable by spatie/laravel-backup[7.6.0]. - spatie/laravel-backup 7.6.0 requires ext-pcntl * -> it is missing from your system. Install or enable PHP's pcntl extension.

To enable extensions, verify that they are enabled in your .ini files: - F:\server8030\php\php.ini You can also run php --ini inside terminal to see which files are used by PHP in CLI mode.

Any one can help me to success

I am using php 7.4 and laravel for our project. We are working on it as a group of two. So whenever my co-worker adds a package, i have to run composer install to install the package. But now when i try to run composer install, i get the following error:

I'm working in a new project in laravel.I am in starting state of the project.
At initial , I try to run the install spatie/laravel-backup package from composer. It shows the binding Resolution Exception. then , i leave to installation.
I then start to make dynamic the heading. and try to redirect the title button to the welcome page through route.but it still shows the bindingResolutionException as of before.

web.php

When running composer require league/flysystem-aws-s3-v3 I get:

league/flysystem-aws-s3-v3[2.0.0, ..., 2.x-dev] require league/flysystem ^2.0.0 -> found league/flysystem[2.0.0-alpha.1, ..., 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

In my composer.json there is no mention of league/flysystem, but it does appear in my composer.lock as "league/flysystem": "^1.1",. It looks like I have a few packages (like spatie/laravel-backup) that have this as an dependancy.

How do I proceed? I'm not sure how to update a package that other packages have as an dependancy, and that these other packages have also fixed to a specific version.

Hi, I am trying solve some problem when I am install voyager. When I try to run composer require I am getting the out of memory error. I am not understand what exably happend. Its result on my console:

@DESKTOP->>>>> /c/xampp/htdocs/ (master) $ composer require tcg/voyager Using version ^1.4 for tcg/voyager ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 134217736 bytes) in phar://C:/composer/composer.phar/src/Composer/DependencyResolver/RuleSet.php on line 83```

Maybe there's a problem with the composer.JSON, something I need to check out. What you should pay attention to what is the problem My composer.json file``` {

I have deployed a Laravel application with Laradock.

I want to point out that the database connection works fine (users can register, login, ... etc.).

In order to back up the application, I have installed the Spatie's Laravel Backup package.

I set up all config variables accordingly as follows:

config/backup.php