# Automating composer packaging for private plugins: sharing a prototype I made

**URL:** https://discourse.roots.io/t/automating-composer-packaging-for-private-plugins-sharing-a-prototype-i-made/14747
**Category:** bedrock
**Tags:** plugins
**Created:** 2019-02-04T14:55:18Z
**Posts:** 2

## Post 1 by @apinstein — 2019-02-04T14:55:18Z

Hi all-

Bedrock is really great! After trying to manage WP without true devops approaches, it has been really great to find such a good project for making a real WP dev path easy.

In converting our app to use Bedrock, I of course ran into the private plugins issue. I put together a small project / proof-of-concept to try to automate the management of private plugins in a clean way. I wanted to share this and get feedback from the community about the approach.

It’s a pretty simple concept:

- Use composer’s `artifact` repository type [which allows you to add a single composer repository via local path that points to a directory of ZIP files]
- Automate creation of appropriate zip files from a source directory of private plugins, without touching the source files.
- Make it easy for the user to then include these packages via composer commands without hand-editing composer.json

> **[apinstein/wordpress-private-plugins-composer](https://github.com/apinstein/wordpress-private-plugins-composer)**
>
> A script to conveniently package private Wordpress plugins into composer "artifact" repositories. - apinstein/wordpress-private-plugins-composer

I look forward to your feedback.

Thanks!  
Alan

---

## Post 2 by @system — 2019-03-18T14:55:18Z

This topic was automatically closed after 42 days. New replies are no longer allowed.