Caddyfile is not autogenerated for SPA applications

[iloveitaly]

Here's how to reproduce (use this branch):

git clone http://github.com/iloveitaly/python-starter-template
cd python-starter-template
just build_javascript

Here's the build output

╭────────────────╮
│ Railpack 0.2.1 │
╰────────────────╯

  ⚠ Failed to read config file `railpack.json`
  Use the following schema to validate your config file: https://schema.railpack.com

  ↳ Detected Node
  ↳ Using pnpm package manager
  ⚠ Node_modules directory found in project root, this is likely a mistake
  ⚠ It is recommended to add node_modules to the .gitignore file

  Packages
  ──────────
  pnpm  │  9.15.9   │  railpack default (9)
  node  │  22.17.0  │  package.json > engines > node (^22.17.0)

  Steps
  ──────────
  ▸ install
    $ pnpm install --frozen-lockfile --prefer-offline

  ▸ build
    $ pnpm run build

  Deploy
  ──────────
    $ caddy run --config /Caddyfile --adapter caddyfile 2>&1

docker buildx build web --build-arg BUILDKIT_SYNTAX=ghcr.io/railwayapp/railpack-frontend:latest -f web/railpack.json -t python-starter-template-javascript:51c797a294382f7975060c40fdd2da07edaae0de-dirty --platform linux/amd64 --cache-to type=inline --cache-from ghcr.io/iloveitaly/python-starter-template-javascript:latest --label org.opencontainers.image.description="Used for building javascript assets, not for deployment"
[+] Building 1.1s (10/19)                                                                                                                                                                        docker:orbstack
 => [internal] load build definition from railpack.json                                                                                                                                                     0.0s
 => => transferring dockerfile: 3.48kB                                                                                                                                                                      0.0s
 => resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:latest                                                                                                                     0.6s
 => [auth] railwayapp/railpack-frontend:pull token for ghcr.io                                                                                                                                              0.0s
 => CACHED docker-image://ghcr.io/railwayapp/railpack-frontend:latest@sha256:46c992da3e89c3dd327506efd3b7fbe9507bb63d7343d00fd45ce23f1e8a532b                                                               0.0s
 => => resolve ghcr.io/railwayapp/railpack-frontend:latest@sha256:46c992da3e89c3dd327506efd3b7fbe9507bb63d7343d00fd45ce23f1e8a532b                                                                          0.0s
 => load build definition from railpack.json                                                                                                                                                                0.0s
 => => transferring dockerfile: 3.48kB                                                                                                                                                                      0.0s
 => CANCELED docker-image://ghcr.io/railwayapp/railpack-builder:latest                                                                                                                                      0.1s
 => => resolve ghcr.io/railwayapp/railpack-builder:latest                                                                                                                                                   0.1s
 => CANCELED docker-image://ghcr.io/railwayapp/railpack-runtime:latest                                                                                                                                      0.1s
 => => resolve ghcr.io/railwayapp/railpack-runtime:latest                                                                                                                                                   0.1s
 => loading .                                                                                                                                                                                               0.0s
 => CANCELED copy /railpack/caddy                                                                                                                                                                           0.1s
 => ERROR copy /Caddyfile                                                                                                                                                                                   0.1s
------
 > copy /Caddyfile:
------
ERROR: failed to solve: lstat /Caddyfile: no such file or directory
error: Recipe `build_javascript` failed on line 116 with exit code 1

The node_modules notice was also strange since I definitely have that in my .gitignore (within the web directory)

[coffee-cup]

The node_modules notice was also strange since I definitely have that in my .gitignore (within the web directory)

Railpack doesn't currently automatically ignore anything. So if the directory being built contains node_modules, it will be loaded into the build context. Hence the message

As for the Caddy file issue, I think something else might be going on here. The first time I run the build_javascript command I get

The first time I run the `build_javascript` command I get

╭────────────────╮
│ Railpack 0.2.1 │
╰────────────────╯

  ↳ Detected Node
  ↳ Using pnpm package manager
  ↳ Deploying as vite static site
  ↳ Output directory: dist

  Packages
  ──────────
  node   │  22.17.0  │  package.json > engines > node (^22.17.0)
  pnpm   │  9.15.9   │  railpack default (9)
  caddy  │  2.10.0   │  railpack default (latest)

  Steps
  ──────────
  ▸ install
    $ pnpm install --frozen-lockfile --prefer-offline

  ▸ build
    $ pnpm run build

  ▸ caddy
    $ caddy fmt --overwrite /Caddyfile

  Deploy
  ──────────
    $ caddy run --config /Caddyfile --adapter caddyfile 2>&1

docker buildx build web --build-arg BUILDKIT_SYNTAX=ghcr.io/railwayapp/railpack-frontend:latest -f web/railpack.json -t python-starter-template-javascript:96a2152b55626c32d783521bb8298b063af8b048 --platform linux/amd64 --cache-to type=inline --cache-from ghcr.io/iloveitaly/python-starter-template-javascript:latest --label org.opencontainers.image.description="Used for building javascript assets, not for deployment"
/etc/zshenv:4: SSH_CONNECTION: parameter not set
[+] Building 66.7s (9/23)                                                                                                                                       docker:orbstack
 => [internal] load build definition from railpack.json                                                                                                                    0.1s
 => => transferring dockerfile: 5.00kB                                                                                                                                     0.0s
 => resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:latest                                                                                    1.8s
 => docker-image://ghcr.io/railwayapp/railpack-frontend:latest@sha256:46c992da3e89c3dd327506efd3b7fbe9507bb63d7343d00fd45ce23f1e8a532b                                     1.6s
 => => resolve ghcr.io/railwayapp/railpack-frontend:latest@sha256:46c992da3e89c3dd327506efd3b7fbe9507bb63d7343d00fd45ce23f1e8a532b                                         0.0s
 => => sha256:d69d4d41cfe2ee680d6972795e2a1eb9e4dc4ec3b3c5e0797c9ab43bb3726fa7 4.14MB / 4.14MB                                                                             0.6s
 => => sha256:fe7fd9eb14e0149f43baa2cdb88269ea2f60bda9aa5ca788bb25702cbdee5e75 7.17MB / 7.17MB                                                                             1.3s
 => => extracting sha256:d69d4d41cfe2ee680d6972795e2a1eb9e4dc4ec3b3c5e0797c9ab43bb3726fa7                                                                                  0.1s
 => => extracting sha256:fe7fd9eb14e0149f43baa2cdb88269ea2f60bda9aa5ca788bb25702cbdee5e75                                                                                  0.1s
 => load build definition from railpack.json                                                                                                                               0.0s
 => => transferring dockerfile: 5.00kB                                                                                                                                     0.0s
 => docker-image://ghcr.io/railwayapp/railpack-runtime:latest                                                                                                              1.7s
 => => resolve ghcr.io/railwayapp/railpack-runtime:latest                                                                                                                  1.6s
 => docker-image://ghcr.io/railwayapp/railpack-builder:latest                                                                                                             60.3s
 => => resolve ghcr.io/railwayapp/railpack-builder:latest                                                                                                                  1.7s
 => => sha256:4c6d6396838b0bab96e1d48a7003807271da9c7535806ba7f3e942ea64ebfc41 119B / 119B                                                                                 0.3s
 => => sha256:ca6ef7bca8ed2706fbc275417397f4b002343f301f926491a31606b6ecc96480 10.02MB / 10.02MB                                                                           1.1s
 => => sha256:59ec0b6dd4e2e8d50eb376a027f451987a1a77cbff84baba2fe959f1ef0cf132 224.47MB / 224.47MB                                                                        55.6s
 => => sha256:255774e0027b72d2327719e78dbad5ad8c9cf446d055e45be7fc149418470bae 64.40MB / 64.40MB                                                                           5.2s
 => => sha256:091eb8249475f42de217265c501e0186f0a3ea7490ef7f51458c30db91fb3cac 24.01MB / 24.01MB                                                                           6.0s
 => => sha256:7cd785773db44407e20a679ce5439222e505475eed5b99f1910eb2cda51729ab 48.47MB / 48.47MB                                                                           4.4s
 => => extracting sha256:7cd785773db44407e20a679ce5439222e505475eed5b99f1910eb2cda51729ab                                                                                  0.6s
 => => extracting sha256:091eb8249475f42de217265c501e0186f0a3ea7490ef7f51458c30db91fb3cac                                                                                  0.2s
 => => extracting sha256:255774e0027b72d2327719e78dbad5ad8c9cf446d055e45be7fc149418470bae                                                                                  0.8s
 => => extracting sha256:59ec0b6dd4e2e8d50eb376a027f451987a1a77cbff84baba2fe959f1ef0cf132                                                                                  2.7s
 => => extracting sha256:ca6ef7bca8ed2706fbc275417397f4b002343f301f926491a31606b6ecc96480                                                                                  0.1s
 => => extracting sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1                                                                                  0.0s
 => => extracting sha256:4c6d6396838b0bab96e1d48a7003807271da9c7535806ba7f3e942ea64ebfc41                                                                                  0.0s
 => loading .                                                                                                                                                              0.1s
 => => transferring context: 488.88kB                                                                                                                                      0.0s
 => ERROR mise install-into caddy@2.10.0 /railpack/caddy                                                                                                                   0.0s
 => mkdir /etc/mise                                                                                                                                                        2.5s
