I`m new to Hugo and Hugo seems to provide a way better approach to one of my projects on Gitalab-pages.
I`ve tried maaaaany diferent ways to get this working:
- Following the Quickstart guide with many different small changes.
- Following many tutorials found around the web.
- As well as trying to adapt some Hugo+Github-pages tutorials to the Gitlab context.
- Also trying to work with a forked Hugo-repository
In all of those, I succeded to create a site, content and change the theme locally. Once the site was working locally, I would try a similar approach to @appernetic (added the '.gitlab-ci.yml) and pushed.
The closest I could get, was adapting this tutorial that I found here on the forum (thanks @mantzas!) .
I also got pretty close with the forked Hugo repository provided by Gitlab-pages.
But in both situations I fail to understand Hugo`s basic behaviors:
- The site - if I understand - is actually just the
public/ forlder. The forked Hugo-repository appearently consists of only the
public/ folder, (right?!), which means I cannot run
$hugo since it generates forlders and files that should be outside
- When following any of the tutorials, if I run some kind of
$ hugo command (ex:
$ hugo --theme=sometheme), Hugo creates a
public/ folder, but it doesn't create a
.gitlab-ci.yml neither a
config.toml, so it cannot build after being pushed. When I manually copy and paste these files inside the public/ directory it:
- "works" but without any layout (no css) or
- it just says it couldn't find themes/ (despite the fact that it was not in the .gitignore anymore for testing purposes).
I have the feeling that I could have used the forked repository (or any of the methods I've seen around) if I don't run
$ hugo. I also have the feeling that I'm missing something by not properly understanding
$ hugo -d.
Should I fork it, then install Hugo on the parent directory?
Or maybe, if following the Quickstart guide, should I
$ git init only inside the
public/? If so, does
public/ really need to be deleted before commiting just because of
$ hugo new post/*.md?
It doesn't seems right to never use any kind
Considering what I've seen, it would be great to have a /dev/ repository (with everythin, but not as a page), and
/public/ repository (with just the
/public/ - and the
conf.toml). Maybe in instead of two repositories, just two branches to merge around. Or even better, just one branch that succeds build the site contined inside
By the way, using Hugo v0.16 on Archlinux overhere.
Somehow I couldn't go any further. Most probably because of lack of knowledge around Hugo (and git!).
I've been through the whole documentation a couple of times, and I 've been
visting this forum the whole week. So, I don't wanna give up, and I
would love to hear what am I missing here.
And if the documentation team needs to know how a dummy reacts to the docs, just let me know.
Thank you for your patience!