gutenberg

0.4.2 | Updated: 11/11/2018

Downloads:

98

Downloads of v 0.4.2:

98

Maintainer(s):

Software Author(s):

  • Vincent Prouillet
  • gutenberg contributors

gutenberg 0.4.2

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install gutenberg, run the following command from the command line or from PowerShell:

>

To upgrade gutenberg, run the following command from the command line or from PowerShell:

>

To uninstall gutenberg, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade gutenberg -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade gutenberg -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure gutenberg installed
  win_chocolatey:
    name: gutenberg
    state: present
    version: 0.4.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'gutenberg' do
  action    :install
  version  '0.4.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: gutenberg,
    Version: 0.4.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller gutenberg
{
   Name     = 'gutenberg'
   Ensure   = 'Present'
   Version  = '0.4.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'gutenberg':
  provider => 'chocolatey',
  ensure   => '0.4.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install gutenberg version="0.4.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 11/12/2018.

Description

Gutenberg

Build Status
Build status

A fast static site generator in a single binary with everything built-in.

Documentation is available on its site or in the docs/content folder of the repository.

Supported content formats

  • Gutenberg: markdown
  • Cobalt: markdown
  • Hugo: markdown, asciidoc, org-mode
  • Pelican: reStructuredText, markdown, asciidoc, org-mode, whatever-you-want

Template engine explanation

Cobalt gets ~ as, while based on Liquid, the Rust library doesn't implement all its features but there is no documentation on what is and isn't implemented. The errors are also cryptic. Liquid itself is not powerful enough to do some of things you can do in Jinja2, Go templates or Tera.

Hugo gets ~. It is probably the most powerful template engine in the list after Jinja2 (hard to beat python code in templates) but personally drives me insane, to the point of writing my own template engine and static site generator. Yes, this is a bit biased.

Pelican notes

Many features of Pelican are coming from plugins, which might be tricky
to use because of version mismatch or lacking documentation. Netlify supports Python
and Pipenv but you still need to install your dependencies manually.

Contributing

As the documentation site is automatically built on commits to master, all development
should happen on the next branch, unless it is fixing the current documentation.

If you want a feature added or modified, please open an issue to discuss it before doing a PR.


tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$packageName= $env:ChocolateyPackageName
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url      = "https://github.com/Keats/gutenberg/releases/download/v$($env:ChocolateyPackageVersion)/gutenberg-v$($env:ChocolateyPackageVersion)-x86_64-pc-windows-msvc.zip"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  url           = $url
  checksum      = 'C18A220CF05AB0AFD1ED22CAA2D2BB6AB7B443E181DE5497524B8C443E57F3A6'
  checksumType  = 'sha256'
}

Install-ChocolateyZipPackage @packageArgs

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

0.4.2 (2018-09-03)

  • Add assets to section indexes
  • Allow users to add custom highlighting syntaxes
  • Add Swift, MiniZinc syntaxes and update others
  • Handle post summaries better: no more cutting references

0.4.1 (2018-08-06)

  • Fix live reload of a section content change getting no pages data
  • Fix critical bug in serve in some OSes
  • Update deps, should now build and work correctly on BSDs

0.4.0 (2018-08-04)

Breaking

  • Taxonomies have been rewritten from scratch to allow custom ones with RSS and pagination
  • order sorting has been removed in favour of only having weight
  • page.next/page.previous have been renamed to page.later/page.earlier and page.heavier/page.lighter depending on the sort method

Others

  • Fix serve not working with the config flag
  • Websocket port on live will not get the first available port instead of a fixed one
  • Rewrite markdown rendering to fix all known issues with shortcodes
  • Add array arguments to shortcodes and allow single-quote/backtick strings
  • Co-located assets are now permalinks
  • Words are now counted using unicode rather than whitespaces
  • Aliases can now be pointing directly to specific HTML files
  • Add year, month and day variables to pages with a date
  • Fix panic when live reloading a change on a file without extensions
  • Add image resizing support
  • Add a 404 template
  • Enable preserve-order feature of Tera
  • Add an external link checker
  • Add get_taxonomy global function to return the full taxonomy

This package has no dependencies.

Discussion for the gutenberg Package

Ground Rules:

  • This discussion is only about gutenberg and the gutenberg package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or gutenberg, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus