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 #489] Update README.md #505

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

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/489
Author: @katelovescode
Created: 5/17/2024
Status: 🔄 Open

Base: master ← Head: patch-1

📝 Commits (1)

📊 Changes

1 file changed (+7 additions, -1 deletions)

View changed files

📝 official-documentation-samples/rails/README.md (+7 -1)

📄 Description

Clarifies specifics about skipping Docker in Rails 7 because Rails 7 now generates a production Dockerfile that makes using Docker/Docker Compose in local development challenging. The steps included in this document are only sufficient for Rails & Docker Compose in a development environment for Rails 7. (In order to run as-is with the production dockerfile, more steps are necessary for the compose, including passing the master key, etc.)

🔄 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/489 **Author:** [@katelovescode](https://github.com/katelovescode) **Created:** 5/17/2024 **Status:** 🔄 Open **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`6444871`](https://github.com/docker/awesome-compose/commit/6444871334425e69193f66d82f450e1273e0392e) Update README.md ### 📊 Changes **1 file changed** (+7 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `official-documentation-samples/rails/README.md` (+7 -1) </details> ### 📄 Description Clarifies specifics about skipping Docker in Rails 7 because Rails 7 now generates a production Dockerfile that makes using Docker/Docker Compose in local development challenging. The steps included in this document are only sufficient for Rails & Docker Compose in a development environment for Rails 7. (In order to run as-is with the production dockerfile, more steps are necessary for the compose, including passing the master key, etc.) --- <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:27:38 -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#505
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?