pull/319/head
Chris McCormick 2023-08-31 14:13:05 +08:00
rodzic 6dd0de4056
commit 6ae327fd8a
1 zmienionych plików z 1 dodań i 1 usunięć

Wyświetl plik

@ -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 Go, it defines a separate `GOPATH` for each app.
* For Node, it installs whatever is in `package.json` into `node_modules`. * 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 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. * 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. * 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. * You can optionally also specify a `release` worker which is run once when the app is deployed.