A small webserver and templating library specifically designed for MicroPython on the Pico W. It aims to provide a complete toolkit for easily creating high quality web based interfaces for your projects.
phew! is ideal for creating web based provisioning interfaces for connected projects using the Raspberry Pi Pico W.
import and during execution)/greet/<name>{{name.lower()}}GET, POST request methodsmultipart/form-data, x-www-form-urlencoded, and JSON POST bodiesconnect_to_wifi and access_point convenience methodsWhere possible phew! tries to minimise the amount of code and setup that you, the developer, has to do in favour of picking sane defaults and hiding away bits of minutiae that rarely needs to be tweaked.
phew! can be installed using pip from the command line or from your favourite IDE. In Thonny this can be achieved by clicking Tools -> Manage packages and searching for micropython-phew.
An example web server that returns a random number between 1 and 100 (or optionally the range specified by the callee) when requested:
from phew import server, connect_to_wifi
connect_to_wifi("<ssid>", "<password>")
@server.route("/random", methods=["GET"])
def random_number(request):
import random
min = int(request.query.get("min", 0))
max = int(request.query.get("max", 100))
return str(random.randint(min, max))
@server.catchall()
def catchall(request):
return "Not found", 404
server.run()phew is designed specifically with performance and minimal resource use in mind. Generally this means it will prioritise doing as little work as possible including assuming the correctness of incoming requests.
The server module provides all functionality for running a web server with
route handlers.
server.add_route(path, handler, methods=["GET"])Adds a new route into the routing table. When an incoming request is received the server checks each route to find the most specific one that matches the request based on the path and method. If a route is found then the handler function is called with a request parameter
that contains details about the request.
def my_handler(request):
return "I got it!", 200
server.add_route("/testpath", my_handler, methods=["GET"])Or, alternatively, using a decorator:
@server.route("/testpath", methods=["GET"])
def my_handler(request):
return "I got it!", 200server.set_catchall(handler)Provide a catchall method for requests that didn't match a route.
def my_catchall(request):
return "No matching route", 404
server.set_catchall(my_catchall)Or, alternatively, using a decorator:
@server.catchall()
def my_catchall(request):
return "No matching route", 404server.run(host="0.0.0.0", port=80)Starts up the web server and begins handling incoming requests.
server.run()The Request object contains all of the information that was parsed out of the
incoming request including form data, query string parameters, HTTP method, path,
and more.
Handler functions provided to add_route and set_catchall will recieve a
Request object as their first parameter.
| member | example | type | description |
|---|---|---|---|
| protocol | "HTTP/1.1" |
string | protocol version |
| method | "GET" or "POST" |
string | HTTP method used for this request |
| uri | "/path/to/page?parameter=foo" |
string | full URI of the request |
| path | "/path/to/page" |
string | just the path part of the URI |
| query_string | "parameter=foo" |
string | just the query string part of the URI |
| form | {"foo": "bar", "name": "geoff"} |
dict | POST body parsed as multipart/form-data |
| data | [{"name": "jenny"}, {"name": "geoff"}] |
any | POST body parsed as JSON |
| query | {"parameter": "foo"} |
dict | result of parsing the query string |
At the time your route handler is being called the request has been fully parsed and you can access any properties that are relevant to the request (e.g. the form dictionary for a multipart/form-data request) any irrelevant properties will be set to None.
@server.route("/login", ["POST"])
def login_form(request):
username = request.form.get("username", None)
password = request.form.get("password", None)
# check the user credentials with your own code
# for example:
#
# logged_in = authenticate_user(username, password)
if not logged_in:
return "Username or password not recognised", 401
return "Logged in!", 200The Response object encapsulates all of the attributes of your programs response
to an incoming request. This include the status code of the result (e.g. 200 OK!)
, the data to return, and any associated headers.
Handler functions can create and return a Response object explicitly or use a couple
of shorthand forms to avoid writing the boilerplate needed.
| member | example | type | description |
|---|---|---|---|
| status | 200 |
int | HTTP status code |
| headers | {"Content-Type": "text/html"} |
dict | dictionary of headers to return |
| body | "this is the response body" |
string or generator | the content to be returned |
@server.route("/greeting/<name>", ["GET"])
def user_details(request):
return Response(f"Hello, {name}", status=200, {"Content-Type": "text/html"})As shorthand instead of returning a Response object the handle may also return a tuple with between
one and three values:
200 if not provided{"Content-Type": "text/html"} if not providedFor example:
@server.route("/greeting/<name>", ["GET"])
def user_details(request, name):
return f"Hello, {name}", 200A web server isn't much use without something to serve. While it's straightforward to serve the contents of a file or some generated JSON things get more complicated when we want to present a dynamically generated web page to the user.
phew! provides a templating engine which allows you to write normal HTML with fragments of Python code embedded to output variable values, parse input, or dynamically load assets.
render_template(template, param1="foo", param2="bar", ...):The render_template method takes a path to a template file on the filesystem and
a list of named paramaters which will be passed into the template when parsing.
The method is a generator which yields the parsing result in chunks, minimising the amount of memory used to hold the results as they can be streamed directly out rather than having to build the entire result as a string first.
Generally you will call render_template to create the body of a Response in one
of your handler methods.
Templates are not much use if you can't inject dynamic data into them. With phew!
you can embed Python expressions with {{<expression here>}} which will be evaluated
during parsing.
In the simplest form you can embed a simple value by just enclosing it in double curly braces. It's also possible to perform more complicated transformations using any built in Python method.
<div id="name">{{name}}</div>
<div id="name">{{name.upper()}}</div>
<div id="name">{{"/".join(name.split(" "))}}</div>If you want to show a value only if some other condition is met then you can use the (slightly clunky) Python tenary operator.
<div>
You won
{{"1st" if prize == 1 else ""}}
{{"2nd" if prize == 2 else ""}}
{{"3rd" if prize == 3 else ""}}
prize!
</div>or
<div>
You won
{{["1st", "2nd", "3rd"][prize]}}
prize!
</div>While a bit unwieldy this methods works. An alternative would be to select the appropriate value in your handler and simply pass it into the template as a parameter however that would mean having some of your copy embedded into your Python code rather than all of it in one place in the template file.
You can include another template by calling render_template() again within your outer template.
include.html
Hello there {{name}}!main.html
<!DOCTYPE html>
<body>
{{render_template("include.html", name=name)}}
</body>:warning: Note: you need to explicitly pass through template parameters into the included template - they are not available by default.
Add a new entry into the log file.
log("info", "> i'd like to take a minute, just sit right there")
log("error", "> the license plate said 'Fresh' and it had dice in the mirror")The entry will automatically have the current date and time, the level value, and the amount of free memory in kB prepended:
2022-09-04 15:29:20 [debug / 110kB] > performing startup
2022-09-04 15:30:42 [info / 113kB] - wake reason: rtc_alarm
2022-09-04 15:30:42 [debug / 112kB] - turn on activity led
2022-09-04 15:30:43 [info / 102kB] > running pump 1 for 0.4 second
2022-09-04 15:30:46 [info / 110kB] > 5 cache files need uploading
2022-09-04 15:30:46 [info / 107kB] > connecting to wifi network 'yourssid'
2022-09-04 15:30:48 [debug / 100kB] - connecting
2022-09-04 15:30:51 [info / 87kB] - ip address: 192.168.x.x
2022-09-04 15:30:57 [info / 79kB] - uploaded 2022-09-04T15:19:03Z.json 2022-09-04 15:31:01 [info / 82kB] - uploaded 2022-09-04T15:28:17Z.json 2022-09-04 15:31:06 [info / 88kB] - uploaded 2022-09-04T15:30:43Z.json 2022-09-04 15:31:11 [info / 95kB] - uploaded 2022-09-04T15:29:00Z.json 2022-09-04 15:31:16 [info / 100kB] - uploaded 2022-09-04T15:29:21Z.json 2022-09-04 15:31:16 [info / 98kB] > going to sleepShorthand method for writing debug messages to the log.
warn("> this is a story")Shorthand method for writing information to the log.
num = 123
info("> all about how", num, time.time())Shorthand method for writing warnings to the log.
warn("> my life got flipped")Shorthand method for writing errors to the log.
warn("> turned upside down")Will automatically truncate the log file to truncate_to bytes long when it reaches truncate_at bytes in length.
# automatically truncate when we're closed to the
# filesystem block size to keep to a single block
set_truncate_thresholds(3.5 * 1024, 2 * 1.024)Truncation always happens on the nearest line ending boundary so the truncated file may not exactly match the size specified.
To make implementing device provisioning interfaces (via captive portal) simple phew! provides a catchall DNS server.
If you put the Pico W into access point mode and then run the catchall DNS server it will route all DNS requests back to the local device so that they can be handled.
dns.run_catchall(ip_address)Pass in the IP address of your device once in access point mode.
connect_to_wifi(ssid, password, timeout=30)Connects to the network specified by ssid with the provided password.
Returns the device IP address on success or None on failure.
access_point(ssid, password=None)Create an access point with the specified SSID. Optionally password protected if provided.
result = is_connected_to_wifi()Returns True if there is an active WiFi connection.
get_ip_address()Returns the current IP address if connected to a network or acting as an access point or None otherwise.
Here are some Phew! community projects and guides that you might find useful. Note that code at the links below has not been tested by us and we're not able to offer support with it.