Module : Config Direct Save

Description :

This module allow you to :
- Make backup of configurations (when you check the backup checkbox).
- Override the sync (all files with old configuration) by the new configurations(replace all configurations files).

This module is useful when we work with differents databases.

We should make the directory sites/default/files/config_HASH on git to share differents configurations between development and productions Drupal 8 sites.

To have more details :
Page project : https://www.drupal.org/sandbox/matio89/2803927.

Git clone command :

 git clone --branch 8.x-1.x https://git.drupal.org/sandbox/matio89/2803927.git config_direct_save
cd config_direct_save 

When we install the module , here is the configuration page of this module :
YOUR-SITE/admin/config/development/configuration/full/update

Thanks.

Comments

matio89 created an issue. See original summary.

matio89’s picture

Assigned: matio89 » Unassigned
PA robot’s picture

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

ckhalilo’s picture

+1 for this module.

I found it today and I will most likely add it to every Drupal 8 Project.

visabhishek’s picture

Issue summary: View changes
sandeepguntaka’s picture

Automated Review

Please fix Error reported By PAReview.sh:
http://pareview.sh/pareview/httpsgitdrupalorgsandboxmatio892803927git

Manual Review

Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
No: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
No: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
No: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
  1. (*)No issues
  2. (+) No issues

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

visabhishek’s picture

Hi @sandeepreddyg : Looks like you forgot to change the status. Is this now RTBC after your review or are there application blockers left and this should be "needs work"?

sandeepguntaka’s picture

Status: Needs review » Reviewed & tested by the community
aamouri’s picture

+1 for this module

apaderno’s picture

Assigned: Unassigned » apaderno
Status: Reviewed & tested by the community » Fixed

I will update your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.

Here are some recommended readings to help with excellent maintainership:

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thank you, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks go the dedicated reviewer(s) as well.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.