# How Do You Manage a Single composer.json for Bedrock & Sage with Private Repos?

**URL:** https://discourse.roots.io/t/how-do-you-manage-a-single-composer-json-for-bedrock-sage-with-private-repos/27003
**Category:** bedrock
**Tags:** bedrock, sage10
**Created:** 2024-04-17T11:04:53Z
**Posts:** 1

## Post 1 by @Dogit — 2024-04-17T11:04:53Z

Hey everyone,

I’m setting up a WordPress site using Bedrock and plan to use a Sage theme pulled from a private GitHub repo. I want to manage everything—plugins and theme—from one `composer.json` file in Bedrock. Example:

```
"repositories": [
    {
      "type": "composer",
      "url": "https://wpackagist.org",
      "only": ["wpackagist-plugin/*", "wpackagist-theme/*"]
    },
    {
      "type": "vcs",
      "url": "https://github.com/vendor/my-sage-theme1"
    }
  ],
```

Here are a few things I’m curious about:

- Is it a good idea to handle one bedrock for 10+ projects with the same plugins and _sage-theme1_, _sage-theme2_ fetched dynamically based on the url. What should I watch out for?
- Any tips on integrating a Sage theme from a private repo without having to tweak `composer.json` for each update?
- How do you deal with updates, especially with private repos in the mix?

Would love to hear if anyone has a neat setup or tips on making this smooth and secure.

Thanks!