About the project
Last updated
Last updated
The source code from FlyingFish and all parts (Nginx, MariaDB, InfluxDB, Node.js, etc.) are open source and can be viewed by anyone. I used open source to ensure security and trust for the used software. In addition, everyone can contribute to improve the software.
I only got to know the Nginx server after Apache. And was pleasantly surprised by the configuration. Some time ago I dealt with the topic of splitting several domains with destinations via the VPN via a bundled server. I found a domain mapping/splitting in the Nginx newer version. From another widely used project (, which is a very good project) I use a lot the creation of certificates (Lets encrypt). I started the project and have a lot to learn myself, to incorporate my own ideas and extensions. It is another building block for other projects that I am making available to others.
The name of the project is an allusion to the fish that is "air" in an atypical environment for it. Nevertheless, the fish copes perfectly here. This is how I see the project with the Nginx server and the interacting components. The name also goes well with "Docker" a whale.
In the classic sense, FlyingFish is a nginx manager. But the way the nginx server is combined with other services is different! The FlyingFish is structured in part service, which automates many processes through an internal database or API communication.
Docker
Docker is used for quick installation and specifically separates/seals the components from the FlyingFish.
Nginx
The Nginx server works as a proxy reserve and interacts with the backend.
Lets encrypt
Automatic generation of certificates and automatic renewal.
DNS management
DNS Server, DynDNS Client and DynDNS Server manage the domains.
UpnpNat
With a mobile device, the correct ports to nginx can be opened automatically on the router with UpnpNat.
SSH jump server
An internal SSH Jump Server can be hidden behind the HTTPS port.
API
API connection for external projects.
