Difference between revisions of "Extensions:Automatic Backups"
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 1: | Line 1: | ||
| − | {{Extensioninfobox|title=Automatic Backups|desc=Sets up in-app automated backups.|auth=Mercury|status= | + | {{Extensioninfobox|title=Automatic Backups|desc=Sets up in-app automated backups.|auth=Mercury|status=Testing|github={{Github|user=itinerare|branch=extensions/auto-backups}}|LKVer=2.0.0|migration=no|package=yes}} |
<!-- Put a short summary of your extension here! --> | <!-- Put a short summary of your extension here! --> | ||
Facilitates automatic/scheduled backups of a site's /public directory-- under the assumption that all else (source code) is already backed up by virtue of originating from a different machine in the first place, thus including more would just waste space-- and database. While by default backups are saved to storage/app, it is '''HIGHLY RECOMMENDED''' that you configure either an off-server storage location for them or have a solution to move the backups off the server regularly, preferably automatically. To this end, optional Dropbox support is included. | Facilitates automatic/scheduled backups of a site's /public directory-- under the assumption that all else (source code) is already backed up by virtue of originating from a different machine in the first place, thus including more would just waste space-- and database. While by default backups are saved to storage/app, it is '''HIGHLY RECOMMENDED''' that you configure either an off-server storage location for them or have a solution to move the backups off the server regularly, preferably automatically. To this end, optional Dropbox support is included. | ||
| Line 6: | Line 6: | ||
== Installation == | == Installation == | ||
<!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. --> | <!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. --> | ||
| + | Pull the branch and update packages like so. | ||
| + | {{Composer}} | ||
== Configuration == | == Configuration == | ||
<!-- Is any configuration necessary? Describe it here! --> | <!-- Is any configuration necessary? Describe it here! --> | ||
Revision as of 07:20, 8 October 2021
| Description | Sets up in-app automated backups. |
|---|---|
| Author(s) | Mercury |
| Status | Testing |
| Github | extensions/auto-backups |
| LK Version | 2.0.0 |
| Uses a Package | |
Facilitates automatic/scheduled backups of a site's /public directory-- under the assumption that all else (source code) is already backed up by virtue of originating from a different machine in the first place, thus including more would just waste space-- and database. While by default backups are saved to storage/app, it is HIGHLY RECOMMENDED that you configure either an off-server storage location for them or have a solution to move the backups off the server regularly, preferably automatically. To this end, optional Dropbox support is included.
This is more or less just a for-convenience implementation of existing tools, ready to go give or take configuration as desired. Implements spatie/laravel-backup with some pre-configuration as well as support for Dropbox via benjamincrozat/laravel-dropbox-driver. Those wishing to customize the configuration in-depth are recommended to peruse the laravel-backup documentation.
Installation
Pull the branch and update packages like so.
| Installing packages with Composer: |
Commands are given as composer [command]; if you have not installed composer globally, they will be php composer.phar [command] instead.
|
You may need to run composer self-update (assuming you have not recently) before installing package(s). If possible, update to composer v2.x; you may need to use the command composer self-update --2.
|
If feasible, run composer update.
|
If you encounter memory issues: Locally, run composer update. Copy the composer.lock file to your site's server.
|
Run composer install.
|
