hugo -h hugo --help hugo help
The static site generator
Hugo
is a command-line app
that you communicate with
through
configuration files,
environment variables,
and
its help
subcommand,
the
-h
--help
hugo config mounts
hugo deploy
hugo mod
(and subcommands)
hugo list all
--ignoreVendor
--path-warnings
For details and more complete lists of changes throughout the history of Hugo, see:
To get help about Hugo’s top-level command-line arguments, run any of the following three equivalent commands at a command-line prompt.
hugo -h hugo --help hugo help
Below is what Hugo v0.80.0 displays.
hugo is the main command, used to build your Hugo site. Hugo is a Fast and Flexible Static Site Generator built with love by spf13 and friends in Go. Complete documentation is available at http://gohugo.io/. Usage: hugo [flags] hugo [command] Available Commands: config Print the site configuration convert Convert your content to different formats deploy Deploy your site to a Cloud provider. env Print Hugo version and environment info gen A collection of several useful generators. help Help about any command import Import your site from others. list Listing out various types of content mod Various Hugo Modules helpers. new Create new content for your site server A high performance webserver version Print the version number of Hugo Flags: -b, --baseURL string hostname (and path) to the root, e.g. http://spf13.com/ -D, --buildDrafts include content marked as draft -E, --buildExpired include expired content -F, --buildFuture include content with publishdate in the future --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache/ --cleanDestinationDir remove files from destination not found in static directories --config string config file (default is path/config.yaml|json|toml) --configDir string config dir (default "config") -c, --contentDir string filesystem path to content directory --debug debug output -d, --destination string filesystem path to write files to --disableKinds strings disable different kind of pages (home, RSS etc.) --enableGitInfo add Git revision, date and author info to the pages -e, --environment string build environment --forceSyncStatic copy all files when static is changed. --gc enable to run some cleanup tasks (remove unused cache files) after the build -h, --help help for hugo --i18n-warnings print missing translations --ignoreCache ignores the cache directory --ignoreVendor ignores any _vendor directory --ignoreVendorPaths string ignores any _vendor for module paths matching the given Glob pattern -l, --layoutDir string filesystem path to layout directory --log enable Logging --logFile string log File path (if set, logging enabled automatically) --minify minify any supported output format (HTML, XML etc.) --noChmod don't sync permission mode of files --noTimes don't sync modification time of files --path-warnings print warnings on duplicate target paths etc. --print-mem print memory usage to screen at intervals --quiet build in quiet mode --renderToMemory render to memory (only useful for benchmark testing) -s, --source string filesystem path to read files relative from --templateMetrics display metrics about template executions --templateMetricsHints calculate some improvement hints when combined with --templateMetrics -t, --theme strings themes to use (located in /themes/THEMENAME/) --themesDir string filesystem path to themes directory --trace file write trace to file (not useful in general) -v, --verbose verbose output --verboseLog verbose logging -w, --watch watch filesystem for changes and recreate as needed Additional help topics: hugo check Contains some verification checks Use "hugo [command] --help" for more information about a command.
An example of running hugo
with no command-line arguments is in
Infinite Ink’s
Hugo Tutorial: Themeless & Gitless Introduction to the Hugo Static Site Generator
in these steps:
Some useful hugo
flags are discussed in these steps:
To get help about
hugo server
command-line arguments, run
any of the following three
equivalent commands
at a command-line prompt.
hugo server -h hugo server --help hugo help server
Below is what Hugo v0.80.0 displays.
Hugo provides its own webserver which builds and serves the site. While hugo server is high performance, it is a webserver with limited options. Many run it in production, but the standard behavior is for people to use it in development and use a more full featured server such as Nginx or Caddy. 'hugo server' will avoid writing the rendered and served content to disk, preferring to store it in memory. By default hugo will also watch your files for any changes you make and automatically rebuild the site. It will then live reload any open browser pages and push the latest content to them. As most Hugo sites are built in a fraction of a second, you will be able to save and see your changes nearly instantly. Usage: hugo server [flags] Aliases: server, serve Flags: --appendPort append port to baseURL (default true) -b, --baseURL string hostname (and path) to the root, e.g. http://spf13.com/ --bind string interface to which the server will bind (default "127.0.0.1") -D, --buildDrafts include content marked as draft -E, --buildExpired include expired content -F, --buildFuture include content with publishdate in the future --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache/ --cleanDestinationDir remove files from destination not found in static directories -c, --contentDir string filesystem path to content directory -d, --destination string filesystem path to write files to --disableBrowserError do not show build errors in the browser --disableFastRender enables full re-renders on changes --disableKinds strings disable different kind of pages (home, RSS etc.) --disableLiveReload watch without enabling live browser reload on rebuild --enableGitInfo add Git revision, date and author info to the pages --forceSyncStatic copy all files when static is changed. --gc enable to run some cleanup tasks (remove unused cache files) after the build -h, --help help for server --i18n-warnings print missing translations --ignoreCache ignores the cache directory -l, --layoutDir string filesystem path to layout directory --liveReloadPort int port for live reloading (i.e. 443 in HTTPS proxy situations) (default -1) --meminterval string interval to poll memory usage (requires --memstats), valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". (default "100ms") --memstats string log memory usage to this file --minify minify any supported output format (HTML, XML etc.) --navigateToChanged navigate to changed content file on live browser reload --noChmod don't sync permission mode of files --noHTTPCache prevent HTTP caching --noTimes don't sync modification time of files --path-warnings print warnings on duplicate target paths etc. -p, --port int port on which the server will listen (default 1313) --print-mem print memory usage to screen at intervals --renderToDisk render to Destination path (default is render to memory & serve from there) --templateMetrics display metrics about template executions --templateMetricsHints calculate some improvement hints when combined with --templateMetrics -t, --theme strings themes to use (located in /themes/THEMENAME/) --trace file write trace to file (not useful in general) -w, --watch watch filesystem for changes and recreate as needed (default true) Global Flags: --config string config file (default is path/config.yaml|json|toml) --configDir string config dir (default "config") --debug debug output -e, --environment string build environment --ignoreVendor ignores any _vendor directory --ignoreVendorPaths string ignores any _vendor for module paths matching the given Glob pattern --log enable Logging --logFile string log File path (if set, logging enabled automatically) --quiet build in quiet mode -s, --source string filesystem path to read files relative from --themesDir string filesystem path to themes directory -v, --verbose verbose output --verboseLog verbose logging
To get help about
hugo new
command-line arguments, run
any of the following three
equivalent commands
at a command-line prompt.
hugo new -h hugo new --help hugo help new
Below is what Hugo v0.80.0 displays.
Create a new content file and automatically set the date and title. It will guess which kind of file to create based on the path provided. You can also specify the kind with `-k KIND`. If archetypes are provided in your theme or site, they will be used. Ensure you run this within the root directory of your site. Usage: hugo new [path] [flags] hugo new [command] Available Commands: site Create a new site (skeleton) theme Create a new theme Flags: -b, --baseURL string hostname (and path) to the root, e.g. http://spf13.com/ -D, --buildDrafts include content marked as draft -E, --buildExpired include expired content -F, --buildFuture include content with publishdate in the future --cacheDir string filesystem path to cache directory. Defaults: $TMPDIR/hugo_cache/ --cleanDestinationDir remove files from destination not found in static directories -c, --contentDir string filesystem path to content directory -d, --destination string filesystem path to write files to --disableKinds strings disable different kind of pages (home, RSS etc.) --editor string edit new content with this editor, if provided --enableGitInfo add Git revision, date and author info to the pages --forceSyncStatic copy all files when static is changed. --gc enable to run some cleanup tasks (remove unused cache files) after the build -h, --help help for new --i18n-warnings print missing translations --ignoreCache ignores the cache directory -k, --kind string content type to create -l, --layoutDir string filesystem path to layout directory --minify minify any supported output format (HTML, XML etc.) --noChmod don't sync permission mode of files --noTimes don't sync modification time of files --path-warnings print warnings on duplicate target paths etc. --print-mem print memory usage to screen at intervals --templateMetrics display metrics about template executions --templateMetricsHints calculate some improvement hints when combined with --templateMetrics -t, --theme strings themes to use (located in /themes/THEMENAME/) --trace file write trace to file (not useful in general) Global Flags: --config string config file (default is path/config.yaml|json|toml) --configDir string config dir (default "config") --debug debug output -e, --environment string build environment --ignoreVendor ignores any _vendor directory --ignoreVendorPaths string ignores any _vendor for module paths matching the given Glob pattern --log enable Logging --logFile string log File path (if set, logging enabled automatically) --quiet build in quiet mode -s, --source string filesystem path to read files relative from --themesDir string filesystem path to themes directory -v, --verbose verbose output --verboseLog verbose logging Use "hugo new [command] --help" for more information about a command.
To get help about
hugo list
command-line arguments, run
any of the following three
equivalent commands
at a command-line prompt.
hugo list -h hugo list --help hugo help list
Below is what Hugo v0.80.0 displays.
Listing out various types of content. List requires a subcommand, e.g. `hugo list drafts`. Usage: hugo list [command] Available Commands: all List all posts drafts List all drafts expired List all posts already expired future List all posts dated in the future Flags: -h, --help help for list Global Flags: --config string config file (default is path/config.yaml|json|toml) --configDir string config dir (default "config") --debug debug output -e, --environment string build environment --ignoreVendor ignores any _vendor directory --ignoreVendorPaths string ignores any _vendor for module paths matching the given Glob pattern --log enable Logging --logFile string log File path (if set, logging enabled automatically) --quiet build in quiet mode -s, --source string filesystem path to read files relative from --themesDir string filesystem path to themes directory -v, --verbose verbose output --verboseLog verbose logging Use "hugo list [command] --help" for more information about a command.
More Hugo command-line help
is available at
gohugo.io/commands/
and,
if you have hugo
installed,
at your command line.
To comment, you must be signed in to GitHub.