Downloads of v 14.3.0:


Last Update:

22 Sep 2021

Package Maintainer(s):

Software Author(s):

  • Gitlab


admin cli foss git cross-platform build docker shell gitlab

Gitlab Runner

This is not the latest version of Gitlab Runner available.

  • 1
  • 2
  • 3

14.3.0 | Updated: 22 Sep 2021



Downloads of v 14.3.0:



Software Author(s):

  • Gitlab

  • 1
  • 2
  • 3
Gitlab Runner 14.3.0

This is not the latest version of Gitlab Runner available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


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


Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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 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. Copy Your Script

choco upgrade gitlab-runner -y --source="'INTERNAL REPO URL'" --version="'14.3.0'" [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 gitlab-runner -y --source="'INTERNAL REPO URL'" --version="'14.3.0'" 

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

Exit $exitCode

- name: Install gitlab-runner
    name: gitlab-runner
    version: '14.3.0'
    state: present

See docs at

chocolatey_package 'gitlab-runner' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '14.3.0'

See docs at

cChocoPackageInstaller gitlab-runner
    Name     = "gitlab-runner"
    Version  = "14.3.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'gitlab-runner':
  ensure   => '14.3.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 22 Sep 2021.


GitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. It is used in conjunction with GitLab CI, the open-source continuous integration service included with GitLab that coordinates the jobs.


  • Allows to run:
    • multiple jobs concurrently
    • use multiple tokens with multiple server (even per-project)
    • limit number of concurrent jobs per-token
  • Jobs can be run:
    • locally
    • using Docker containers
    • using Docker containers and executing job over SSH
    • using Docker containers with autoscaling on different clouds and virtualization hypervisors
    • connecting to remote SSH server
  • Is written in Go and distributed as single binary without any other requirements
  • Supports Bash, Windows Batch and Windows PowerShell
  • Works on GNU/Linux, OS X and Windows (pretty much anywhere you can run Docker)
  • Allows to customize the job running environment
  • Automatic configuration reload without restart
  • Easy to use setup with support for Docker, Docker-SSH, Parallels or SSH running environments
  • Enables caching of Docker containers
  • Easy installation as a service for GNU/Linux, OSX and Windows
  • Embedded Prometheus metrics HTTP server

Package parameters

  • /InstallDir - Installation directory. If the Gitlab Runner is already installed, its current directory will be used. To install to a new directory, uninstall it first.
  • /Service - Install as a service. If value is not specified system account will be used. If value is specified it is in the form of Username:Password. The installer will create that user if it doesn't exist, add it to local administrators group, enable ServiceLogonRight and disable password expiration. Example: /Service:gitlab-runner:[email protected]. Can't be used with Autologon parameter
  • /Autologon - Use autologon feature of Windows. Can't be used with Service parameter. Username and password must be provided. Example: /Autologon:gitlab-runner:[email protected].


  • The script register_example.ps1 is provided along the executable which can be used to quickly register runner non-interactively. If you want to use it, rename it to register.ps1 and set desired environment variables.
  • Autologon vs Service: Services do not have access to all Windows features and some scripts, particularly those that depend on GUI, are not usable.

The MIT License (MIT)

Copyright (c) 2015-2017 GitLab B.V.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.


Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to


   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: D634E4BE9B835C11E5918927435C86720502E994291189A1B56E7981C3412420
   checksum64: 07138DC30EE6A9C4AD42378B0B70A1DE7BF4A3B72A59BD36F7920E4FC4835D7D

File 'license.txt' is obtained from:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="">
    <Principal id="Author">
  <Actions Context="Author">
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

$pp = Get-PackageParameters

$current_dir = Get-RunnerInstallDir
if ($current_dir) {
    Write-Host 'Using previous gitlab-runner install path:' $current_dir
    $pp.InstallDir = $current_dir
} else {
    if (!$pp.InstallDir) { $pp.InstallDir = "c:\gitlab-runner" }
    Write-Host 'Using install directory:' $pp.InstallDir
$installDir = $pp.InstallDir

$is64 = (Get-ProcessorBits 64) -and $env:chocolateyForceX86 -ne 'true'
$runner_embedded = if ($is64) { Write-Host "Installing x64 bit version"; Get-Item $toolsPath\*_x64.exe } else { Write-Host "Installing x32 bit version"; Get-Item $toolsPath\*_x32.exe }

Write-Host "Stopping executing runner"
Get-Service gitlab-runner -ea 0 | Stop-Service
Get-Process gitlab-runner -ea 0 | Stop-Process
Start-Sleep 2

Write-Host "Copying files to $installDir"
New-Item -ItemType Directory $installDir -ea 0 | Out-Null
Move-Item $runner_embedded, $toolsPath\register_example.ps1 $installDir -Force
ls $toolsPath\*.exe | % { Remove-Item $_ -ea 0; if (Test-Path $_) { touch "$_.ignore" }}
Move-Item $installDir\gitlab*.exe $installDir\gitlab-runner.exe -Force

$runner_path = Join-Path $installDir 'gitlab-runner.exe'
Install-BinFile gitlab-runner $runner_path

if ($pp.Service) {
    if ($pp.Autologon) { throw 'Autologon and Service parameters are mutually exclusive' }

    if ($pp.Service -is [string]) {
        $Username, $Password = $pp.Service -split ':'
        if (!$Password) { throw 'When specifying service user, password is required' }

    if (!(Get-Service gitlab-runner -ea 0)) {
        Write-Host "Installing gitlab-runner service"
        $cmd = @("install")
        if ($Username) {
            Add-User $Username $Password
            Add-ServiceLogonRight $Username
            $cmd += " --user", "$Env:COMPUTERNAME\$Username", "--password", $Password
            $cmd += " --working-directory", $installDir, "--config", "$installDir\config.toml"

        $ErrorActionPreference = 'Continue'
        & $runner_path $cmd
        $ErrorActionPreference = 'Stop'
    } else { Write-Host "Service gitlab-runner already installed" }

    Write-Host "Starting service"
    Start-Service gitlab-runner
    Get-Service gitlab-runner

if ($pp.Autologon) {
    if ($pp.Service) { throw 'Autologon and Service parameters are mutually exclusive' }

    $Username, $Password = $pp.Autologon -split ':'
    if (!$Password) { throw 'When specifying autologon user, password is required' }

    Add-User $Username $Password

    Write-Host "Setting autologon for $Username"
    Set-AutoLogon $Username $Password

    Write-Host "Creating logon script: $installDir\autologon.bat"
    "cd ""$installDir""`n" +
    """$installDir\gitlab-runner.exe"" run" | Out-File $installDir\autologon.bat -Encoding ascii

    Write-Host "Creating scheduled task: autologon"
    [xml] $xml = gc $toolsPath\autologon.xml -Encoding Ascii
    $xml.Task.RegistrationInfo.Author       = "$Env:COMPUTERNAME\$Env:USERNAME"
    $xml.task.Triggers.LogonTrigger.UserId  = "$Env:COMPUTERNAME\$Username"
    $xml.task.Principals.Principal.UserId   = "$Env:COMPUTERNAME\$Username"
    $xml.task.Actions.Exec.Command          = "$installDir\autologon.bat"
    $xml.Save( "$toolsPath\autologon.xml" )

    schtasks.exe /Create /XML "$toolsPath\autologon.xml" /Tn autologon /F
    if ($LASTEXITCODE) { throw "Scheduled task not created ($LastExitCode)" }
$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

if (Get-Service gitlab-runner -ea 0) {
    gitlab-runner.exe stop
    gitlab-runner.exe uninstall

$installDir = Get-RunnerInstallDir

Write-Warning 'If a gitlab-runner user is created during the installation, it is not removed as a safety measure'
Write-Warning '  to remove it execute: net user gitlab-runner /delete'
Write-Warning 'If Autologon parameter was used when installing, disable autolog manually'

# It might not be safe to just rm -Force -Recursive, let the user do it manually.
if ($installDir) {
    Write-Warning "Gitlab-runner remained installed in $installDir"
    Write-Warning "  to delete it execute: rm '$installDir' -Force -Recurse"
} else {
    Write-Warning "Can't find gitlab-runner installation directory, please remove it manually"
md5: 8CEA6FE543520EF65A11D473AD973A89 | sha1: B11132CEA0DEE4197C331E535681BEACB0B1ED43 | sha256: D634E4BE9B835C11E5918927435C86720502E994291189A1B56E7981C3412420 | sha512: E87BA2D706BD31FDA6F9DD45CE6025A97642BC7FF038608C27BB628E69789CF6994E766312DA1DE5B8503579BF58FD58DD9E70656ADF14187C9D17D2D3E9C0B5
md5: 33A74875D5C34E6E6E5F2995A7B5B8BD | sha1: D897F6BFB7451324086A3DB4E34FE72D517B0847 | sha256: 07138DC30EE6A9C4AD42378B0B70A1DE7BF4A3B72A59BD36F7920E4FC4835D7D | sha512: 911E0399D07170DAE96504B43E295E9FA11C0AAD0010EC6F04DF215683690623CC3AFAC810813DE9C6B0A9C3DBF8DC020AE05736FBB2A300FE6854DDA74F0DF6
function Get-RunnerInstallDir() {
    $res = Get-WmiObject win32_service | ? {$_.Name -eq 'gitlab-runner'} | select -Expand PathName
    if (!$res) { 
        if (!(gcm gitlab-runner.exe -ea 0)) { return }
        $res = (gitlab-runner.exe --shimgen-help 2>&1) -match '^\s*Target:' -replace "Target:|'"
        $res = $res.Trim()
    $res = $res -split '\\gitlab-runner.exe' | select -First 1
    if (Test-Path $res) { return $res }

function Add-ServiceLogonRight([string] $Username) {
    Write-Host "Enable ServiceLogonRight for $Username"
    $tmp = [System.IO.Path]::GetTempFileName()
    secedit /export /cfg "$tmp.inf" | Out-Null
    (gc -Encoding ascii "$tmp.inf") -replace '^SeServiceLogonRight .+', "`$0,$Username" | sc -Encoding ascii "$tmp.inf"
    secedit /import /cfg "$tmp.inf" /db "$tmp.sdb" | Out-Null
    secedit /configure /db "$tmp.sdb" /cfg "$tmp.inf" | Out-Null
    rm $tmp* -ea 0

function Add-User([string] $Username, [string] $Password ) {
    $user = Get-WmiObject win32_useraccount -Filter { LocalAccount = 'true' } | ? { $_.Name -eq $Username }
    if ($user) { Write-Host "User $Username already exists"; return } 

    Write-Host "Creating user $Username as local administrator"
    net user $Username $Password /add | Out-Null
    net localgroup Administrators $Username /add | Out-NUll
    $user = Get-WmiObject win32_useraccount -Filter { LocalAccount = 'true' } | ? { $_.Name -eq $Username }
    $user.PasswordExpires = $false

# Author: Miodrag Milic <[email protected]>
# Last Change: 23-Jun-2016.

    Set Windows to automatically login as given user after restart and eventually execute a script

    Enable AutoLogon next time when the server reboots.
    It can trigger a specific Script to execute after the server is back online after Auto Logon.

    Set-AutoLogon -Username "domain\user" -Password "my password"

    Set-AutoLogon -Username "domain\user" -Password "my password" -LogonCount 3

    Set-AutoLogon -Username "domain\user" -Password "my password" -Script "c:\test.bat"
function Set-AutoLogon {
        #Provide the username that the system would use to login.

        #Provide the Password for the User provided.

        #Sets the number of times the system would reboot without asking for credentials, by default 100000.

        #Script: Provide Full path of the script for execution after server reboot

    $ErrorActionPreference = 'Stop'

    $RegPath   = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"
    $RegROPath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce"

    Set-ItemProperty $RegPath "AutoAdminLogon"  -Value 1
    Set-ItemProperty $RegPath "DefaultUsername" -Value $Username
    Set-ItemProperty $RegPath "DefaultPassword" -Value $Password
    #Set-ItemProperty $RegPath "DefaultDomain" -Value $Env:USERDOMAIN

    $v = if ($LogonCount)  { $LogonCount } else { '' }
    Set-ItemProperty $RegPath "AutoLogonCount" -Value $v -Type DWord

    $v = if ($Script)  { $Script } else { '' }
    Set-ItemProperty $RegROPath "Set-Autologon" -Value $v
    Rename this file to register.ps1 or it will get overwritten by the future updates.
    For the list of all environment vars run `gitlab-runner register --help`.
    After registration, config.toml is generated and subsequent configuration changes should
    be set in that file. Gitlab-Runner automatically picks up config.toml changes while executing.

$Env:RUNNER_NAME                = $env:COMPUTERNAME
$Env:REGISTRATION_TOKEN         = ''
$Env:CI_SERVER_URL              = ''
$Env:RUNNER_TAG_LIST            = ''        #comma separated list of tags

$Env:CONFIG_FILE                = "$PSScriptRoot\config.toml"
$Env:REGISTER_RUN_UNTAGGED      = 'false'
$Env:REGISTER_LOCKED            = $false    #lock runner to current project 
$Env:RUNNER_EXECUTOR            = 'shell'
$Env:RUNNER_SHELL               = 'powershell'

$Env:RUNNER_BUILDS_DIR          = ''
$Env:RUNNER_CACHE_DIR           = ''

gitlab-runner register --non-interactive

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
Gitlab Runner 15.5.0 11206 Sunday, October 23, 2022 Approved
Gitlab Runner 15.4.0 1806 Thursday, September 22, 2022 Approved
Gitlab Runner 15.3.0 1865 Saturday, August 20, 2022 Approved
Gitlab Runner 15.2.0 933 Tuesday, August 9, 2022 Approved
Gitlab Runner 15.1.0 1701 Tuesday, June 21, 2022 Approved
Gitlab Runner 15.0.0 1291 Friday, May 20, 2022 Approved
Gitlab Runner 14.10.0 1510 Tuesday, April 19, 2022 Approved
Gitlab Runner 14.9.0 1355 Tuesday, March 22, 2022 Approved
Gitlab Runner 14.8.0 1087 Tuesday, February 22, 2022 Approved
Gitlab Runner 14.7.0 1062 Thursday, January 20, 2022 Approved
Gitlab Runner 14.6.0 1389 Saturday, December 18, 2021 Approved
Gitlab Runner 14.5.0 1245 Monday, November 22, 2021 Approved
Gitlab Runner 14.4.0 1022 Tuesday, October 26, 2021 Approved
Gitlab Runner 14.3.0 1054 Wednesday, September 22, 2021 Approved
Gitlab Runner 14.2.0 1123 Saturday, August 28, 2021 Approved
Gitlab Runner 14.0.0 2053 Sunday, June 20, 2021 Approved
Gitlab Runner 13.12.0 2713 Friday, May 21, 2021 Approved
Gitlab Runner 13.11.0 973 Wednesday, April 21, 2021 Approved
Gitlab Runner 13.10.0 1611 Monday, March 22, 2021 Approved
Gitlab Runner 13.9.0 1254 Tuesday, February 23, 2021 Approved
Gitlab Runner 13.8.0 1695 Thursday, January 21, 2021 Approved
Gitlab Runner 13.7.0 1368 Tuesday, December 22, 2020 Approved
Gitlab Runner 637 Saturday, December 5, 2020 Approved
Gitlab Runner 13.6.0 962 Sunday, November 22, 2020 Approved
Gitlab Runner 13.5.0 9114 Wednesday, October 21, 2020 Approved
Gitlab Runner 13.4.0 194 Saturday, September 19, 2020 Approved
Gitlab Runner 13.3.0 3183 Friday, August 21, 2020 Approved
Gitlab Runner 13.2.0 1589 Monday, July 20, 2020 Approved
Gitlab Runner 13.1.0 1377 Saturday, June 20, 2020 Approved
Gitlab Runner 13.0.1 1163 Monday, June 1, 2020 Approved
Gitlab Runner 13.0.0 769 Thursday, May 21, 2020 Approved
Gitlab Runner 12.10.0 2768 Wednesday, April 22, 2020 Approved
Gitlab Runner 12.9.0 688 Tuesday, April 14, 2020 Approved
Gitlab Runner 12.8.0 2429 Sunday, February 23, 2020 Approved
Gitlab Runner 12.7.1 1067 Friday, January 24, 2020 Approved
Gitlab Runner 12.7.0 242 Tuesday, January 21, 2020 Approved
Gitlab Runner 12.6.0 506 Tuesday, December 24, 2019 Approved
Gitlab Runner 12.5.0 1010 Thursday, November 21, 2019 Approved
Gitlab Runner 12.4.1 1023 Tuesday, October 29, 2019 Approved
Gitlab Runner 12.4.0 448 Tuesday, October 22, 2019 Approved
Gitlab Runner 12.3.0 2128 Saturday, September 21, 2019 Approved
Gitlab Runner 12.2.0 1197 Friday, August 23, 2019 Approved
Gitlab Runner 12.1.0 1045 Saturday, July 20, 2019 Approved
Gitlab Runner 12.0.0 1596 Saturday, June 22, 2019 Approved
Gitlab Runner 11.11.2 790 Tuesday, June 4, 2019 Approved
Gitlab Runner 11.11.0 450 Tuesday, May 21, 2019 Approved
Gitlab Runner 11.10.0 829 Saturday, April 20, 2019 Approved
Gitlab Runner 11.9.0 646 Saturday, March 23, 2019 Approved
Gitlab Runner 11.8.0 832 Saturday, February 23, 2019 Approved
Gitlab Runner 11.7.0 953 Tuesday, January 22, 2019 Approved
Gitlab Runner 11.6.0 321 Friday, January 18, 2019 Approved
Gitlab Runner 11.4.0 1420 Monday, October 22, 2018 Approved
Gitlab Runner 11.4.0-rc1 250 Thursday, October 11, 2018 Exempted
Gitlab Runner 11.3.0 790 Saturday, September 22, 2018 Approved
Gitlab Runner 11.3.0-rc1 262 Wednesday, September 12, 2018 Exempted
Gitlab Runner 11.2.0 695 Thursday, August 23, 2018 Approved
Gitlab Runner 11.2.0-rc1 248 Thursday, August 9, 2018 Approved
Gitlab Runner 11.1.0 709 Monday, July 23, 2018 Approved
Gitlab Runner 11.1.0-rc1 303 Saturday, July 14, 2018 Approved
Gitlab Runner 11.0.0 895 Saturday, June 23, 2018 Approved
Gitlab Runner 11.0.0-rc1 337 Wednesday, June 13, 2018 Approved
Gitlab Runner 10.8.0 785 Wednesday, May 23, 2018 Approved
Gitlab Runner 10.8.0-rc1 400 Friday, May 11, 2018 Approved
Gitlab Runner 10.7.0-rc1 464 Thursday, April 12, 2018 Approved
Gitlab Runner 10.6.0 1090 Friday, March 23, 2018 Approved
Gitlab Runner 10.6.0-rc1 387 Friday, March 9, 2018 Approved
Gitlab Runner 10.5.0 624 Friday, February 23, 2018 Approved
Gitlab Runner 10.5.0-rc1 408 Friday, February 9, 2018 Approved
Gitlab Runner 10.4.0 628 Monday, January 22, 2018 Approved
Gitlab Runner 10.4.0-rc1 476 Tuesday, January 9, 2018 Approved
Gitlab Runner 10.3.0 669 Saturday, December 23, 2017 Approved
Gitlab Runner 10.3.0-rc1 435 Monday, December 11, 2017 Approved
Gitlab Runner 10.2.0 768 Thursday, November 23, 2017 Approved
Gitlab Runner 10.2.0-rc1 429 Saturday, November 11, 2017 Approved
Gitlab Runner 10.1.0 895 Sunday, October 22, 2017 Approved
Gitlab Runner 10.1.0-rc1 467 Tuesday, October 10, 2017 Approved
Gitlab Runner 10.0.0-rc1 402 Tuesday, September 26, 2017 Approved
Gitlab Runner 9.5.0 1052 Wednesday, August 23, 2017 Approved
Gitlab Runner 9.4.0 677 Sunday, July 23, 2017 Approved
Gitlab Runner 9.3.0 489 Thursday, June 22, 2017 Approved
Gitlab Runner 9.2.1 377 Saturday, June 17, 2017 Approved
Gitlab Runner 9.2.0 453 Monday, May 22, 2017 Approved
Gitlab Runner 9.1.1 382 Wednesday, May 3, 2017 Approved
Gitlab Runner 9.1.0 402 Monday, April 24, 2017 Approved
Gitlab Runner 9.0.0 416 Thursday, March 30, 2017 Approved
Discussion for the Gitlab Runner Package

Ground Rules:

  • This discussion is only about Gitlab Runner and the Gitlab Runner 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 Gitlab Runner, 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