Git Versioning: ignore vendor & dist

  • Resolved marius.cucuruz

    (@mariuscucuruz)


    4 months ago

    tl;dr

    Would it be safe to exclude these directories from tracking with Git?

    • **/vendor/
    • **/assets/dist/
    • **/node_modules/

    Detailing:

    Similarly to this WF Question:

    I’d like to Git ignore all /vendor/ directories on my WP website; so I’m thinking of adding **/vendor/ to .gitignore. (…) Would it be safe to ignore it?

    I want to skim the fat off the repository for my WordPress website so I am considering ignoring some obvious directories from Git tracking. I can see the following directories currently in my website:

    • /wp-content/plugins/jetpack-boost/vendor/
    • /wp-content/plugins/jetpack/vendor/
    • /wp-content/plugins/jetpack-boost/app/assets/dist/

    My main worry is whether there would be any issues if I were to change host (i.e. move my website by git cloning on another server)?

    For extra context, I’m running my website in a Docker container (with docker compose ) and I’m also wondering if ignoring all /vendor/ and /assets/dist/ directories would cause any issues should I rebuild the container from scratch?

    • This topic was modified 4 months ago by marius.cucuruz. Reason: update tags
Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi @mariuscucuruz,

    Thanks for contacting us! For all Jetpack plugins all the directories that you have listed in your comment are required for them to work properly.

    Instead of excluding specific plugin directories, I recommend using WP-CLI ( https://wp-cli.org/) to automate the installation of WordPress, plugins, and themes when rebuilding the container.

    Best,

    Thread Starter marius.cucuruz

    (@mariuscucuruz)

    Thanks, @gaurav984!

    I’ll look into integrating WP-CLI with Docker (i.e. docker compose) to automate things as per your suggestion.

    Cheers

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.