tag | fd12b7ac0330a43befaef0d2506a75f2aa1abd60 | |
---|---|---|
tagger | David Grove <groved@us.ibm.com> | Wed Jul 03 13:35:24 2019 -0400 |
object | 65a641c4b2c160b1ddc29bc1439bfd26b9d055dc |
7.1@1.13.0-incubating
tag | 65a641c4b2c160b1ddc29bc1439bfd26b9d055dc | |
---|---|---|
tagger | Rodric Rabbah <rodric@gmail.com> | Tue May 14 10:10:40 2019 -0400 |
object | 9c5d3d779425223488ca0f49100095736853f147 |
Apache OpenWhisk Runtimes 1.13 release.
commit | 9c5d3d779425223488ca0f49100095736853f147 | [log] [tgz] |
---|---|---|
author | falkzoll <falkzoll@de.ibm.com> | Mon Apr 01 15:43:50 2019 +0200 |
committer | David Grove <dgrove-oss@users.noreply.github.com> | Mon Apr 01 09:43:50 2019 -0400 |
tree | 658f2f3aedd210999e90e7d5e88fec917922a7c3 | |
parent | d19cb764d2d83465d28a0f08d2343848f2f4f4a0 [diff] |
Update to php7.1.27,7.2.16 and 7.3.3. (#55) Update to actionloop 42fd5e6.
This runtime provides PHP 7.3, 7.2 and 7.1.
To use as a docker action
PHP 7.3:
wsk action update myAction myAction.php --docker openwhisk/action-php-v7.3:latest
PHP 7.2:
wsk action update myAction myAction.php --docker openwhisk/action-php-v7.2:latest
PHP 7.1:
wsk action update myAction myAction.php --docker openwhisk/action-php-v7.1:latest
This works on any deployment of Apache OpenWhisk
To use as a kind action
PHP 7.3:
wsk action update myAction myAction.php --kind php:7.3
PHP 7.2:
wsk action update myAction myAction.php --kind php:7.2
PHP 7.1:
wsk action update myAction myAction.php --kind php:7.1
./gradlew core:php7.3Action:distDocker ./gradlew core:php7.2Action:distDocker ./gradlew core:php7.1Action:distDocker
This will produce the images whisk/action-php-v7.3
, whisk/action-php-v7.2
& whisk/action-php-v7.1
Build and Push image
docker login ./gradlew core:php7.3Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io ./gradlew core:php7.2Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io ./gradlew core:php7.1Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io
Deploy OpenWhisk using ansible environment that contains the kinds php:7.3
, php:7.2
& php:7.1
Assuming you have OpenWhisk already deploy locally and OPENWHISK_HOME
pointing to root directory of OpenWhisk core repository.
Set ROOTDIR
to the root directory of this repository.
Redeploy OpenWhisk
cd $OPENWHISK_HOME/ansible ANSIBLE_CMD="ansible-playbook -i ${ROOTDIR}/ansible/environments/local" $ANSIBLE_CMD setup.yml $ANSIBLE_CMD couchdb.yml $ANSIBLE_CMD initdb.yml $ANSIBLE_CMD wipe.yml $ANSIBLE_CMD openwhisk.yml
Or you can use wskdev
and create a soft link to the target ansible environment, for example:
ln -s ${ROOTDIR}/ansible/environments/local ${OPENWHISK_HOME}/ansible/environments/local-php wskdev fresh -t local-php
To use as docker action push to your own dockerhub account
docker tag whisk/php7.2Action $user_prefix/action-php-v7.3 docker push $user_prefix/action-php-v7.3
docker tag whisk/php7.2Action $user_prefix/action-php-v7.2 docker push $user_prefix/action-php-v7.2
docker tag whisk/php7.1Action $user_prefix/action-php-v7.1 docker push $user_prefix/action-php-v7.1
Then create the action using your the image from dockerhub
wsk action update myAction myAction.php --docker $user_prefix/action-php-v7.3
The $user_prefix
is usually your dockerhub user id.
Install dependencies from the root directory on $OPENWHISK_HOME repository
./gradlew install
Using gradle for the ActionContainer tests you need to use a proxy if running on Mac, if Linux then don't use proxy options You can pass the flags -Dhttp.proxyHost=localhost -Dhttp.proxyPort=3128
directly in gradle command. Or save in your $HOME/.gradle/gradle.properties
systemProp.http.proxyHost=localhost systemProp.http.proxyPort=3128
Using gradle to run all tests
./gradlew :tests:test
Using gradle to run some tests
./gradlew :tests:test --tests *ActionContainerTests*
Using IntelliJ:
-Dhttp.proxyHost=localhost -Dhttp.proxyPort=3128
Apache OpenWhisk Runtime PHP is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.