From 6ae327fd8a1647681157358f476e139a0a027e73 Mon Sep 17 00:00:00 2001 From: Chris McCormick Date: Thu, 31 Aug 2023 14:13:05 +0800 Subject: [PATCH] Typo. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 188afe8..f019991 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ I kept finding myself wanting an Heroku/CloudFoundry-like way to deploy stuff on * For Go, it defines a separate `GOPATH` for each app. * For Node, it installs whatever is in `package.json` into `node_modules`. * For Java, it builds your app depending on either `pom.xml` or `build.gradle` file. - * For Clojure, it can use either `leiningen` or the Clojure CLI and a `eps.edn` file. + * For Clojure, it can use either `leiningen` or the Clojure CLI and a `deps.edn` file. * For Ruby, it does `bundle install` of your gems in an isolated folder. * It then looks at a [`Procfile`](docs/DESIGN.md#procfile-format) which is [documented here](docs/DESIGN.md#procfile-format) and starts the relevant workers using [uWSGI][uwsgi] as a generic process manager. * You can optionally also specify a `release` worker which is run once when the app is deployed.