Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy through organisation (proxy with auth tokens) #174

Open
giggsey opened this issue May 23, 2020 · 4 comments
Open

Proxy through organisation (proxy with auth tokens) #174

giggsey opened this issue May 23, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@giggsey
Copy link
Contributor

giggsey commented May 23, 2020

Would it be possible to proxy to Packagist through an organisation? At the moment, it seems that is only possible through the main domain.

The organisation instructions say to add the organisation repo, but then you need to go to the proxy instructions to add a different repository for the main proxy repo.

Our use case is to keep all traffic for composer packages going through a central location.

Could be as simple as adding the proxy instructions onto the organisation view, so it says:

{
    "repositories": [
        {"type": "composer", "url": "https://giggsey-test.repo.repman.io"},
        {"type": "composer", "url": "https://repo.repman.io"},
        {"packagist": false}
    ]
}
@akondas akondas added the enhancement New feature or request label May 25, 2020
@akondas
Copy link
Member

akondas commented May 25, 2020

Assuming you will use an organization token, this would be an option. You could then let all traffic go through the organization's subdomain.

@giggsey
Copy link
Contributor Author

giggsey commented May 25, 2020

Authenticated is absolutely fine for my use case.

@akondas akondas changed the title Proxy through organisation Proxy through organisation (proxy with auth tokens) Oct 22, 2020
@giggsey
Copy link
Contributor Author

giggsey commented Oct 22, 2020

Doing this would require undoing some of the Composer v2 performance improvements done in #310.

@akondas
Copy link
Member

akondas commented Oct 22, 2020

Nobody said it would be easy 😉 . But we leave it in the backlog. Maybe there will be someone brave with enough time ⚔️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants