v0.20.0

This release provides support for cflinuxfs3. This is a final maintenance release, and will likely be the last release of CF Local in its current state. Future versions of CF Local may look like a set of extensions for Cloud Foundry on top of the Cloud Native Buildpacks pack CLI, which covers most of the functionality of CF Local.

Special thanks to @jghiloni, who ported CF Local to cflinuxfs3 for this release!

Release Notes

• Switch from cflinuxfs2 to cflinuxfs3.

Known Differences from CF

• No instance identity credentials
• No support for adding custom CAs to the system CA store

Known Issues

• Writes UNIX line endings on Windows in some cases
• Some file paths may require UNIX path separators (/) on Windows

v0.19.0

For release v0.19.0, this repository has moved to the cloudfoundry-incubator Github org.

This release includes a complete refactoring of CF Local and forge to use packs. Packs are buildpack builder images that provide a simple, generic, image-based interface for using buildpacks with a variety of tools that support Docker images.

Release Notes

• Complete support for HTTP/HTTPS proxies on all platforms (#14)
  Proxy environment variables (such as $http_proxy) that are set in your shell are now propagated into local app containers that are running in Docker.
  Note: To prevent local proxy settings from applying to app containers running in remote Docker servers, this behavior is disabled if $DOCKER_HOST is set to a non-default value. You may override this behavior by setting $CFL_USE_PROXY to true or false.
• New -t flag: cf local run myapp -t
  This new flag to cf local run starts an interactive terminal in the app's environment.

$ cf local run my-rails-app -t -p 8080
Running my-rails-app on port 8080...
vcap@my-rails-app:~$ ls
app	config.ru     lib	    package.json  README.md  vendor
bin	Gemfile       log	    public	  test	     yarn.lock
config	Gemfile.lock  node_modules  Rakefile	  tmp
vcap@my-rails-app:~$ ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
vcap         1  3.6  2.9 892720 59660 ?        Ssl  08:33   0:01 puma 3.8.2 [app]
vcap         9  0.0  0.1  62536  3836 pts/0    Ss   08:33   0:00 bash
vcap        54  0.0  0.1  59928  2676 pts/0    R+   08:33   0:00 ps aux
vcap@my-rails-app:~$ rails c
Loading production environment (Rails 5.1.0.beta1)
irb(main):001:0>

• Significant performance enhancements
  This is due to the use of pre-built packs images as well as more aggressive caching introduced in the most recent Cloud Foundry buildpacks.
• Simplified options for local volume mounting in the cf local stage and cf local run commands
  There is now a single local volume mounting option available via cf local run -d. It always uses the contents of the local directory and uses rsync to copy the files into the app root before the app starts. If you'd like to retrieve a staged app root, it must be manually extracted out of the droplet tarball. Let me know if a cf local extract command would be useful for this purpose.
• Fixed an SSL validation bug when communicating with Cloud Controller. (#18)
• Fixed a (pre-release) bug with cf local run -t. (#20)
• Compiled with Go 1.10 to prevent some crashes on Windows. (#15)
• Upgraded to Diego 1.32.0.

Compiled with: Go 1.10 on macOS 10.13.2

Roadmap

• Performance enhancements that will use Docker image layer rebasing to significantly reduce staging time in cases where no app dependencies have changed
• cf local develop, pending buildpack features
• Local services marketplace

Known Differences from CF

• No instance identity credentials
• No support for adding custom CAs to the system CA store

Known Issues

• Writes UNIX line endings on Windows in some cases
• Some file paths may require UNIX path separators (/) on Windows

v0.18.0

This is the first release as an official incubating Cloud Foundry project.
This repository will move to the cloudfoundry-incubator Github org in the near future.

Release Notes

• Upgrade to Diego v1.29.1
• Set DATABASE_URL during staging and launch
• Use forge

Known Differences from CF

• No instance identity credentials
• No support for adding custom CAs to the system CA store

Known Issues

• Writes UNIX line endings on Windows in some cases
• Some file paths require UNIX path separators (/) on Windows

v0.17.0

Release Notes

• Added support for running the buildpack detection process using custom buildpacks (-e).

Known Issues

• Writes UNIX line endings on Windows
• Does not set the DATABASE_URL environment variable
• Buildpack file paths (and potentially other file paths) require UNIX path separators (/) on Windows

v0.16.0

Release Notes

• Added support for staging with buildpacks specified as local paths to zip files.
  • When specifying multiple buildpacks, any combination of buildpack sources (local path to zip, URL to zip, git URL) is valid.
  • See note below about Windows.

Known Issues

• Writes UNIX line endings on Windows
• Does not set the DATABASE_URL environment variable
• Buildpack file paths (and potentially other file paths) require UNIX path separators (/) on Windows

v0.15.0

Release Notes

• Added multi-buildpack support
  • Use cf local stage <name> -b ... -b ... for the CLI
  • Use buildpacks field in place of buildpack field for local.yml
• Upgraded to Diego 1.26.1

Known Issues

• Writes UNIX line endings on Windows
• Does not set the DATABASE_URL environment variable

v0.14.0

Release Notes

• Greatly improved stability of SSH tunnels used for service forwarding. Tunnels will now automatically reestablish even after long network outages.
• Added support for specifying a buildpack in local.yml using the buildpack field.
• Distribution archives are now GPG-signed

Known Issues

• Writes UNIX line endings on Windows
• Does not set the DATABASE_URL environment variable

v0.13.0

Release Notes

• Added support for disk and memory limits. Only memory limits in launch containers are enforced.
• Added support for four different types of volume mounts (run, run+rsync, stage, stage+rsync).
• Added support for automatically restarting the launch container when app files are modified (-w).
• Fixed service forwarding for certain services that use JSON numbers for ports (ex. p-mysql).

Known Issues

• Writes UNIX line endings on Windows

v0.12.0

Release Notes

• Fix staging when one or more buildpacks is in a pre-published release state.
• Please upgrade to this version ASAP, as both v0.10.0 and v0.11.0 will fail to stage droplets at a certain point during the buildpack release process.

Known Issues

• Writes UNIX line endings on Windows

v0.11.0

Release Notes

• JAR, WAR, and ZIP files can now be staged with cf local stage myapp -p ./app.jar

Known Issues

• Writes UNIX line endings on Windows