alihan/fn-serverless
1
0
Fork 0
mirror of https://github.com/fnproject/fn.git synced 2022-10-28 21:29:17 +03:00
Code Issues Packages Projects Releases Wiki Activity

fnctl: update docs and function filenames (#283)

Browse Source 
* fnctl: functions.yaml -> func.yaml

* fnctl: update documentation
This commit is contained in:
C Cirello
2016-11-15 01:54:26 +01:00
committed by GitHub
parent 1395393b9b
commit d8526a85e1
13 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
examples/blog/functions.yml → examples/blog/func.yml
View File

0
examples/caddy-lb/functions.yml → examples/caddy-lb/func.yml
View File

0
examples/checker/functions.yml → examples/checker/func.yml
View File

0
examples/echo/functions.yml → examples/echo/func.yml
View File

0
examples/error/functions.yml → examples/error/func.yml
View File

0
examples/hello-go/functions.yml → examples/hello-go/func.yml
View File

0
examples/hello-ruby/functions.yml → examples/hello-ruby/func.yml
View File

0
examples/hello/php/functions.yaml → examples/hello/php/func.yaml
View File

0
examples/hello/python/functions.yaml → examples/hello/python/func.yaml
View File

0
examples/redis/functions.yml → examples/redis/func.yml
View File

0
examples/sleeper/functions.yml → examples/sleeper/func.yml
View File

0
examples/twitter/functions.yml → examples/twitter/func.yml
View File

2
fnctl/README.md
View File

@@ -175,7 +175,7 @@ It means that first subdirectory are always considered app names (e.g. `myapp`
and `other`), each subdirectory of these firsts are considered part of the route and `other`), each subdirectory of these firsts are considered part of the route
(e.g. `route1/subroute1`). (e.g. `route1/subroute1`).
`fnctl update` expects that each directory to contain a file `func.yaml` `fnctl publish` expects that each directory to contain a file `func.yaml`
which instructs `fnctl` on how to act with that particular update, and a which instructs `fnctl` on how to act with that particular update, and a
Dockerfile which it is going to use to build the image and push to Docker Hub. Dockerfile which it is going to use to build the image and push to Docker Hub.