We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't this line: https://github.com/docksal/boilerplate-hugo/blob/master/.docksal/docksal.yml#L23 have to resolve to a tag in here somewhere: https://hub.docker.com/r/docksal/cli/tags?page=1&name=hugo
I don't see how this resolves since there are no "hugo" labeled tags:
image: docksal/cli:hugo-0.34
We should also update it to tag https://github.com/gohugoio/hugo/releases/tag/v0.96.0 much like this PR does https://github.com/docksal/boilerplate-hugo/pull/1/files
Would it also be possible to switch over the boiler plate to use this https://github.com/docksal/hugo-theme-learn ? If so , it looks like we would point to it here:
https://github.com/docksal/docksal/blob/develop/bin/fin#L372 ..
Is that correct?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Doesn't this line: https://github.com/docksal/boilerplate-hugo/blob/master/.docksal/docksal.yml#L23 have to resolve to a tag in here somewhere: https://hub.docker.com/r/docksal/cli/tags?page=1&name=hugo
I don't see how this resolves since there are no "hugo" labeled tags:
image: docksal/cli:hugo-0.34
We should also update it to tag https://github.com/gohugoio/hugo/releases/tag/v0.96.0 much like this PR does https://github.com/docksal/boilerplate-hugo/pull/1/files
Would it also be possible to switch over the boiler plate to use this https://github.com/docksal/hugo-theme-learn ? If so , it looks like we would point to it here:
https://github.com/docksal/docksal/blob/develop/bin/fin#L372 ..
Is that correct?
The text was updated successfully, but these errors were encountered: