NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #3296 by repository stars
Latest stable
v0.30.0
Last release 6 years ago
no release in 18 months
Ships unpredictably
gaps range from 1 weeks to 2.4 years
Most releases are documented
notes for 25 of 30 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
31 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
PCF Dev v0.30.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.30.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.30.0+PCF1.11.0-<OS>.zip
$ ./pcfdev-v0.30.0+PCF1.11.0-<OS>
Plugin successfully upgraded. Current version: 0.30.0. For more info run: cf dev help
$ cf dev help
This is a maintenance release that fixes another expired certificate.
We are working on a complete re-write of PCF Dev that includes support for BOSH and runs on native hypervisors. To try out the alpha release for macOS, check out the CF Dev Github repo.
Please note, a PCF 2.1 version of the alpha will be available shortly as well.
cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev destroy may prompt you for your password on linux (#190)Your coding agent can read these notes before it upgrades. Set up the MCP server →
PCF Dev v0.29.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.29.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.29.0+PCF1.11.0-<OS>.zip
$ ./pcfdev-v0.29.0+PCF1.11.0-<OS>
Plugin successfully upgraded. Current version: 0.29.0. For more info run: cf dev help
$ cf dev help
This is a maintenance release that fixes two bugs in v0.28.0.
We are working on a complete re-write of PCF Dev that includes support for BOSH and runs on native hypervisors. To try out the alpha release for macOS, follow these steps :
cf uninstall-plugin pcfdev .cf install-plugin <path to cfdev binary> -f.Please note, a PCF version of the alpha will be available shortly as well.
local.pcfdev.io. (#263)cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev destroy may prompt you for your password on linux (#190)PCF Dev v0.28.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.28.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.28.0+PCF1.11.0-<OS>.zip
$ ./pcfdev-v0.28.0+PCF1.11.0-<OS>
Plugin successfully upgraded. Current version: 0.28.0. For more info run: cf dev help
$ cf dev help
This is a maintenance release that fixes a bug in v0.27.0. We're working a new version of PCF Dev that includes major changes to how PCF Dev is deployed, as well as exciting new features. Stay tuned!
cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev destroy may prompt you for your password on linux (#190)PCF Dev v0.27.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.27.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.27.0+PCF1.11.0-<OS>.zip
$ ./pcfdev-v0.27.0+PCF1.11.0-<OS>
Plugin successfully upgraded. Current version: 0.27.0. For more info run: cf dev help
$ cf dev help
This is a maintenance release that brings the PCF Dev components up to the versions present in PCF 1.11.0. We're working a new version of PCF Dev that includes major changes to how PCF Dev is deployed, as well as exciting new features. Stay tuned!
cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev destroy may prompt you for your password on linux (#190)PCF Dev v0.26.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.26.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.26.0+PCF1.10.0-<OS>.zip
$ ./pcfdev-v0.26.0+PCF1.10.0-<OS>
Plugin successfully upgraded. Current version: 0.26.0. For more info run: cf dev help
$ cf dev help
This is an immediate follow-up release to v0.25.0. Please see the release notes for v0.25.0 for additional changes since v0.24.0.
cf dev start -r <registry> to prevent VM startupcf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev destroy may prompt you for your password on linux (#190)PCF Dev v0.25.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary distribution of PCF Dev may b
PCF Dev v0.25.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary distribution of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.25.0+PCF1.10.0-<OS>.zip
$ ./pcfdev-v0.25.0+PCF1.10.0-<OS>
Plugin successfully upgraded. Current version: 0.25.0. For more info run: cf dev help
$ cf dev help
vboxmanage storagectl pcfdev-v0.459.0 --name SATA --hostiocache on
cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev start -r <registry> will fail if multiple docker registries are specifiedcf dev destroy may prompt you for your password on linux (#190)PCF Dev v0.24.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.24.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.24.0+PCF1.9.0-<OS>.zip
$ ./pcfdev-v0.24.0+PCF1.9.0-<OS>
Plugin successfully upgraded. Current version: 0.24.0. For more info run: cf dev help
$ cf dev help
console.local.pcfdev.io to apps.local.pcfdev.io (#186)cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.PCF Dev v0.23.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.23.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.23.0+PCF1.9.0-<OS>.zip
$ ./pcfdev-v0.23.0+PCF1.9.0-<OS>
Plugin successfully upgraded. Current version: 0.23.0. For more info run: cf dev help
$ cf dev help
cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.PCF Dev v0.22.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.22.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.22.0+PCF1.8.2-<OS>.zip
$ ./pcfdev-v0.22.0+PCF1.8.2-<OS>
Plugin successfully upgraded. Current version: 0.22.0. For more info run: cf dev help
$ cf dev help
cf dev ssh now allows you to quickly access the VM over SSH. ssh vcap@local.pcfdev.io now requires a private key in ~/.pcfdev/vms/key.pem. NOTE: This access is provided for debugging purposes only. PCF Dev contains PCF components that may not be redistributed or reverse engineered.cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust requires user password entry on Mac OS X.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.PCF Dev v0.21.0 is an open beta release that is publicly available on the Pivotal Network . Feedback for the proprietary version of PCF Dev may be lef
PCF Dev v0.21.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.21.0+PCF1.8.2-<OS>.zip
$ ./pcfdev-v0.21.0+PCF1.8.2-<OS>
Plugin successfully upgraded. Current version: 0.21.0. For more info run: cf dev help
$ cf dev help
/etc/resolv.conf in the VM on startup is now fixed.cf dev commands no longer appear with recent cf CLI versions. (#145)cf dev trust is no longer set by UAA. Unfortunately, this header is "sticky." See Known Issues for a workaround.PIVNET_TOKEN env var for non-interactive downloads.cf dev trust as a non-administrative Windows user now works, and it only affects that user's keychain. (#144)-i and -d flags. Note that the specified domain will always resolve to the specified IP inside of the PCF Dev VM. More documentation on these flags is forthcoming.cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust requires user password entry on Mac OS X.cf dev trust accesses the system keychain in Mac OS X, which causes certain versions of Mac OS X to crash. This has only been observed in 10.10.3 and 10.10.5 and appears to be rare.cf dev trust in 0.20.0 due to HSTS headers that were added to UAA. These headers have been removed in 0.21.0, but unfortunately the headers are "sticky," and you may still be unable to access Apps Manager without cf dev trust after upgrading. To work around this, navigate to chrome://net-internals/#hsts and delete the uaa.local.pcfdev.io (or uaa.local2.pcfdev.io) domain. For instructions in other browsers, see here.ip:port format to the -r flag may not work. (#80)> PCF Dev v0.20.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev).
PCF Dev v0.20.0 is an open beta release that is publicly available on the Pivotal Network. Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.20.0+PCF1.8.0-<OS>.zip
$ ./pcfdev-v0.20.0+PCF1.8.0-<OS>
Plugin successfully upgraded. Current version: 0.20.0. For more info run: cf dev help
$ cf dev help
cf dev trust command removes all browser SSL warnings and allows you to run cf login without --skip-ssl-validation. Running cf dev untrust will revert this behavior. Running cf dev start -k will run cf dev trust automatically after starting the VM. The cf dev trust command inserts a CA certificate into your OS certificate store. For security reasons, the CA private key is never written to disk and is deleted from memory before the certificate is inserted. See "Known Issues" for limitations.cf dev target command targets PCF Dev using the cf CLI and logs you in as the "user" user. Running cf dev start -t will run cf dev target automatically after starting the VM.-r flag to the cf dev start command allows you to specify insecure Docker registries that the platform will allow Docker images to be pushed from.cf dev trust does not prevent SSL warnings in the Firefox web browser and in various Linux web browsers.cf dev trust requires user password entry on Mac OS X.> PCF Dev v0.19.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev).
PCF Dev v0.19.0 is an open beta release that is publicly available on the Pivotal Network. Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.19.0+PCF1.7.12-<OS>.zip
$ ./pcfdev-v0.19.0+PCF1.7.12-<OS>
Plugin successfully upgraded. Current version: 0.19.0. For more info run: cf dev help
$ cf dev help
cf dev import command now allows OVAs to be imported in fresh installation of PCF Dev.cf dev help text clarifies that the MySQL service is always enabled. (#108)200 status code responses from PivNet. This may address #101, but we were unable to replicate the issue.cf create-service, try creating services one at a time, making sure each service is created successfully before creating the next. For example, the sample Traveler app deploy script will occasionally fail because it attempts to create a service registry and a circuit breaker dashboard simultaneously.-s flag.> PCF Dev v0.18.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev).
PCF Dev v0.18.0 is an open beta release that is publicly available on the Pivotal Network. Feedback for the proprietary version of PCF Dev may be left in the Github issues for this repository.
$ unzip pcfdev-v0.18.0+PCF1.7.0-<OS>.zip
$ ./pcfdev-v0.18.0+PCF1.7.0-<OS>
Plugin successfully upgraded. Current version: 0.18.0. For more info run: cf dev help
$ cf dev help
Spring Cloud Services is now available in the commercial version of PCF Dev. You must have 6 GB of free memory to run PCF Dev with Spring Cloud Services, and you must specify that it should start when you start PCF Dev.
$ cf dev start -s scs
See Known Issues below for caveats.
The -s flag to cf dev start may be used to customize what services are started. By default, MySQL, Redis, and RabbitMQ are started. MySQL is used internally by the VM and cannot be disabled. Run cf dev help for more info.
The PCF Dev cf CLI plugin version and OVA version are available by running cf dev version. (#76)
Apps Manager services now have corresponding tile images and relevant descriptions.
Certain invalid VM states are now detectable. cf dev status is more reliable in this release.
Invalid VM states that are recoverable can be recovered with cf dev stop followed by cf dev start.
The vcap user in the VM can now use the cf CLI.
The EULA is now scrollable and disappears from your terminal after accepting it.
DNS resolution inside the PCF Dev VM is completely re-vamped. External resolution is now performed on the host. This may address issues where PCF Dev fails to start. (#79, #93, #102)
HTTP proxy support is improved. (#100)
Local network detection and VM IP address collision prevention is improved (#88).
The SSL certificate for PCF Dev matches the system domain in all cases.
The corresponding PCF Dev OVA (pcfdev-v0.219.0.ova for this release) may be imported from the local filesystem with cf dev import /path/to/pcfdev-v0.219.0.ova
Component versions are still matched to PCF 1.7.0. PCF Dev v0.19.0 will include PCF 1.7.12 components and will be available soon.
Experimental support for AWS continues to be discontinued. We found that many users had trouble configuring PCF Dev on AWS in a secure and usable manner. AWS support will return soon, and will be available from the AWS Marketplace. If you are a Pivotal employee, please contact us on Slack for continued AWS support.
cf create-service, try creating services one at a time, making sure each service is created successfully before creating the next. For example, the sample Traveler app deploy script will occasionally fail because it attempts to create a service registry and a circuit breaker dashboard simultaneously.-s flag.> PCF Dev v0.17.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev).
PCF Dev v0.17.0 is an open beta release that is publicly available on the Pivotal Network. Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.
The plugin may be installed or upgraded by running it directly (as well as via cf install-plugin). (#76, #77)
$ unzip pcfdev-v0.17.0+PCF1.7.0-<OS>.zip
$ ./pcfdev-v0.17.0+PCF1.7.0-<OS>
Plugin successfully upgraded, run: cf dev help
$ cf dev help
A corresponding PCF version is now included in the PCF Dev version for more clarity.
Whitespace in proxy variables is now ignored. The delimitation of no_proxy may now include spaces. (#82)
Apps Manager is now included with PCF Dev. Navigate to http://local.pcfdev.io in your web browser to check it out. (Your browser may warn you that the SSL certificate is self-signed.) (#12, #60)
A default non-administrative user is now included: Email: user / Password: pass
Application security groups are now open to private IP ranges by default. You may remove the all security group to revert to the previous behavior of only allowing access to public IP ranges. (#80, #81)
HTTP/HTTPS proxy domains that resolve to multiple IP addresses are now supported. (#85)
Custom OVAs may be used with the CLI plugin via the undocumented -o flag: cf dev start -o custom.ova. This will eventually replace Vagrant for booting OSS builds of PCF Dev. The source code for the CLI plugin will be released soon. (#84)
PCF Dev VMs that fail to start may always be destroyed with cf dev destroy. Running cf dev status will report these VMs as "Invalid" and instruct you to destroy them. (#78, #79)
The entire PCF Dev VM now lives in the ~/.pcfdev directory.
Local network detection is significantly improved.
Component versions are still matched to PCF 1.7.0.
Experimental support for AWS has been discontinued temporarily. We found that many users had trouble configuring PCF Dev on AWS in a secure and usable manner. AWS support will return soon, and will be available from the AWS Marketplace. If you are a Pivotal employee, please contact us on Slack for continued AWS support.
> PCF Dev v0.16.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev).
PCF Dev v0.16.0 is an open beta release that is publicly available on the Pivotal Network. Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.
PCF Dev is managed by a cf CLI plugin instead of Vagrant (for local VMs). Read the documentation for more info.
$ unzip pcfdev-v0.16.0-<OS>.zip
$ cf install-plugin pcfdev-v0.16.0-<OS>
$ cf help dev
PCF Dev is fully supported on Mac OS X, Windows, and Linux.
Experimental support for PCF Dev on AWS is available through Vagrant. Follow the instructions in the INSTALL.md file in the PCF Dev AWS kit available from PivNet (pcfdev-aws-v0.16.0.zip).
Boot time is reduced -- PCF Dev 0.16.0 boots 5x faster than 0.15.0.
Syslog drains are now supported.
PCF Dev analyzes your system memory usage and warns when starting the VM might cause your system to slow down.
PCF Dev analyzes your local networking configuration to start on a subnet that doesn't conflict with other VMs or devices.
Enterprise HTTP/HTTPS proxies may be set to domains as well as IP addresses.
Component versions are still matched to PCF 1.7.
cf dev start or cf dev destroy, please open the Virtualbox UI and manually delete the PCF Dev VM. In the next release, cf dev destroy will always work.> PCF Dev v0.15.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev)!
PCF Dev v0.15.0 is an open beta release that is publicly available on the Pivotal Network! Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.
> PCF Dev v0.14.0 is an open beta release that is publicly available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev)!
PCF Dev v0.14.0 is an open beta release that is publicly available on the Pivotal Network! Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.
> PCF Dev v0.13.0 is now in open beta and is publically available on the [Pivotal Network](https://network.pivotal.io/products/pcfdev)!
PCF Dev v0.13.0 is now in open beta and is publically available on the Pivotal Network! Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.
local.pcfdev.io)cf env <app> on an app with a bound service for connection detailsHTTP_PROXY and HTTPS_PROXY (uppercase or lowercase) at vagrant upvagrant up (or start-osx / start-windows.ps1)
HTTP_PROXY / HTTPS_PROXY (uppercase or lowercase)NO_PROXY can be set during vagrant up to exclude addresses from proxycf push <app> -b <buildpack-repo> are downloaded via proxycf pushvagrant suspend / vagrant resume functionalitycf service my-mysql-service)cf push <app> -m 256M to reduce your VM footprintNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The AWS provider does not currently work properly due to I/O throughput issues and has been deprecated.
512mb and 1gb plans are available for the p-mysql service brokerVagrantfilecf ssh to an app container no longer requires disabling host key checking (-k option)Looking for a base distribution of MicroPCF without service brokers? Download here.
First pre-release version of the official "MicroPCF" distro of MicroPCF.
First pre-release version of the official "MicroPCF" distro of MicroPCF.
In addition to the standard Cloud Foundry components, the MicroPCF distro now includes the Redis service broker. This allows Redis instances to be created and bound to apps running on MicroPCF. More information can be found on Redis for Pivotal Cloud Foundry.
cf utility to v6.15.0vagrant up waits for all buildpacks to be initialized
Minor release to allow app-to-app communication via the router.
Minor release to allow app-to-app communication via the router.
app.local.micropcf.ioFirst stable pre-release version of the base distro for MicroPCF.
First stable pre-release version of the base distro for MicroPCF.
This does not include services planned for the official MicroPCF distro (i.e., Redis, RabbitMQ, MySQL)
vagrant halt followed by vagrant up provides working cluster when vagrant up completes
vagrant ssh no longer supportedcf app <app> work as expectedxip.io DNS resolution is often flakyOffline (cached) buildpacks are pre-installed instead of online buildpacks
vagrant up waits for cluster to warm up
vagrant up workmicropcf-org / micropcf-space as default organization & spacecf and rtr commands to microPCF VMcf create-org functions as expectedPasses CF Acceptance Tests (CATS) appropriate for microPCF.
cf create-org fails with 501, error code: 20005, message: The UAA endpoint needed is disabled
cf create-org fails with 501, error code: 20005, message: The UAA endpoint needed is disabledNothing published for this version
One column per quarter.