------
 > mise install-into caddy@2.10.0 /railpack/caddy:
------
ERROR: failed to solve: secret BUILD_COMMIT: not found
error: Recipe `build_javascript` failed on line 116 with exit code 1

Running it again without changing anything and I get the same thing you shared

╭────────────────╮
│ Railpack 0.2.1 │
╰────────────────╯

  ⚠ Failed to read config file `railpack.json`
  Use the following schema to validate your config file: https://schema.railpack.com

  ↳ Detected Node
  ↳ Using pnpm package manager

  Packages
  ──────────
  node  │  22.17.0  │  package.json > engines > node (^22.17.0)
  pnpm  │  9.15.9   │  railpack default (9)

  Steps
  ──────────
  ▸ install
    $ pnpm install --frozen-lockfile --prefer-offline

  ▸ build
    $ pnpm run build

  Deploy
  ──────────
    $ caddy run --config /Caddyfile --adapter caddyfile 2>&1

docker buildx build web --build-arg BUILDKIT_SYNTAX=ghcr.io/railwayapp/railpack-frontend:latest -f web/railpack.json -t python-starter-template-javascript:96a2152b55626c32d783521bb8298b063af8b048-dirty --platform linux/amd64 --cache-to type=inline --cache-from ghcr.io/iloveitaly/python-starter-template-javascript:latest --label org.opencontainers.image.description="Used for building javascript assets, not for deployment"
/etc/zshenv:4: SSH_CONNECTION: parameter not set
[+] Building 1.1s (9/20)                                                                                                                                        docker:orbstack
 => [internal] load build definition from railpack.json                                                                                                                    0.0s
 => => transferring dockerfile: 3.26kB                                                                                                                                     0.0s
 => resolve image config for docker-image://ghcr.io/railwayapp/railpack-frontend:latest                                                                                    0.7s
 => CACHED docker-image://ghcr.io/railwayapp/railpack-frontend:latest@sha256:46c992da3e89c3dd327506efd3b7fbe9507bb63d7343d00fd45ce23f1e8a532b                              0.1s
 => => resolve ghcr.io/railwayapp/railpack-frontend:latest@sha256:46c992da3e89c3dd327506efd3b7fbe9507bb63d7343d00fd45ce23f1e8a532b                                         0.1s
 => load build definition from railpack.json                                                                                                                               0.0s
 => => transferring dockerfile: 3.26kB                                                                                                                                     0.0s
 => CANCELED docker-image://ghcr.io/railwayapp/railpack-builder:latest                                                                                                     0.1s
 => => resolve ghcr.io/railwayapp/railpack-builder:latest                                                                                                                  0.1s
 => ERROR copy /railpack/caddy                                                                                                                                             0.1s
 => ERROR copy /Caddyfile                                                                                                                                                  0.1s
 => CANCELED docker-image://ghcr.io/railwayapp/railpack-runtime:latest                                                                                                     0.1s
 => => resolve ghcr.io/railwayapp/railpack-runtime:latest                                                                                                                  0.1s
 => loading .                                                                                                                                                              0.0s
------
 > copy /railpack/caddy:
------
------
 > copy /Caddyfile:
------
ERROR: failed to solve: lstat /railpack/caddy: no such file or directory
error: Recipe `build_javascript` failed on line 116 with exit code 1

Removing the generated web/railpack* files returns me to the first error.

The first error is because of failed to solve: secret BUILD_COMMIT: not found. This happens when a secret (environment variable) is passed in to the railpack prepare command and appears in the plan (and in the --plan-out file) but is not passed in to the docker buildx build. Buildkit is attempting to load that secret but it doesn't exist.

The next run is picking up the generated web/railpack.json file as a config as code file and that is causing issues. Why... I'm not quite sure. I'll need to investigate that later. The build plan that Railpack sends to the Buildkit frontend and builds with is not the same as the config that you can use to modify the build (the plan is lower level and more granular which gives more control). I suspect that a difference here is causing issues (likely somewhere around here). I suggest changing the --plan-out argument to write to a railpack-plan.json file instead. This file is not intended to be hand modified and I wish there was a better way of passing this data into the Buildkit frontend (maybe there is).

For the secrets, they need to be passed to Docker/Buildkit (like this). It is a bit tedious, but using the proper secrets mechanism in Buildkit is much more secure than and the values never show up in the final image or written anywhere to disk, which is why they need to be passed twice. Once to railpack prepare so it knows what secrets exist, and then to docker buildx to actually use them during the build.

Let me know if anything isn't clear or if you have any other questions. I'm not ruling out a Railpack issue here, but there are several Node SPA examples that build in CI so I think the problem here is more nuanced.

[bipulmgr]

Hi @iloveitaly, @coffee-cup

I’m also encountering the same issue where the Caddyfile is not being auto-generated when using railpack to build a Node SPA project. This leads to the following error during the build process:

Is there any better way to force clear the Caddyfile as it is creating major issue on our application demo for client?
Can you guys help me out on it?

[iloveitaly]

@bipulmgr do you have an example project structure (package.json, etc) that I could take a look at? I am doing to start debugging this soon and may be able to help you as well!

[bipulmgr]

Hi @iloveitaly,

I hope you're doing well.

We're currently using this repo sursatech/employee-info-app as a reference. In our system, when importing this or other Node.js applications, we utilize Railpack to extract key metadata like the install command, start command, mise packages, apt packages, and port. This allows us to automate background execution and provide instant project previews.

However, we noticed that for many imported Node.js applications—including ones we've forked from public repos for testing—the generated startCommand often defaults to:

caddy run --config /Caddyfile --adapter caddyfile 2>&1

We're wondering if this is expected behavior for most SPA-based projects, or if there's a better way to detect and handle custom start commands in such cases.

Also, is there an official community chat (like Discord or similar) where discussions and support around these tools happen? We'd love to connect.

Thanks in advance!

[bipulmgr]

@iloveitaly is there any update or suggestion for above

[coffee-cup]

Hi @bipulmgr,

This is an interesting use case of Railpack and I'd love to learn more about it.

What I suspect you are running into is Caddy being disabled if a custom start command is detected (source).

Automatically building a static site as an SPA and deploying with Caddy is useful if that is the intended goal, but if it isn't then it can be frustrating. Its a fine balance on how to detect this and Railpack airs on the side of "if a user has specified a custom start command, then assume thats what they want to run when the app is deployed". Since you are specifying a custom start command, then it is not detecting it as an SPA. You can prevent this behaviour by removing the custom start command or adding a RAILPACK_SPA_OUTPUT_DIR variable (set to the static site directory to serve).

Very open to suggestions here if you would like to configure Railpack in a different way. Also, if this is does not fix your issue, please let me know since it could very well be a bug. I'm just suspecting that this is what it is.

[bipulmgr]

Hi @coffee-cup,
Thanks for reply.

Just to add more context here is the package.json

{
  "name": "employee-info-app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@testing-library/dom": "^10.4.0",
    "@testing-library/jest-dom": "^6.6.3",
    "@testing-library/react": "^16.3.0",
    "@testing-library/user-event": "^13.5.0",
    "@types/jest": "^27.5.2",
    "@types/node": "^16.18.126",
    "@types/react": "^19.1.8",
    "@types/react-dom": "^19.1.6",
    "react": "^19.1.0",
    "react-dom": "^19.1.0",
    "react-scripts": "5.0.1",
    "typescript": "^4.9.5",
    "web-vitals": "^2.1.4"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "devDependencies": {
    "autoprefixer": "^10.4.21",
    "postcss": "^8.5.6",
    "tailwindcss": "^3.4.17"
  }
}

which already includes a "start" script (react-scripts start) along with standard dependencies like React and TailwindCSS.

From what I understand, Railpack analyzes package.json to generate startCommand, installCommand, aptPackages, and misePackages. Given that, shouldn't Railpack either extract the defined start script or, if missing, default to something like npm run start based on the project’s nature?

Is this understanding correct?

[bipulmgr]

@coffee-cup

Also, were you able to check out the demo repo we provided sursatech/employee-info-app ?
Just wanted to confirm if anything might be missing or misconfigured on our side that could affect detection.

OR

maybe my understanding is off — would love your take on that.

[coffee-cup]

