Answers.Body: <p>Instead of wrestling with artifacts and that whole approach I simply created a private repo on github, then set up a local satis that pulls in from that repo and then serves it to the installs as a composer repository when running <code>composer update</code>. Works like a charm.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-14T06:08:00.460Z
Answers.LastActivityDate: 2019-03-14T06:08:00.460Z
Answers.UserDisplayName: Anders
Body: <p>Has anyone been successful using Satis for composer repo(s) with Craft plugins? I have a repo set up with artifacts, that are posted as a public composer repo in the network. It finds the plugins and downloads, but for some reason I keep getting the following error whenever I try to do <code>composer update</code>:</p>
  
  <pre><code>[craft\composer\InvalidPluginException]
    Couldn't install vendor/plugin: Unable to determine the base path
  </code></pre>
  
  <p>It works if I do a local path and pull it in that way.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-11T00:00:37.467Z
Comments.Text: Wow, the crickets sure are loud here.
Comments.UserDisplayName: Anders
Tags: <plugin-development><craft3>
Title: Private Plugin Repository Using Satis
ThreadText: # Private Plugin Repository Using Satis
  
  (Asked by: username_0 on 2019-02-01)
  
  Has anyone been successful using Satis for composer repo(s) with Craft plugins? I have a repo set up with artifacts, that are posted as a public composer repo in the network. It finds the plugins and downloads, but for some reason I keep getting the following error whenever I try to do `composer update`:
  
  ```
  [craft\composer\InvalidPluginException]
    Couldn't install vendor/plugin: Unable to determine the base path
  
  ```
  
  It works if I do a local path and pull it in that way.
  
  **Tags:** plugin-development, craft3
  
  > **Comments:**
  > **username_0**: Wow, the crickets sure are loud here.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-03-14. Score: 1 | Accepted answer
  
  Instead of wrestling with artifacts and that whole approach I simply created a private repo on github, then set up a local satis that pulls in from that repo and then serves it to the installs as a composer repository when running `composer update`. Works like a charm.
  
  
  ---
  
  