Merge branch 'feat/blog-news' into feat/gemini-output
All checks were successful
check / check (pull_request) Successful in 30s
All checks were successful
check / check (pull_request) Successful in 30s
This commit is contained in:
commit
faff6476ab
1 changed files with 688 additions and 48 deletions
|
|
@ -11,12 +11,15 @@ motorino build -site DIR -out DIR build the site in DIR into the output folde
|
|||
motorino build -drafts ... the same, with the drafts and the posts dated in the future, for a preview
|
||||
motorino gemini -site DIR -out DIR write the same site as gemtext, for a Gemini server (defaults: . and capsule)
|
||||
motorino gemini -lang CODE ... the language at the root of the capsule; -drafts works as for build
|
||||
motorino build -clean ... empty the output folder first, if it is new, empty or holds .motorino-out
|
||||
motorino new -site DIR "A title" write news/a-title.md, a draft with the header ready, and print its path
|
||||
motorino version print the version
|
||||
```
|
||||
|
||||
The binary is a single static Go program. The version comes from semantic-release.
|
||||
|
||||
A build writes the files it makes and leaves the others in the output folder, so the pages of a list that got shorter (`news/page/3/`) stay behind. When that happens the command prints a warning that names the old files. The deploy never has them: it builds into a new folder and publishes it with `rsync --delete`. For a folder you reuse, `-clean` empties it first. It does that only for a folder that is new, empty or holds the `.motorino-out` file that an earlier `-clean` left, never for any other folder with files in it and never for the folder of the site or one that holds it. A build without `-clean` writes no extra file.
|
||||
|
||||
## What a site looks like
|
||||
|
||||
```
|
||||
|
|
|
|||
Loading…
Reference in a new issue