Skip to content

Versioning wp-config.php seems problematic / insecure #122

@eyalroth

Description

@eyalroth

I'm pretty new with wordpress. Being a developer I wanted to version my wordpress with git, and decided to try Revisr out. I've followed the official instructions on how to use the plugin for staging, but it wasn't all that smooth.

I installed Wordpress on a Vultr VPS using their "one click" wordpress installation (they install wordpress for you). Their installation creates a custom DB name, username and password for wordpress. Thing is, by default Revisr commits wp-config.php which stores these credentials. In order to setup a local development wordpress site, one has to create exactly the same DB with the same username and password, which is not the most secure thing.

Is there a real need to version wp-config.php? Again I'm new to wordpress but it seems that this file contains mostly local-machine configuration; be it the DB credentials or even the Git executable path. For now I've added wp-config.php to my .gitignore and removed it from my repository.

What you guys think is the best practice here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions