I've been reading the issues about using nginx as reverse proxy, so there're people where it seems to work.
The problem is that there isn't enough info to set it up properly.
My setup:

nginx:

location / {
    # First attempt to serve request as file, then
    # as directory, then fall back to displaying a 404.
    #try_files $uri $uri/ =404;
    proxy_pass htt

If, for the directory /var/lib/virt-lightning/pool/upstream, the underlying filesystem is BTRFS, then we should make sure the images are created with copy on write turned off.

There are several ways to do it:

• make sure /var/lib/virt-lightning/pool/upstream is created with nocow option
• chattr -C on the empty files

I am not sure which ways should be the most suitable for the project.

• to be extendable for containers, rather use the proc fs than reading the values from libvirt daemon.
• missing metrics: wait times, queue sizes, cache misses, errors, etc.

Nitro is currently lacking in documentation, this should be improved. I am creating this issue to track the progress of documentation project.

As of what the documentation should contain, as a starting point, I think we should have:

• Basic API Documentation: Basic documentation of classes and functions.
• Higher-Level Description of Project Structure: What are the different

New features have been added but the documentation is not in sync.