forked from cloudfoundry/docs-cf-admin
-
Notifications
You must be signed in to change notification settings - Fork 0
/
buildpacks.html.md.erb
65 lines (44 loc) · 2.31 KB
/
buildpacks.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
---
title: Adding Buildpacks to Cloud Foundry
---
If your application uses a language or framework that Cloud Foundry system
buildpacks do not support, you can [write your own](../buildpacks/custom.html) buildpack, customize an
existing buildpack, or use a [Cloud Foundry Community Buildpack][b] or a [Heroku
Third-Party Buildpack][c].
You can add the new buildpack to Cloud Foundry, making it available alongside
the system buildpacks.
[b]: https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Buildpacks
[c]: https://devcenter.heroku.com/articles/third-party-buildpacks
## <a id='commands'></a>The cf Admin-Only Buildpack Commands ##
<p class="note"><strong>Note</strong>: You must be an administrator for your Cloud Foundry org to run the commands discussed in this section.</p>
To add a buildpack, run:
~~~
cf create-buildpack BUILDPACK PATH POSITION [--enable|--disable]
~~~
The arguments to `cf create-buildpack` do the following:
* **buildpack** tells cf what you want to call the buildpack.
* **path** tells cf where to find the buildpack.
The path can point to a zip file, the URL of a zip file, or a local directory.
* **position** tells cf where to place the buildpack in the detection
priority list. See [Buildpack Detection](../buildpacks/detection.html).
* **enable or disable** tells cf whether to allow apps to be pushed
with the buildpack.
This argument is optional, and defaults to enable.
While a buildpack is disabled, app developers cannot push apps using that buildpack.
You can also update and delete buildpacks. For more information, run:
`cf update-buildpack -h`
`cf delete-buildpack -h`
## <a id='confirm'></a> Confirming that a Buildpack was Added ##
To confirm that you have successfully added a buildpack, view the available
buildpacks by running `cf buildpacks`.
The example below shows the `cf buildpacks` output after the administrator added
a python buildpack.
<pre class=terminal>
$ cf buildpacks
Getting buildpacks...
buildpack position enabled locked filename
ruby_buildpack 1 true false buildpack_ruby_v46-245-g2fc4ad8.zip
nodejs_buildpack 2 true false buildpack_nodejs_v8-177-g2b0a5cf.zip
java_buildpack 3 true false buildpack_java_v2.1.zip
python_buildpack 4 true false buildpack_python_v2.7.6.zip
</pre>