Skip to content

Commit fa385a3

Browse files
committed
updated lead.
1 parent 0054e72 commit fa385a3

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

README.rst

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ python-λ
1414
:alt: Python Versions
1515
:target: https://pypi.python.org/pypi/python-lambda/
1616

17-
Python-lambda is a toolset for developing microservices in AWS Lambda.
17+
Python-lambda is a toolset for developing and deploying *serverless* Python code in AWS Lambda.
1818

1919
Description
2020
===========
@@ -23,7 +23,7 @@ AWS Lambda is a service that allows you to write Python, Java, or Node.js code t
2323

2424
Working with Lambda is relatively easy, but the process of bundling and deploying your code is not as simple as it could be.
2525

26-
The *Python-Lambda* library takes away the guest work of developing your Python-Lambda microservices by providing you a toolset to streamline the annoying parts.
26+
The *Python-Lambda* library takes away the guest work of developing your Python-Lambda services by providing you a toolset to streamline the annoying parts.
2727

2828
Requirements
2929
============
@@ -40,20 +40,20 @@ Begin by creating a new virtualenv and project folder.
4040

4141
.. code:: bash
4242
43-
$ mkvirtualenv my_microservice
44-
(my_microservice) $ mkdir my_microservice
43+
$ mkvirtualenv lambduh
44+
(lambduh) $ mkdir lambduh
4545
4646
Next, download *Python-Lambda* using pip via pypi.
4747

4848
.. code:: bash
4949
50-
(my_microservice) $ pip install python-lambda
50+
(lambduh) $ pip install python-lambda
5151
52-
From your ``my_microservice`` directory, run the following to bootstrap your project.
52+
From your ``lambduh`` directory, run the following to bootstrap your project.
5353

5454
.. code:: bash
5555
56-
(my_microservice) $ lambda init
56+
(lambduh) $ lambda init
5757
5858
This will create the following files: ``event.json``, ``__init__.py``, ``service.py``, and ``config.yaml``.
5959

@@ -81,7 +81,7 @@ If you now try and run:
8181

8282
.. code:: bash
8383
84-
(my_microservice) $ lambda invoke
84+
(lambduh) $ lambda invoke
8585
# "your test handler was successfully invoked!"
8686
# below shows the result returned by your function execution:
8787
# 5.858
@@ -94,7 +94,7 @@ When you're ready to deploy your code to Lambda simply run:
9494

9595
.. code:: bash
9696
97-
(my_microservice) $ lambda deploy
97+
(lambduh) $ lambda deploy
9898
9999
The deploy script will evaluate your virtualenv and identify your project dependencies. It will package these up along with your handler function to a zip file that it then uploads to AWS Lambda.
100100

0 commit comments

Comments
 (0)