FlyingFish
FlyingFish on GitHub
  • FlyingFish
    • About the project
    • Screenshots
    • Installation
      • Quick Setup
      • Quick Update
      • Create Backup
      • Long setup
        • Env
        • Docker compose
          • Ports
          • Network
      • Storage management
      • FAQ
    • Configurations
      • Which user type am I
      • Listen
        • Port forwarding
        • Proxy protocol
        • IP Access
        • Gateway identifiers
        • UPnP Nat
      • Domains
        • DynDns Clients
        • Own DNS Server
        • Discussions Subdomains
        • DynDns Server
      • Routes
    • Examples
      • SSH hidden on HTTPS
      • FlyingFish to other reverse proxy
      • Backup Server, SSH to Nas
      • Own DynDNS Server - Fritzbox
      • Inventree - Route
    • Developer
      • Ideas, requests and bugs
      • Project structure
        • Under the hood
        • Service structure
        • Schema
        • Object name rules
      • Image build
      • Plugins
    • Contribution
Powered by GitBook
On this page
  • Memory
  • Hard disk space
  • Summary
Edit on GitHub
  1. FlyingFish
  2. Installation

Storage management

PreviousNetworkNextFAQ

Last updated 3 months ago

With the new version v1.1.12 a few more containers have been added. Among other things, Redis and InfluxDB.

This resulted in some problems for the host system because the wrong memory sizes were selected.

Memory

Choose the appropriate RAM size for your system. At the beginning and also as a goal I set a system with 2 GB. This depends on what kind of traffic I expect. This means I have now restricted the Redis server and the InfluxDB server. The settings for this can be set in the Docker-Compose file and in the

The limit of the Nginx workers is also set to 4096 by default. These can be set in the web interface under Settings.

Hard disk space

I have given my VM 60 GB here. But after 1 year of operation I realized that the logs were too many.

In addition to the Docker image, some logs are written by the containers. In the new version (1.2.0) some changes have been made, and the log rotation has been improved. The important data is all located in Docker volumes.

Don't log everything in the productive system! I run my own system with the logs "silly", but only to understand all the processes and to further develop the software. Your system should run with logs of "error", maximum "waring".

Summary

Pay attention to how much traffic your system processes and give the VM the resources accordingly.

Env.
Proxmox FlyingFish VM