You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
For explanation about these steps, continue reading the next section.
74
+
Once deployed,[continue development](#user-content-continue-development) 🌱
75
+
76
+
For explanation about these steps, continue reading the[next section](#user-content-usage).
77
+
74
78
75
79
Usage
76
80
-----
@@ -138,6 +142,16 @@ Eventually, to share, collaborate, or simply back-up your code, [create an empty
138
142
Customization
139
143
-------------
140
144
145
+
###Procfile
146
+
147
+
Heroku apps declared what processes are launched for a successful deployment by way of the[`Procfile`](https://devcenter.heroku.com/articles/procfile). This buildpack's default process comes from[`heroku/static` buildpack](https://github.com/heroku/heroku-buildpack-static). (See: 🏙[Architecture](#user-content-architecture-)). The implicit`Procfile` to start the static web server is:
148
+
149
+
```
150
+
web: bin/boot
151
+
```
152
+
153
+
To customize an app's processes, commit a`Procfile` and deploy. Include`web: bin/boot` to launch the default web process, or you may replace the default web process. Additional[process types](https://devcenter.heroku.com/articles/procfile#declaring-process-types) may be added to run any number of dynos with whatever arbitrary commands you want, and scale each independently.
154
+
141
155
###Web server
142
156
143
157
The web server may be[configured via the static buildpack](https://github.com/heroku/heroku-buildpack-static#configuration).