This is a personal fork of gethomepage/homepage.
This fork is not affiliated with the original project maintainers. For the official version, please visit the upstream repository.
This fork extends Homepage with additional, optional features.
Branch: feature/worldclock
Adds a lightweight information widget for displaying multiple time zones with customizable labels and optional country flags. Designed for global teams and distributed operations.
- worldclock:
format: 24h
show_date: true
layout: grid
columns: 3
clocks:
- timezone: Europe/Berlin
label: DE
flag: de
- timezone: America/New_York
label: NYC
flag: us
- timezone: Asia/Tokyo
label: TYO
flag: jpβ‘οΈ See World Clock Documentation for all supported options.
Branch: feature/pwa-configuration
Homepage supports installation as a Progressive Web App (PWA) on mobile devices, tablets, and desktops. This feature exposes the full PWA manifest configuration, allowing precise control over app name, appearance, icons, colors, and platform-specific behavior.
pwa:
title: "Dashboard | BAUER GROUP"
shortName: "Dashboard"
description: "Dashboard of Company Services at BAUER GROUP"
display: standalone
startUrl: /
scope: /
themeColor: "#FF8500"
backgroundColor: "#18181B"
iconPath: /images/iconsThe configuration is added to settings.yaml and is automatically converted into a valid PWA manifest.
For the complete list of supported options (icons, categories, Apple settings, orientation, etc.), see: β‘οΈ PWA Configuration
services:
homepage:
image: ghcr.io/karlspace/dashboard:latest
# ... rest of your config
A modern, fully static, fast, secure fully proxied, highly customizable application dashboard with integrations for over 100 services and translations into multiple languages. Easily configured via YAML files or through docker label discovery.
With features like quick search, bookmarks, weather support, a wide range of integrations and widgets, an elegant and modern design, and a focus on performance, Homepage is your ideal start to the day and a handy companion throughout it.
- Fast - The site is statically generated at build time for instant load times.
- Secure - All API requests to backend services are proxied, keeping your API keys hidden. Constantly reviewed for security by the community.
- For Everyone - Images built for AMD64, ARM64.
- Full i18n - Support for over 40 languages.
- Service & Web Bookmarks - Add custom links to the homepage.
- Docker Integration - Container status and stats. Automatic service discovery via labels.
- Service Integration - Over 100 service integrations, including popular starr and self-hosted apps.
- Information & Utility Widgets - Weather, time, date, search, and more.
- And much more...
Homepage has built-in support for Docker, and can automatically discover and add services to the homepage based on labels. See the Docker Service Discovery page for more information.
Homepage also has support for hundreds of 3rd-party services, including all popular *arr apps, and most popular self-hosted apps. Some examples include: Radarr, Sonarr, Lidarr, Bazarr, Ombi, Tautulli, Plex, Jellyfin, Emby, Transmission, qBittorrent, Deluge, Jackett, NZBGet, SABnzbd, etc. As well as service integrations, Homepage also has a number of information providers, sourcing information from a variety of external 3rd-party APIs. See the Service page for more information.
Homepage has built-in support for a number of information providers, including weather, time, date, search, glances and more. System and status information presented at the top of the page. See the Information Providers page for more information.
Homepage is highly customizable, with support for custom themes, custom CSS & JS, custom layouts, formatting, localization and more. See the Settings page for more information.
For configuration options, examples and more, please check out the homepage documentation.
Please note that when using features such as widgets, Homepage can access personal information (for example from your home automation system) and Homepage currently does not (and is not planned to) include any authentication layer itself. If Homepage is reachable from any untrusted network, it must sit behind a reverse proxy (and/or VPN) that enforces authentication, TLS, and strictly validates Host headers. The built-in host check in Homepage is a best-effort guard and should not be treated as security when exposed publicly.
Using docker compose:
services:
homepage:
image: ghcr.io/gethomepage/homepage:latest
container_name: homepage
environment:
HOMEPAGE_ALLOWED_HOSTS: gethomepage.dev # required, may need port. See gethomepage.dev/installation/#homepage_allowed_hosts
PUID: 1000 # optional, your user id
PGID: 1000 # optional, your group id
ports:
- 3000:3000
volumes:
- /path/to/config:/app/config # Make sure your local config directory exists
- /var/run/docker.sock:/var/run/docker.sock:ro # optional, for docker integrations
restart: unless-stoppedor docker run:
docker run --name homepage \
-e HOMEPAGE_ALLOWED_HOSTS=gethomepage.dev \
-e PUID=1000 \
-e PGID=1000 \
-p 3000:3000 \
-v /path/to/config:/app/config \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
--restart unless-stopped \
ghcr.io/gethomepage/homepage:latestFirst, clone the repository:
git clone https://github.com/gethomepage/homepage.gitThen install dependencies and build the production bundle:
pnpm install
pnpm buildIf this is your first time starting, copy the src/skeleton directory to config/ to populate initial example config files.
Finally, run the server in production mode:
pnpm startPlease refer to the homepage documentation website for more information. Everything you need to know about configuring Homepage is there. Please read everything carefully before asking for help, as most questions are answered there or are simple YAML configuration issues.
Install NPM packages, this project uses pnpm (and so should you!):
pnpm installStart the development server:
pnpm devOpen http://localhost:3000 to start.
This is a Next.js application, see their documentation for more information.
The homepage documentation is available at https://gethomepage.dev/.
Homepage uses Material for MkDocs for documentation. To run the documentation locally, first install the dependencies:
pip install -r requirements.txtThen run the development server:
mkdocs serve # or build, to build the static siteIf you have any questions, suggestions, or general issues, please start a discussion on the Discussions page.
In addition to the docs, the troubleshooting guide can help reveal many basic config or network issues. If you're having a problem, it's a good place to start.
Contributions are welcome! Please see the CONTRIBUTING.md file for more information.
Thanks to the over 200 contributors who have helped make this project what it is today!
Especially huge thanks to @shamoon, who has been the backbone of this community from the very start.

