Home - softerfish/fyuhls GitHub Wiki

fyuhls wiki

This wiki is the operator handbook for fyuhls v0.1.5.

Use it when you need:

  • deployment guidance
  • admin-side configuration notes
  • storage and delivery setup help
  • monetization and rewards operations
  • API and extension references

Recommended reading order

  1. Installation and Deployment
  2. Config Hub Reference
  3. Storage Nodes
  4. Local Storage
  5. Wasabi Setup
  6. Cloudflare R2 Setup
  7. Backblaze B2 Setup
  8. S3 Compatible Setup
  9. Uploads and Downloads
  10. Downloads, CDN, and Delivery Methods
  11. File Manager Guide
  12. Admin Dashboard Guide
  13. Cron and Heartbeat
  14. System Status and Diagnostics
  15. Support Center and Support Bundles
  16. Email and SMTP
  17. Packages
  18. Nginx Setup
  19. Cloudflare Setup
  20. Cloudflare Turnstile Setup
  21. ProxyCheck Setup
  22. Rewards and Withdrawals
  23. Rewards Fraud
  24. Stripe and PayPal Payments
  25. Requests and Compliance
  26. Two-Factor Auth
  27. Public API
  28. Plugin Development
  29. Theme Overrides and Branding
  30. Demo Mode and Demo Admin

What changed in v0.1.5

  • account-facing pages such as the file manager, settings, rewards, and affiliate views now share a more consistent shell and sidebar structure
  • human-facing download-state pages now use a shared rendering path, which makes ad placement and blocked-state behavior more consistent
  • VPN and proxy protection now supports three clear modes: None, Enforcement, and Intelligence
  • the Requests inbox now includes in-place DMCA file-removal processing with live activity updates
  • Rewards Fraud now has stronger proxy/VPN intelligence guidance and a clearer manual review flow
  • storage, cron, and admin workflow pages are more internally consistent with the current admin surface

Page map

Core setup

Storage and delivery

Accounts and protection

Monetization and compliance

Integrations and extensions

Maintenance rule

When a product behavior changes, update these together:

  1. the relevant in-app admin guide
  2. the matching wiki page
  3. the public docs or API docs if installers, owners, or developers are affected

Documentation habit

If you are checking whether a wiki page is still current, compare it against:

  • the matching admin page
  • Admin > Docs
  • the current README and changelog for broader operator-facing behavior changes