# Install Sage as Composer dependecy (post-install-cmd?)

**URL:** https://discourse.roots.io/t/install-sage-as-composer-dependecy-post-install-cmd/12185
**Category:** sage
**Tags:** composer
**Created:** 2018-04-12T12:04:04Z
**Posts:** 4

## Post 1 by @LehtinenRiku — 2018-04-12T12:04:04Z

I have forked Sage as Composer dependecy in my WP project. Is it possible to “composer install” Sage, when install is done in WP project? Now it has to be done manually.

---

## Post 2 by @knowler — 2018-04-13T01:28:56Z

What is your use case for this? It kinda seems a bit strange since Sage is a starter theme and something you wouldn’t normally install as a dependency since it’s designed to be modified directly.

Or am I misreading you, and you’ve actually forked Sage, made your modifications, and are using Composer to use the _forked_ version in your project?

In either case, what is your project setup? Bedrock?

---

## Post 3 by @LehtinenRiku — 2018-04-13T06:04:09Z

Yes I’ve forked Sage and have my private repo for it. And then I’m trying to use it in my project.

Well it’s not Bedrock. I just followed this tutorial

> **[File-system layout for WordPress - using composer and git](https://easyengine.io/tutorials/composer-wordpress/git-file-system-layout/)**
>
> A non-default file-system layout for WordPress projects using composer and git. Everything is managed using stuff WordPress already supports.

---

## Post 4 by @ben — 2018-04-23T04:41:38Z

Use Bedrock! :smiley: …one option would be to [run a script](https://getcomposer.org/doc/articles/scripts.md#scripts) after update/install to run another `composer install` in the theme directory