Your understanding of Railpack is correct, but it looks like (based on the second screenshot in this comment) you have a custom (non-railpack defined) start command. This tells Railpack that SPA mode should not be used because "the user knows what they are doing and using a separate start command". For example, this is important if you had a custom fastify or http-server that you wanted to use instead of Caddy.

This is where that happens in the code.

I checked out the employee-info-app and was successfully able to get it to deploy with zero configuration

but as soon as a custom start command is provided, SPA mode is no longer used (I realize the start command is incorrect in this screenshot, but it is the same result)

I'm not sure what platform you are deploying to, but ideally you want to completely omit the start command and use whatever railpack detects and provides by default.

If that is not possible, then I recommend setting the RAILPACK_SPA_OUTPUT_DIR=build environment variable as that forces SPA mode and will serve the build directory with Caddy.

[bipulmgr]

@coffee-cup
Thanks for the response.

Just to give more context on our use case:
We’re building an online code editor for developers, where each project is treated as a service. A service can be initialised in three ways:

1. As an empty project
2. Via GitHub import
3. Via file upload

Once a service is created, we deploy it inside a Docker container. For the container to run successfully, each service needs a build config that includes:

1. startCommand
2. installCommand
3. aptPackages
4. misePackages
5. port

When a project is imported or uploaded (via GitHub or ZIP), we use RAILPACK to analyze and extract the necessary metadata — especially the startCommand, installCommand, and package dependencies — to allow users to preview their project instantly, without any manual setup.

