# \#composer

**URL:** https://forum.gitlab.com/tag/composer/187.md

[Latest](https://forum.gitlab.com/latest.md) · [Categories](https://forum.gitlab.com/categories.md) · [Tags](https://forum.gitlab.com/tags.md)

---

## [CI Component testing vs. metadata access](https://forum.gitlab.com/t/ci-component-testing-vs-metadata-access/133187)

<div class="topic-metadata">

**Author:** [@pmhahn](https://forum.gitlab.com/u/pmhahn)\
**Replies:** 1\
**Last updated:** [June 18, 2026, 7:21pm UTC](https://forum.gitlab.com/t/ci-component-testing-vs-metadata-access/133187 "2026-06-18T19:21:34Z")

</div>

Problem to solve I have a GitLab CI component, which needs an associated docker image. Currently both template/component-name.yml and the Dockerfile live in the same git repository. I follow best practice and test the co…

---

## [Example GitLab Runner docker compose configuration](https://forum.gitlab.com/t/example-gitlab-runner-docker-compose-configuration/67344)

<div class="topic-metadata">

**Author:** [@TyIsI](https://forum.gitlab.com/u/TyIsI)\
**Replies:** 13\
**Last updated:** [March 18, 2026, 11:36am UTC](https://forum.gitlab.com/t/example-gitlab-runner-docker-compose-configuration/67344 "2026-03-18T11:36:21Z")

</div>

After having spent some time the other day to redo my (“standalone”) runner setup, I figured that I would share this for the benefit of the community. .env: RUNNER\_NAME=RUNNER-NAME REGISTRATION\_TOKEN=TOKEN CI\_SERVER\_UR…

---

## [Sharing a .gitlab-ci.yml for a docker runner that creates composer packages on push](https://forum.gitlab.com/t/sharing-a-gitlab-ci-yml-for-a-docker-runner-that-creates-composer-packages-on-push/116385)

<div class="topic-metadata">

**Author:** [@cloudcogs](https://forum.gitlab.com/u/cloudcogs)\
**Replies:** 0\
**Last updated:** [November 5, 2024, 9:06am UTC](https://forum.gitlab.com/t/sharing-a-gitlab-ci-yml-for-a-docker-runner-that-creates-composer-packages-on-push/116385 "2024-11-05T09:06:09Z")

</div>

Problem to solve Make self hosted, private projects available via composer packages. The below file will create composer packages versioned as dev-master once a push is executed to the master branch. Process is: Chec…

---

## [Package build Pipeline - 401 Unauthorised](https://forum.gitlab.com/t/package-build-pipeline-401-unauthorised/93337)

<div class="topic-metadata">

**Author:** [@lind101](https://forum.gitlab.com/u/lind101)\
**Replies:** 2\
**Last updated:** [September 10, 2024, 2:23pm UTC](https://forum.gitlab.com/t/package-build-pipeline-401-unauthorised/93337 "2024-09-10T14:23:22Z")

</div>

I’ve been using the GitLab composer CI template for over a year now to build PHP packages for my project. It worked perfectly every time I pushed code updates to the repository or added a tag it would build a new package…

---

## [Cannot access composer registry in CI with $CI\_JOB\_TOKEN authentication](https://forum.gitlab.com/t/cannot-access-composer-registry-in-ci-with-ci-job-token-authentication/44208)

<div class="topic-metadata">

**Author:** [@philipsorst](https://forum.gitlab.com/u/philipsorst)\
**Replies:** 6\
**Last updated:** [July 22, 2024, 6:35pm UTC](https://forum.gitlab.com/t/cannot-access-composer-registry-in-ci-with-ci-job-token-authentication/44208 "2024-07-22T18:35:28Z")

</div>

We are using GitLab Enterprise Edition 13.4.3-ee and the composer package registry. Publishing to the registry in a CI step with authentication via $CI\_JOB\_TOKEN works fine. However composer install on a depending projec…

---

## [Better understanding Composer registry](https://forum.gitlab.com/t/better-understanding-composer-registry/54243)

<div class="topic-metadata">

**Author:** [@valentin-ed](https://forum.gitlab.com/u/valentin-ed)\
**Replies:** 7\
**Last updated:** [February 2, 2024, 10:09am UTC](https://forum.gitlab.com/t/better-understanding-composer-registry/54243 "2024-02-02T10:09:10Z")

</div>

How gitlab create composer package to registry ? I’m currently working on building several “module” to be usable throuhg “composer” cli. In some of this module i have to build “assets” with node/npm and webpack. For th…

---

## [Unable to read from package registry, composer and/or maven](https://forum.gitlab.com/t/unable-to-read-from-package-registry-composer-and-or-maven/94007)

<div class="topic-metadata">

**Author:** [@padafi](https://forum.gitlab.com/u/padafi)\
**Replies:** 4\
**Last updated:** [October 19, 2023, 5:22am UTC](https://forum.gitlab.com/t/unable-to-read-from-package-registry-composer-and-or-maven/94007 "2023-10-19T05:22:17Z")

</div>

I can’t install private packages stored on gitlab, I use my organization gitlab installation where I’m not the admin. I’ve problems with maven and composer but in this post I will focus on composer I followed all the i…

---

## [Is there a way to protect package archives in the composer registry from being publicly downloadable?](https://forum.gitlab.com/t/is-there-a-way-to-protect-package-archives-in-the-composer-registry-from-being-publicly-downloadable/58820)

<div class="topic-metadata">

**Author:** [@daniel.kreuer.juit](https://forum.gitlab.com/u/daniel.kreuer.juit)\
**Replies:** 0\
**Last updated:** [September 21, 2021, 8:27am UTC](https://forum.gitlab.com/t/is-there-a-way-to-protect-package-archives-in-the-composer-registry-from-being-publicly-downloadable/58820 "2021-09-21T08:27:35Z")

</div>

Greetings! Having the ability to have a composer registry for packages is great. But I realized that packages published there are publicly downloadable even if the project itself is private. This means the URL stored fo…

---

## [Getting "404 Group Not Found" when trying to deploy composer package](https://forum.gitlab.com/t/getting-404-group-not-found-when-trying-to-deploy-composer-package/50352)

<div class="topic-metadata">

**Author:** [@avrjeff](https://forum.gitlab.com/u/avrjeff)\
**Replies:** 2\
**Last updated:** [March 17, 2021, 6:31am UTC](https://forum.gitlab.com/t/getting-404-group-not-found-when-trying-to-deploy-composer-package/50352 "2021-03-17T06:31:33Z")

</div>

I just created a new project and I’m using a .gitlab-ci.yml to build a composer package, but am getting a “404 Group Not Found” error: The “https://gitlab.com/api/v4/group/996XXXX/-/packages/composer/packages.json” file…

---

## [Error pipeline](https://forum.gitlab.com/t/error-pipeline/40434)

<div class="topic-metadata">

**Author:** [@michaelleonzio](https://forum.gitlab.com/u/michaelleonzio)\
**Replies:** 2\
**Last updated:** [August 10, 2020, 9:53am UTC](https://forum.gitlab.com/t/error-pipeline/40434 "2020-08-10T09:53:15Z")

</div>

I have an issue when pushing my project update, can anyone help me?