Evolution of the api-platform/api-platform repository · Issue #2987 · api-platform/api-platform · GitHub
Skip to content

Evolution of the api-platform/api-platform repository #2987

Open
Open
Evolution of the api-platform/api-platform repository#2987

Description

@soyuka
soyuka
opened on May 18, 2026

Hi!

This repository will be changed from a template to an installer see #2980.

Several reasons to this, first we maintain symfony-docker and it is really the same as this repository which makes it hard to keep them in sync. In the future we'll just install API Platform inside a symfony-docker setup.

The PWA choice is also hard as many of users will want to setup their own stack for front-end development.

Last but not least having Laravel as a possible choice is something we want to offer from scratch, an installer makes this way easier for newcomers.

In the next months we'll slowly be closing issues from this repository and/or moving them to github.com/api-platform/core where development of the framework lives.

About Helm charts, we'll replace them by a similar solution directly in the symfony-docker project.

Activity

  1. soyuka
    pinned this issue on May 18, 2026

  2. soyuka commented on May 18, 2026

    @soyuka
    soyuka
    on May 18, 2026
    MemberAuthor

    Triage pass starting today

    We're triaging the 700 open issues on this repository over the next few days, per the rationale in this thread. Quick summary of how we'll handle each one:

    • Issues about the previous Docker/PWA/Helm distribution (Caddyfile, FrankenPHP config, Next.js PWA, Mercure hub, Helm charts, …) → closed with a pointer to the new installer and to dunglas/symfony-docker.
    • Questions / "how do I…" issues → closed with a pointer to api-platform/core Discussions and Stack Overflow.
    • Old, stale issues (3+ years, no engagement, or pre-3.0 annotation-era code samples that don't apply to current API Platform) → closed as stale.
    • Framework bugs and feature requests (serializer, GraphQL, validators, filters, providers, …) → transferred to api-platform/core for re-triage.
    • Anything ambiguous stays open for manual review.

    Each closed issue keeps its history and reactions; transferred issues keep the full thread on the new repo. Both actions are reversible — if we mishandle yours, just reply or reopen and we'll fix it.

    We're running this in small batches with a maintainer review on each, so expect notification activity but no surprises.

  3. andrew-demb commented on May 19, 2026

    @andrew-demb
    andrew-demb
    on May 19, 2026

    Links to symfony-docker are broken in the issue description.

    Current: https://github.com/api-platform/api-platform/issues/github.com/dunglas/symfony-docker
    Expected: https://github.com/dunglas/symfony-docker

    By the way, should symfony-docker eventually migrate to some GitHub organization rather than a personal namespace (dunglas), given that it has become the officially recommended setup for API Platform?

  4. soyuka commented on May 19, 2026

    @soyuka
    soyuka
    on May 19, 2026
    MemberAuthor

    By the way, should symfony-docker eventually migrate to some GitHub organization rather than a personal namespace (dunglas), given that it has become the officially recommended setup for API Platform?

    Probably that it should be under the symfony org not sure where they're at with this ping @dunglas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions