fossil-new

View documentation for the original command

$ tldr fossil init

fossil new REPOSITORY_FILE [options]

REPOSITORY_FILE
    The path and filename for the new Fossil repository. This file will be created and must not already exist.

--admin-user USERNAME
    Specifies the initial administrator username for the repository's web interface. If omitted, Fossil will prompt for one or use a default if running non-interactively.

--project-name NAME
    Sets the initial project name. This name is displayed in the repository's web interface.

--description TEXT
    Provides an initial description for the project, which is also visible in the web interface.

--autoonline
    Automatically enables the 'autoonline' setting for the new repository, facilitating automatic synchronization with remote repositories.

--set-date DATETIME
    Sets the initial date and time for the repository. If not specified, the current system time is used.

The fossil-new command is used to create an empty, self-contained Fossil SCM repository file. This command is the essential first step for initiating a new project or managing an existing one under Fossil's version control system. Unlike other SCMs that might create a directory structure, fossil-new generates a single SQLite database file that will store all project history, branches, tags, as well as integrated features like the project wiki, bug tracking system, and forum.

The repository file is designed to be highly portable and robust. After creation, this file serves as the central hub for all version control operations. Users can then 'open' this repository to begin adding source code, commits, and interacting with Fossil's comprehensive web interface.

The fossil-new command will not overwrite an existing file; it will report an error and exit if the specified REPOSITORY_FILE already exists. Users must have appropriate write permissions in the target directory to create the repository file. This command only creates the repository file itself, not a working directory or checkout; additional commands like 'fossil open' or 'fossil clone' are needed to start working with project files.

If the --admin-user option is not provided, fossil-new will interactively prompt the user to enter an administrator username and password unless running in a non-interactive environment.

The newly created repository file is an empty Fossil database. It contains only the necessary schema and initial configuration; no project files or source code are present until they are added and committed using subsequent Fossil commands.

Fossil SCM was created by D. Richard Hipp, the author of SQLite, and first released in 2007. The fossil-new command has been a fundamental part of Fossil since its inception, serving as the primary method for initializing new projects. Its design reflects Fossil's core philosophy of simplicity and self-containment, with the entire repository residing in a single, robust SQLite database file. The command's functionality has remained consistent, underscoring its foundational role in the Fossil ecosystem.

fossil(1), fossil-open(1), fossil-clone(1), fossil-add(1), git-init(1), svnadmin(1)