<p>I have a plugin that I developed in a symlinked folder locally.
I now want to deploy it to production.
But when I do <code>composer require namespace/pluginhandle</code> it gets symlinked. </p>

<p>What I want is to install it just like all the other production plugins - without a symlink.</p>

<p>I couldn't find instructions on how to do this in the <a href="https://docs.craftcms.com/v3/extend/plugin-guide.html#loading-your-plugin-into-a-craft-project" rel="nofollow noreferrer">docs</a>.</p>

CC BY-SA 4.0
2020-02-27T08:07:47.287Z
Did you remove it from the `"repositories"` section in your `composer.json`? Also, did you publish it to Packagist?
Oli
CC BY-SA 4.0
2020-02-28T11:01:49.883Z
@Oli I still have the `"repositories"` section pointing to my plugin dev folder. I'm not using Packagist. Should I just copy the entire folder into `/vendor` and then do a `composer update`?
Crafty Cat
<plugin-development><composer>
How to move a plugin from dev to prod?
# How to move a plugin from dev to prod?

(Asked by: username_0 on 2020-02-27)

I have a plugin that I developed in a symlinked folder locally.
I now want to deploy it to production.
But when I do `composer require namespace/pluginhandle` it gets symlinked.

What I want is to install it just like all the other production plugins - without a symlink.

I couldn't find instructions on how to do this in the [docs](https://docs.craftcms.com/v3/extend/plugin-guide.html#loading-your-plugin-into-a-craft-project).

**Tags:** plugin-development, composer
> **Comments:**
> **username_1**: Did you remove it from the `"repositories"` section in your `composer.json`? Also, did you publish it to Packagist?  
> **username_0**: @Oli I still have the `"repositories"` section pointing to my plugin dev folder. I'm not using Packagist. Should I just copy the entire folder into `/vendor` and then do a `composer update`?  

---

## 0 answers

