import Link from "next/link"; import { redirect } from "next/navigation"; import { ChartPie, Code2, FileCode2, File, Folder, Ghost, GitBranch, GitCommitHorizontal, GitFork, GitPullRequest, History, KeyRound, Lock, MessageSquare, Package, Star, Terminal, Webhook, } from "lucide-react"; import { ThemePicker } from "@/components/theme-picker"; import { Button } from "@/components/ui/button"; import { Badge } from "@/components/ui/badge"; import { languageColor } from "@ghost/languages"; import { getServerSession } from "@/lib/api/server"; import { API_URL } from "@/lib/env"; const FEATURES = [ { icon: Terminal, title: "Push and pull over HTTP", description: "A real git remote. Clone, fetch and push with the git you already have - no client, no daemon, no extra port.", }, { icon: GitPullRequest, title: "Pull requests, reviewed and merged", description: "Compare two branches, read the diff file by file, talk it through in the thread, and merge server-side when it is ready.", }, { icon: MessageSquare, title: "Issues with labels and assignees", description: "Threads on a repository, filtered by state, label, author or assignee, with a timeline that records every close, reopen and label change.", }, { icon: FileCode2, title: "Read your code in the browser", description: "Syntax highlighting for 300+ languages, READMEs rendered in every directory, images and PDFs in place, raw downloads for the rest.", }, { icon: History, title: "Commit context on every row", description: "Directory listings show the newest commit touching each entry, indexed up front instead of walked per request.", }, { icon: ChartPie, title: "Language breakdown", description: "Bytes per language, counted from the tree rather than by reading files, so it stays fast on a repository with years of history.", }, { icon: GitFork, title: "Forks and stars", description: "Fork any repository you can read, star the ones worth coming back to, and see who else did from the repository page.", }, { icon: Lock, title: "Private by choice", description: "Public repositories are readable by anyone; private ones stay invisible to everyone but you, over HTTP and the web alike.", }, { icon: Ghost, title: "Durable by design", description: "Every push is appended to a write-ahead log in object storage. Local disk is only a cache, so a repository can be rebuilt wherever it is next needed.", }, ]; const PREVIEW_ENTRIES = [ { type: "tree", name: "apps", message: "split the api and the web app", age: "2 hours ago", }, { type: "tree", name: "packages", message: "share the database schema", age: "2 days ago", }, { type: "blob", name: "README.md", message: "explain what this is", age: "5 days ago", }, { type: "blob", name: "package.json", message: "bump the workspace", age: "last week", }, ]; const PREVIEW_LANGUAGES = [ { language: "TypeScript", percent: 71.2 }, { language: "Rust", percent: 18.4 }, { language: "CSS", percent: 6.9 }, { language: "Shell", percent: 3.5 }, ]; const FAQ = [ { question: "Does it work with the git I already have?", answer: "Yes. A Ghost repository is a plain HTTP remote, so clone, fetch, pull and push all work with stock git. There is nothing to install and no plugin to add.", }, { question: "Can repositories be private?", answer: "Every repository is public or private, and a private one is invisible to everyone but its owner - over HTTP and in the browser alike. Visibility is checked on the way in, not hidden in the interface.", }, { question: "How do accounts work?", answer: "Sign up with an email address and a password, pick a username, and your repositories live under it. That username is the first part of every clone URL.", }, { question: "What happens with large files?", answer: "Files past a megabyte are not rendered in the browser, but they download in full at their original size. Git LFS is not supported yet.", }, { question: "Is it ready for a team?", answer: "Issues and pull requests are both here: open a request from a branch, read the diff, review it in the thread and merge it from the page. What is still missing for a team is SSH access and webhooks.", }, { question: "Can I fork someone else's repository?", answer: "Any repository you can read, yes. The fork keeps its own history from the moment you make it, and the original keeps a link back from its page.", }, { question: "What does it take to run?", answer: "An API process, a web app, a PostgreSQL database and an S3-compatible bucket. The bucket holds the write-ahead log that every repository is replayed from; the git directories on disk are a cache you can throw away.", }, ]; const STEPS = [ { title: "Create a repository", description: "Name it. Public or private. It exists as a bare repository the moment you press create.", }, { title: "Add it as a remote", description: "The repository page hands you the clone URL, ready to paste into the project you already have.", }, { title: "Push", description: "Your files, branches and history show up in the browser as soon as the push lands.", }, ]; const STACK = [ "Next.js", "NestJS", "PostgreSQL", "Drizzle", "S3-compatible storage", ]; const ROADMAP = [ { icon: KeyRound, title: "SSH access", description: "git over SSH with your own keys, served by a dedicated process rather than bolted onto the API.", status: "Next", }, { icon: Webhook, title: "Webhooks", description: "Push events posted to a URL you own - the hook every CI runner is waiting for.", status: "Planned", }, { icon: Package, title: "Large files", description: "Git LFS, so a repository that carries binaries is as ordinary as one that does not.", status: "Planned", }, ]; export default async function LandingPage() { const session = await getServerSession(); if (session) redirect("/dashboard"); return (
Ghost
Self-hosted git, without the weight

Your repositories, on your own machine

Ghost is a git host you can run yourself. Push over HTTP, read your code, open issues, review pull requests - and nothing you did not ask for.

push an existing repository 
              
                $ 
                git remote add origin {API_URL}/you/project.git{"\n"}
                $ 
                git push -u origin main

A repository, the way you expect to read one

Directories first, the latest commit against every row, and the languages, stars and forks of the repository beside it.

{/* the repository page in miniature, down to the sidebar it now has */}
main Code
serve raw file contents a3f19c2
    {PREVIEW_ENTRIES.map((entry) => (
  • {entry.type === "tree" ? ( ) : ( )} {entry.name} {entry.message} {entry.age}
    • ))}
{/* plain, like the real sidebar: a second card here would read as a panel bolted onto the listing */}
{FEATURES.map(({ icon: Icon, title, description }) => (

{title}

{description}

))}

Three commands from empty to hosted

No setup wizard, no config file, no CI to configure before the first push works.

    {STEPS.map(({ title, description }, index) => (
  1. {index + 1}

    {title}

    {description}

    2. ))}
Running on {STACK.map((item) => ( {item} ))}

What comes next

Issues, pull requests, forks and stars are done. These are not, and they are being built in roughly this order.

    {ROADMAP.map(({ icon: Icon, title, description, status }) => (

  • {title}

    {status}

    {description}

    • ))}

Questions worth asking first

{FAQ.map(({ question, answer }) => (

{question}

{answer}

))}

Start with one repository

Create an account, add a remote, push. Everything else can wait until you need it.

); }