Change absolute to relative file references (#4799)

With this change, the standalone project build uses relative paths instead of absolute paths starting from the root project. With these relative paths, the standalone project can be built as sub-project of different root projects.

Co-authored-by: gbildh <>
1 file changed
tree: cdf4764be63b59b11036a6873bef7be6fd66684f
  1. .asf.yaml
  2. .gitattributes
  3. .github/
  4. .gitignore
  5. .pydevproject
  6. .scalafmt.conf
  7. .travis.yml
  10. CREDITS.txt
  11. Jenkinsfile
  12. LICENSE.txt
  13. NOTICE.txt
  15. ansible/
  16. bin/
  17. build.gradle
  18. common/
  19. core/
  20. docs/
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. licenses/
  25. settings.gradle
  26. tests/
  27. tools/


Build Status License Join Slack codecov Twitter

OpenWhisk is a cloud-first distributed event-based programming service. It provides a programming model to upload event handlers to a cloud service, and register the handlers to respond to various events. Learn more at

Quick Start

The easiest way to start using OpenWhisk is to get Docker installed on Mac, Windows or Linux. The Docker website has detailed instructions on getting the tools installed. This does not give you a production deployment but gives you enough of the pieces to start writing functions and seeing them run.

git clone
cd openwhisk-devtools/docker-compose
make quick-start

For more detailed instructions or if you encounter problems see the OpenWhisk-dev tools project.

Kubernetes Setup

Another path to quickly starting to use OpenWhisk is to install it on a Kubernetes cluster. On a Mac, you can use the Kubernetes support built into Docker 18.06 (or higher). You can also deploy OpenWhisk on Minikube, on a managed Kubernetes cluster provisioned from a public cloud provider, or on a Kubernetes cluster you manage yourself. To get started,

git clone

Then follow the instructions in the OpenWhisk on Kubernetes

Native development

Docker must be natively installed in order to build and deploy OpenWhisk. If you plan to make contributions to OpenWhisk, we recommend either a Mac or Ubuntu environment.

Learn concepts and commands

Browse the documentation to learn more. Here are some topics you may be interested in:

Repository Structure

The OpenWhisk system is built from a number of components. The picture below groups the components by their GitHub repos. Please open issues for a component against the appropriate repo (if in doubt just open against the main openwhisk repo).

component/repo mapping


Report bugs, ask questions and request features here on GitHub.


You can also join the OpenWhisk Team on Slack and chat with developers. To get access to our public slack team, request an invite