github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-03-09 06:52:08 -05:00
Code Issues 627 Packages Projects Releases Wiki Activity

[PR #312] Add Next.js example #377

New Issue
Open
opened 2025-11-06 14:24:56 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 14:24:56 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/312
Author: @maxproske
Created: 12/8/2022
Status: 🔄 Open

Base: master ← Head: next

📝 Commits (1)

  • 179afb8 Add link to official Next.js example

📊 Changes

2 files changed (+6 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)
➕ next/README.md (+5 -0)

📄 Description

Next.js is one of the most popular React frameworks, and awesome-compose is a fantastic springboard, so I think this example is a great addition for people looking here to Composeize their Next.js apps.

It's also a rapidly evolving framework, with every release being their biggest release ever, and often contains breaking changes. For example, bumping the minimum version of React to v18.2. For this reason, I think it's more appropriate to link to the official Next.js + Compose example, so it can be maintained by the Next.js community and Next.js team, and enjoy more frequent updates and finetuning.

This example is a bit different, and I know submodules aren't allowed https://github.com/docker/awesome-compose/pull/235#pullrequestreview-974465834. But I noticed some reviews in this repo can take up to a few months, so I hope you consider my reasoning and making an exception for Next.js!

Next.js and Compose is a powerful combo. Combined with Multistage builds, it can output up to 85% smaller Next.js apps! (Approximately 110 MB compared to 1 GB with create-next-app)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/312 **Author:** [@maxproske](https://github.com/maxproske) **Created:** 12/8/2022 **Status:** 🔄 Open **Base:** `master` ← **Head:** `next` --- ### 📝 Commits (1) - [`179afb8`](https://github.com/docker/awesome-compose/commit/179afb850572e45f6becc49282cb13a3a03f1d8f) Add link to official Next.js example ### 📊 Changes **2 files changed** (+6 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) ➕ `next/README.md` (+5 -0) </details> ### 📄 Description Next.js is one of the most popular React frameworks, and awesome-compose is a fantastic springboard, so I think this example is a great addition for people looking here to Composeize their Next.js apps. It's also a rapidly evolving framework, with every release being their biggest release ever, and often contains breaking changes. For example, bumping the minimum version of React to v18.2. For this reason, I think it's more appropriate to link to the [**official Next.js + Compose example**](https://github.com/vercel/next.js/tree/canary/examples/with-docker-compose), so it can be maintained by the Next.js community and Next.js team, and enjoy more frequent updates and finetuning. This example is a bit different, and I know submodules aren't allowed https://github.com/docker/awesome-compose/pull/235#pullrequestreview-974465834. But I noticed some reviews in this repo can take up to a few months, so I hope you consider my reasoning and making an exception for Next.js! Next.js and Compose is a powerful combo. Combined with Multistage builds, it can output up to 85% smaller Next.js apps! (Approximately 110 MB compared to 1 GB with create-next-app) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 14:24:56 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#377
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?