Lucky

A self-hosted home-network utility that consolidates port forwarding, reverse proxying, dynamic DNS, wake-on-LAN, IPv4 NAT traversal, WebDAV services, task…

  • Automation
  • Network Services
A self-hosted home-network utility that consolidates port forwarding, reverse proxying, dynamic DNS, wake-on-LAN, IPv4 NAT traversal, WebDAV services, task scheduling, and automatic certificate management in a single web-managed app.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

12/100 Low

Maintained
0last commit 1151 days ago
Popular
144 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
4
Open issues
0
Last commit
2023-09-26
Latest release
v1.0.0
License
GPL-3.0
Activity
stale

Checked 13 days ago - source: GitHub (omerbustun/git-lucky)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install and start PostgreSQL first Install PostgreSQL (the database program that stores Lucky's data) and make sure it is running before launching Lucky. Without it, Lucky will have nowhere to save or read data and may error out. source
  • Run the setup script before starting Lucky Run ./script/setup the first time you set up an existing Lucky app. It prepares web files, installs the app's needed code packages, creates the database, and updates its structure, so skipping it can leave Lucky with missing pieces or no usable data store. source
  • Fill in real setting values first Before starting the app, replace example configuration values, such as the api_token (a secret key) in Habitat (the app's settings system), with your real keys. If you leave placeholders in place, features that depend on those settings will fail. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Lucky require PostgreSQL before first launch?

Yes. Install and start PostgreSQL before launching Lucky because it stores Lucky's data, and Lucky may error out without it.

What one-time command should be run when first setting up an existing Lucky app?

Run ./script/setup before starting Lucky. It prepares web files, installs needed code packages, creates the database, and updates its structure.

What should be done to configuration values before starting Lucky?

Replace example configuration values, such as the api_token secret key in Habitat, with real keys. If placeholders remain, features that depend on those settings can fail.

Answers sourced from luckyframework.org, luckyframework.org, luckyframework.org

Community

Collected 48 days ago - public community threads