How to handle POST data in Nanoweb?

Nanoweb allows reading POST data through the request object in handler functions. The example.py file shows how to process POST requests, including file uploads and form data, by accessing the request stream asynchronously.

Does Nanoweb support WebSockets?

No, Nanoweb does not natively support WebSockets. It is focused on basic HTTP server functionality, so for real-time communication, you would need to implement WebSockets separately or use a different library.

Nanoweb vs uasyncio server: which is better for MicroPython?

Nanoweb builds on uasyncio to provide a higher-level web server with routing and static file support, whereas uasyncio.servers offer more low-level control. Choose Nanoweb for convenience in web applications; use uasyncio directly for custom protocols.

How to serve static files with Nanoweb?

Nanoweb has built-in static file management through the assets_extensions configuration. Define which file extensions to serve statically, and the server handles requests automatically, as mentioned in the features.

Can Nanoweb run on Raspberry Pi Pico?

Yes, Nanoweb is designed to run on various MicroPython boards including Raspberry Pi Pico, ESP8266, and ESP32, as stated in the project description and README.

Is Nanoweb good for building REST APIs?

Yes, Nanoweb is suitable for lightweight REST APIs on microcontrollers, with support for HTTP methods like GET, POST, and DELETE, and JSON responses as shown in the example.py file.

Open-Awesome

micropython-nanoweb

MITPythonv1.0.0

A full asynchronous web server for MicroPython designed for microcontrollers with minimal memory footprint.

GitHub

119 stars19 forks0 contributors

What is micropython-nanoweb?

Nanoweb is a full asynchronous web server designed specifically for MicroPython, enabling web server functionality on microcontrollers with limited memory and processing power. It solves the problem of running a web server on embedded devices like ESP8266, ESP32, and Raspberry Pi Pico by balancing features with a small memory footprint. The server supports routing, static file serving, and asynchronous request handling, making it ideal for IoT projects.

Target Audience

Embedded developers and IoT enthusiasts working with MicroPython on microcontrollers who need to add web server capabilities to their projects without overwhelming device resources.

Value Proposition

Developers choose Nanoweb for its asynchronous architecture and minimal memory usage, allowing web server functionality on devices where traditional servers are impossible. Its simple API, decorator-based routing, and static file support provide a practical solution for building web-enabled embedded applications.

Overview

Full async Micropython web server with small memory footprint.

Use Cases

Best For

Building web interfaces for IoT devices running on ESP32 or ESP8266
Creating lightweight REST APIs for microcontroller-based projects
Serving static web pages or assets from embedded systems
Prototyping web-enabled sensor networks with MicroPython
Developing asynchronous web servers for Raspberry Pi Pico applications
Adding HTTP server functionality to resource-constrained embedded devices

Not Ideal For

Projects requiring HTTPS encryption or advanced security features out-of-the-box
High-traffic web applications where scalability beyond basic async handling is critical
Developers needing a rich ecosystem with built-in templating, ORM, or extensive middleware

Pros & Cons

Pros

Asynchronous Architecture

Full asynchronous operation enables efficient, non-blocking request handling on single-threaded microcontrollers, as highlighted in the key features for concurrency.

Flexible Route Declaration

Supports both dictionary-based and decorator-based routing, allowing for clean and adaptable code structure, demonstrated in the usage example with @naw.route.

Static File Management

Includes built-in support for serving static files with configurable extensions via assets_extensions, simplifying asset delivery from embedded devices.

Minimal Memory Footprint

Designed specifically for resource-constrained environments like ESP8266 and ESP32, balancing features with low memory usage per the project philosophy.

Cons

Limited Feature Set

Lacks advanced web server features such as HTTPS support, templating engines, or database integration, requiring developers to build these manually.

Sparse Documentation

The README provides only basic examples without comprehensive guides or API references, which can slow development for complex projects.

MicroPython-Only

Exclusively tied to MicroPython environments, making it unsuitable for standard Python projects or other embedded runtimes without modification.

Frequently Asked Questions

Related Projects

microdot

The impossibly small web framework for Python and MicroPython.

Stars2,143

Forks156

Last commit9 days ago

MicroWebSrv2

The last Micro Web Server for IoTs (MicroPython) or large servers (CPython), that supports WebSockets, routes, template engine and with really optimized architecture (mem allocations, async I/Os). Ready for ESP32, STM32 on Pyboard, Pycom's chipsets (WiPy, LoPy, ...). Robust, efficient and documented!

Stars719

Forks100

Last commit1 year ago

MicroWebSrv

A micro HTTP Web server that supports WebSockets, html/python language templating and routing handlers, for MicroPython (used on Pycom modules & ESP32)

Stars661

Forks118

Last commit3 years ago

tinyweb

Simple and lightweight HTTP async server for micropython

Stars278

Forks47

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub