Composer with API Key - Meta Box

This topic has 3 replies, 4 voices, and was last updated 6 months, 3 weeks ago by JOANNA WHITTLE.

Viewing 4 posts - 1 through 4 (of 4 total)

Author

Posts
May 25, 2021 at 11:50 AM #28402

maybeadev
Participant

Hi:

The current example for using composer with the api key to grab the premium add-ons places the api key in the json file as part of the metabox repo url.

Is there support for using a custom request header in which to place the api key or http basic auth?

Thanks.

Add New Note to this Reply

June 1, 2021 at 4:15 PM #28590

Anh Tran
Keymaster

Hi, currently we don't have support for putting API key in the header yet or using it with basic auth. Can you share how you do it with Composer?

Add New Note to this Reply

June 3, 2021 at 9:05 PM #28683
axieller
Participant
You could use this Composer plugin to manage private packages: private-composer-installer see it here. In your composer.json add
```
{
      "type": "composer",
      "url": "https://packages.metabox.io/{%MB_KEY}"
}
```
under the "repositories" key.

Require the plugin

"ffraenz/private-composer-installer": "^5.0"

Then in your .env file add your license, e.g: MB_KEY='xxxxx'

Add New Note to this Reply
April 29, 2024 at 7:40 PM #45341

JOANNA WHITTLE
Participant

I would also love support for this!!! It's also how ACF Pro does it - ACF Pro Example

Add New Note to this Reply
Author

Posts

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.