update deployment environment in params.toml and hugo.toml
Some checks reported warnings
Build and Deploy Hugo Site / buildAndDeploy (push) Has been cancelled
Some checks reported warnings
Build and Deploy Hugo Site / buildAndDeploy (push) Has been cancelled
clarify usage and content update instructions
This commit is contained in:
parent
61cdbc7240
commit
d193a32b7c
3 changed files with 5 additions and 5 deletions
|
|
@ -1,3 +1,7 @@
|
|||
########################### Deployment #############################
|
||||
# set to "development" or "production". This deploys the site to the correct environment and sets the robot.txt to disallow all pages when in development mode.
|
||||
environment = "development"
|
||||
|
||||
#################### default parameters ################################
|
||||
# favicon module: https://github.com/gethugothemes/hugo-modules/tree/master/images#favicon-implementation
|
||||
favicon = "images/verua_fav.png"
|
||||
|
|
|
|||
|
|
@ -18,10 +18,6 @@ disableLanguages = ["en"]
|
|||
hasCJKLanguage = false # If hasCJKLanguage true, auto-detect Chinese/Japanese/Korean Languages in the content. see: https://gohugo.io/getting-started/configuration/#hascjklanguage
|
||||
enableRobotsTXT = true
|
||||
|
||||
########################### Deployment #############################
|
||||
# set to "development" or "production". This deploys the site to the correct environment and sets the robot.txt to disallow all pages when in development mode.
|
||||
[params]
|
||||
environment = "development"
|
||||
|
||||
########################### Services #############################
|
||||
[services]
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Production site: <a target="_blank" href="https://verua.info/" rel="nofollow">ve
|
|||
|
||||
## Usage / Update Content
|
||||
|
||||
To use the theme, you need to clone the repository, update your content in the content folder and push your changes to the main branch.
|
||||
To use the theme, and to update your content, you need to clone the repository, update your content in the content folder and push your changes to the main branch which will trigger a deployment.
|
||||
|
||||
```bash
|
||||
# Clone the repository
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue