Frequently Asked Questions
$ cf api api.dev.cfdev.sh Setting api endpoint to api.dev.cfdev.sh... FAILED Invalid SSL Cert for api.dev.cfdev.sh TIP: Use 'cf api --skip-ssl-validation' to continue with an insecure API endpoint
PCF Dev comes with a self-signed SSL certificate for its API. The self-signed SSL certificate causes an
Invalid SSL Cert error when using the cf CLI. To avoid the error, use the
PCF Dev provides a special hostname for addressing the host from inside of application containers.
If the PCF Dev system domain is
dev.cfdev.sh, then the host will be routable at
Services running on the host must be listening on all network interfaces (not just
localhost) for apps to access them.
localhost inside of app containers will not refer to your workstation.
By default, PCF Dev allocates 8GB of memory to run.
To change the allocated memory, run the following command, replacing
NEW-ALLOCATED-MEMORY with the amount of memory you want to allocate in megabytes:
cf dev start -m NEW-ALLOCATED-MEMORY
By default, PCF Dev tries to use 4 cores. To change this setting, run the following command, replacing
DESIRED-NUMBER-OF-CORES with the number of processor cores PCF Dev should use:
cf dev start -c DESIRED-NUMBER-OF-CORES
Unlike PCF, PCF Dev allows applications to access all private address ranges without the need for additional ASGs.
This is because PCF Dev is considered a trusted, local environment.
You can remove the
all_pcfdev security group:
$ cf unbind-running-security-group all_pcfdev Unbinding security group all_pcfdev from defaults for running as admin OK TIP: Changes will not apply to existing running applications until they are restarted. $ cf unbind-staging-security-group all_pcfdev Unbinding security group all_pcfdev from defaults for staging as admin OK TIP: Changes will not apply to existing running applications until they are restarted.