Download the PHP package wearejh/stripped-db-provider without Composer
On this page you can find all versions of the php package wearejh/stripped-db-provider. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wearejh/stripped-db-provider
More information about wearejh/stripped-db-provider
Files in wearejh/stripped-db-provider
Package stripped-db-provider
Short Description Stripped DB Provider for Magento 2
License
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 stripped-db-provider
Jh Stripped Db Provider
This module can be configured to automatically send stripped databases periodically into an Amazon S3 Bucket in the cloud.
Installation
Add the following repositories to the repositories section of your composer.json
Then install like any regular composer package
Configuration
There are two areas of configuration. The first is project specific config, which is set in config.php and gets commited to the repository. The second is environment specific configuration which is added to the env.php file directly on the server.
Project Specific Configuration
All databases are stripped by default but you can define project specific tables whose data you wish to not be included in the dump by adding the following to your config.php file:
Where project_ignore_tables is a list of project specfic tables.
Environment Specific Configuration
Once Installed and deployed to production, you will want to configure it so that it automatically sends stripped DBs to the S3 Bucket. Edit the env.php file manually and set the following config (values below are examples):
Values are described in the following table:
| config | value |
|---|---|
| enabled | One of {0,1} |
| project-name | String. Unique name for the project (used to name the db dump) |
| cron_expr | A valid cron expression. Eg. "0 0/5 *" |
| bucket_name | String. AWS S3 Bucket name |
| region | String. AWS S3 Bucket region |
| access_key_id | String. AWS S3 Bucket access key id |
| secret_access_key | String. AWS S3 Bucket secret access key |
The Amazon S3 Bucket Details should be in LastPass. Ask your fellow developers if you can't find it or need help setting up.
After you have edited the env.php file, run the following command immediately :
Run upload manually
You can also manually trigger the stripped database upload from the command line by running the following command :
To do a full DB dump
Import a remote dump locally
You can use the module to import a dump from S3 directly to your local. It will back up your local admin accounts and reimport them
To skip admin accounts backup
Issues / Feature Request
Please open github issues for any issues you encounter or feature requests you want to see. PRs are of course welcomed.
Troubleshooting
If any project has 0.3.3 version installed of this module, getting a dependency error related to module: ifsnop/mysqldump-php ^2.12 while upgrading module to latest version then remove the below line from composer.json file of project root folder: { "type": "vcs", "url": "[email protected]:maciejslawik/mysqldump-php.git" }