In some Node.js or Bun-based projects, Railpack returns caddy as the startCommand. Here’s a snippet for reference of the previously provided github repo:

     {
      "railpackVersion": "0.2.2",
      "plan": {
        "steps": [
          {
            "name": "packages:mise",
            "inputs": [
              {
                "image": "ghcr.io/railwayapp/railpack-builder:latest"
              }
            ],
            "commands": [
              {
                "path": "/mise/shims"
              },
              {
                "path": "/etc/mise/config.toml",
                "name": "mise.toml",
                "customName": "create mise config"
              },
              {
                "cmd": "sh -c 'mise trust -a \u0026\u0026 mise install'",
                "customName": "install mise packages: node"
              }
            ],
            "assets": {
              "mise.toml": "[tools]\n  [tools.node]\n    version = \"22.18.0\"\n"
            },
            "variables": {
              "MISE_CACHE_DIR": "/mise/cache",
              "MISE_CONFIG_DIR": "/mise",
              "MISE_DATA_DIR": "/mise",
              "MISE_INSTALLS_DIR": "/mise/installs",
              "MISE_NODE_VERIFY": "false",
              "MISE_SHIMS_DIR": "/mise/shims"
            }
          },
          {
            "name": "install",
            "inputs": [
              {
                "step": "packages:mise"
              }
            ],
            "commands": [
              {
                "path": "/app/node_modules/.bin"
              },
              {
                "src": "package.json",
                "dest": "package.json"
              },
              {
                "cmd": "npm install"
              }
            ],
            "variables": {
              "CI": "true",
              "NODE_ENV": "production",
              "NPM_CONFIG_FUND": "false",
              "NPM_CONFIG_PRODUCTION": "false",
              "NPM_CONFIG_UPDATE_NOTIFIER": "false"
            },
            "caches": [
              "npm-install"
            ]
          },
          {
            "name": "build",
            "inputs": [
              {
                "step": "install"
              }
            ],
            "commands": [
              {
                "src": ".",
                "dest": "."
              },
              {
                "cmd": "npm run build"
              }
            ],
            "secrets": [
              "*"
            ],
            "caches": [
              "node-modules"
            ]
          },
          {
            "name": "packages:caddy",
            "inputs": [
              {
                "image": "ghcr.io/railwayapp/railpack-builder:latest"
              }
            ],
            "commands": [
              {
                "cmd": "mise install-into caddy@2.10.0 /railpack/caddy"
              },
              {
                "path": "/railpack/caddy"
              },
              {
                "path": "/railpack/caddy/bin"
              }
            ]
          },
          {
            "name": "caddy",
            "inputs": [
              {
                "step": "packages:caddy"
              }
            ],
            "commands": [
              {
                "path": "/Caddyfile",
                "name": "Caddyfile"
              },
              {
                "cmd": "caddy fmt --overwrite /Caddyfile"
              }
            ],
            "secrets": [
              "*"
            ],
            "assets": {
              "Caddyfile": "# global options\n{\n\tadmin off\n\tpersist_config off\n\tauto_https off\n\n\tlog {\n\t\tformat json\n\t}\n\n\tservers {\n\t\ttrusted_proxies static private_ranges 100.0.0.0/8 # trust railway's proxy\n\t}\n}\n\n# site block, listens on the $PORT environment variable, automatically assigned by railway\n:{$PORT:80} {\n\tlog {\n\t\tformat json\n\t}\n\n\trespond /health 200\n\n\t# Security headers\n\theader {\n\t\t# Prevent some browsers from MIME-sniffing a response away from the declared Content-Type\n\t\tX-Content-Type-Options \"nosniff\"\n\t\t# Remove Server header\n\t\t-Server\n\t}\n\n\t# serve from the 'dist' folder (Vite builds into the 'dist' folder)\n\troot * /app/build\n\n\t# Handle static files\n\tfile_server {\n\t\thide .git\n\t\thide .env*\n\t}\n\n\t# Compression with more formats\n\tencode {\n\t\tgzip\n\t\tzstd\n\t}\n\n\t# Try files with HTML extension and handle SPA routing\n\ttry_files {path} {path}.html {path}/index.html /index.html\n}\n"
            }
          }
        ],
        "caches": {
          "node-modules": {
            "directory": "/app/node_modules/.cache",
            "type": "shared"
          },
          "npm-install": {
            "directory": "/root/.npm",
            "type": "shared"
          }
        },
        "deploy": {
          "base": {
            "image": "ghcr.io/railwayapp/railpack-runtime:latest"
          },
          "inputs": [
            {
              "step": "packages:caddy",
              "include": [
                "/railpack/caddy"
              ]
            },
            {
              "step": "caddy",
              "include": [
                "/Caddyfile"
              ]
            },
            {
              "step": "build",
              "include": [
                "build"
              ]
            }
          ],
          "startCommand": "caddy run --config /Caddyfile --adapter caddyfile 2\u003e\u00261",
          "variables": {
            "CI": "true",
            "NODE_ENV": "production",
            "NPM_CONFIG_FUND": "false",
            "NPM_CONFIG_PRODUCTION": "false",
            "NPM_CONFIG_UPDATE_NOTIFIER": "false"
          }
        }
      },
      "resolvedPackages": {
        "caddy": {
          "name": "caddy",
          "requestedVersion": "latest",
          "resolvedVersion": "2.10.0",
          "source": "railpack default"
        },
        "node": {
          "name": "node",
          "requestedVersion": "22",
          "resolvedVersion": "22.18.0",
          "source": "railpack default"
        }
      },
      "metadata": {
        "nodeIsSPA": "true",
        "nodePackageManager": "npm",
        "nodeRuntime": "cra",
        "nodeSPAFramework": "CRA",
        "providers": "node"
      },
      "detectedProviders": [
        "node"
      ],
      "logs": [
        {
          "Level": "info",
          "Msg": "Detected Node"
        },
        {
          "Level": "info",
          "Msg": "Using npm package manager"
        },
        {
          "Level": "info",
          "Msg": "Deploying as CRA static site"
        },
        {
          "Level": "info",
          "Msg": "Output directory: build"
        }
      ],
      "success": true
    }

This introduces a problem for us, because our runtime expects to execute the returned startCommand directly. However it return the startCommand as in the above json caddy run --config /Caddyfile --adapter caddyfile 2\u003e\u00261 due to which our application provides the issue related to caddy as in the below image.

Would it make sense in this case to override the startCommand or enforce RAILPACK_SPA_OUTPUT_DIR=build ourselves when we detect a static site or SPA? Let us know what’s the best approach here from Railpack’s perspective.

Appreciate the great work you’re doing with Railpack — it’s been very helpful in streamlining our service onboarding!

[bipulmgr]

@coffee-cup
Also, one quick question — is it possible to use Railpack to extract and deploy projects directly from Docker Hub images, or is that out of scope?

[iloveitaly]

@bipulmgr I have a couple things on my list to fix (#162) before I can dig into this, but it's high-pri for me since it's blocking a couple of my projects, so will respond back when I take a look! I should be able to answer your questions then.

Also, one quick question — is it possible to use Railpack to extract and deploy projects directly from Docker Hub images, or is that out of scope?

I'm not sure how railpack could be useful here—could you help me understand more?

i.e. railpack is for taking a project without a container and creating a container. If there's already a container, then railpack doesn't really help, right?