hugo-deployer-git
Deploy your hugo site using one command
Inspired by hexo-deployer-git.
Installation
pip3 install hugo-deployer-git
Setup
In your config.toml, insert this section with your configs.
[hugo-deployer-git]
# required
repo = "your github page repo"
branch = "master"
# optoinal
name= "haha"
email= "test@testtest.com"
message = ""
build-config= "--minify"
How to use
cd to your hugo project and use hugo-deployer-git.
1 maintainer
Metadata
1 maintainer
Release files for hugo-deployer-git 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hugo-deployer-git-0.0.5.tar.gz | 4.0 kB | Without provenance | Details for hugo-deployer-git-0.0.5.tar.gz |
Release files / hugo-deployer-git-0.0.5.tar.gz
| Download URL | hugo-deployer-git-0.0.5.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e5e1e7b00e46d3221edbc835150b3e365c09ce863210b6d2267105167918a12
|
|
BLAKE2b-256 checksum How to use checksums |
c97ab6b24f510472265755d14ec0d4e7f0a98229310f4307f5d265c25f2d9b7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.7
|
Security for hugo-deployer-git 0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
