-
Notifications
You must be signed in to change notification settings - Fork 42
Troubleshooting
These errors are related to hugo
running on. They can be encountered for a
number of reasons, including but not limited to having missing values in the
configuration files ending in .toml
at the root of the project. Because these
commands are wrapped with gulp
they might not show all of the output in the
terminal.
If the gulp build:website
command fails to execute properly, you can try
running the following in the terminal to see the hugo
output.
hugo --config="config.toml" --baseURL="localhost" --destination="tmp/test"
# If that works fine, then run the following command.
hugo --config="config_es.toml" --baseURL="localhost" --destination="tmp/test"
These commands will build the website using the config
file passed in via
--config=""
and will output to the terminal.
Things can go wrong during the deployment phase of the project. We currently use
CircleCI to deploy the website onto cloud.gov
. The CircleCI
service has a feature which allows users to ssh
into the CI server to help
troubleshoot any issues during the CI phase. This is helpful in debugging
deployment issues or build issues for the project.