You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 9, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: examples/http-custom-path/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ In this example we will deploy a function that will be available under the path
7
7
We will need to have an Ingress controller deployed in order to be able to deploy your function in a specific path. If you don't have it yet you can deploy one executing:
@@ -22,7 +22,7 @@ Serverless: Waiting for function hello to be fully deployed. Pods status: {"wait
22
22
Serverless: Function hello succesfully deployed
23
23
```
24
24
25
-
As we can see in the logs an Ingress Rule has been deployed to run our function at `/hello`. We can know the specific URL in which the function will be listening executing `serverless info`:
25
+
As we can see in the logs an Ingress Rule has been deployed to run our function at `/hello`. If no host is specified, by default it will use `API_URL.nip.io` being `API_URL` the URL/IP of the Kubernetes IP. We can know the specific URL in which the function will be listening executing `serverless info`:
26
26
```console
27
27
$ serverless info
28
28
Service Information "hello"
@@ -34,7 +34,7 @@ Ports:
34
34
Target Port: 8080
35
35
Node Port: 31444
36
36
Function Info
37
-
URL: 192.168.99.100/hello
37
+
URL: 192.168.99.100.nip.io/hello
38
38
Handler: handler.hello
39
39
Runtime: python2.7
40
40
Trigger: HTTP
@@ -43,7 +43,7 @@ Dependencies:
43
43
44
44
Depending on the Ingress configuration the URL may be redirected to use the HTTPS protocol. You can call your function with a browser or executing:
Copy file name to clipboardExpand all lines: examples/todo-app/README.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,10 +11,6 @@ You'll find two directories here. Deploy them in the following order:
11
11
1. The [backend](backend) directory contains the whole Serverless service and it's corresponding function code.
12
12
2. The [frontend](frontend) directory contains the frontend you can connect to your backend to use the Todos service through your web browser.
13
13
14
-
# Known issue
15
-
16
-
When deploying this applicaiton with the default ingress controller the web browser may reject the self-signed certificate used. To be able to use the application go to `https://API_URL` (where API_URL is the URL of your cluster) and add the certificate to the white list.
17
-
18
14
# Source
19
15
20
16
This is a modified version of Philipp Muens Todo example from his serverless [book](https://github.com/pmuens/serverless-book/blob/master/06-serverless-by-example/02-a-serverless-todo-application.md). Modified to run on [Kubeless](https://github.com/kubeless/kubeless)
Copy file name to clipboardExpand all lines: examples/todo-app/frontend/react-redux/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Do the following to setup and use the frontend
6
6
7
7
1. Make sure that you've deployed the backend of the `todo` application
8
8
2. Run `npm install` to install the used npm packages
9
-
3. Go to `app/js/actions/index.js` and update the `API_URL` with the endpoint of your deployed `todo` Serverless service (e.g. `https://192.168.99.100`)
10
-
*NOTE: Check the [known issue](../../README.md#known-issue) for web browsers and the self-signed certificate
9
+
3. Go to `app/js/actions/index.js` and update the `API_URL` with the endpoint of your deployed `todo` Serverless service (e.g. `http://192.168.99.100.nip.io`)
10
+
*Note: You can find the application hostname executing `serverless info` in the backend folder and checking the field `URL` of any function.
11
11
4. Run `npm start`
12
12
5. Open up a browser on [localhost:8080](http://localhost:8080) and play around with the application
0 commit comments