Skip to content

Commit 3d101d3

Browse files
committed
Apply feedback
1 parent a41cc4a commit 3d101d3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/concepts/railpack.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ sidebar_position: 500
88

99
[Railpack](https://railpack.com/) is a tool for building container images from source code with minimal configuration. It is the successor to [Nixpacks](https://nixpacks.com/) and incorporates several lessons learned from running Nixpacks in production at [Railway](https://railway.com/) over the years.
1010

11-
In Defang deployments, one of the most common points of failure is a missing or invalid Dockerfile that can’t produce OCI-compliant images. This is especially common when Dockerfile are generated by LLMs or created by users with limited Docker experience. Since integrating Railpack into Defang, if no Dockerfile is provided, we now automatically build a working image for you using Railpack.
11+
In Defang deployments, one of the most common issues faced by users is a missing or invalid Dockerfile that can’t produce OCI-compliant images. This is especially common when Dockerfile are generated by LLMs or created by users with limited Docker experience. Since integrating Railpack into Defang, if no Dockerfile is provided, we now automatically build a working image for you using Railpack.
1212

1313
## How to trigger a Defang Railpack deployment
1414

15-
When you run a Defang Railpack deployment you need 2 components:
15+
When you run a Defang Railpack deployment, you need 2 components:
1616

1717
1. A working application
1818
2. A valid Compose file
@@ -44,7 +44,7 @@ If the deployment fails, here are some things you can try.
4444
4545
### Railpack Detection
4646
47-
To allow Railpack to generate a build plan for your project, please structure it to include the following files, or rename existing ones to be compatible.
47+
To allow Railpack to generate a build plan for your project, please restructure or rename your existing project files to be Railpack-compatible, as described for each framework below.
4848
4949
#### [Node](https://railpack.com/languages/node/)
5050
@@ -111,7 +111,7 @@ Your project will be detected as a Rust application if any of these conditions a
111111

112112
Your project will be detected as a Elixir application if any of these conditions are met:
113113

114-
- A mix.exs file exists in the root directory.
114+
- A mix.exs file exists in the root directory
115115

116116
#### [Static Sites](https://railpack.com/languages/staticfile)
117117

0 commit comments

Comments
 (0)