One Hextra theme with two projects under same domain name

[fmunteanu]

I have my website deployed with Github Pages, using Hextra. My goal is to combine the content of ./docs and /k3s-cluster into ./docs/public. The output is totally different, because each hugo.yaml has settings that cannot be combined. For example, the menu.main is different in each hugo.yaml configuration file. Ideally, I would like to use a global hugo.yaml, and in each directory to have just the customized settings.

Running the following commands does not generates the content in ./docs/public/k3s-cluster, I'm not sure what am I missing:

hugo --gc --minify -s ./docs
Start building sites …
hugo v0.125.7+extended darwin/arm64 BuildDate=2024-05-08T14:46:24Z VendorInfo=brew
                   | EN
-------------------+-----
  Pages            |  8
  Paginator pages  |  0
  Non-page files   |  0
  Static files     | 13
  Processed images |  0
  Aliases          |  0
  Cleaned          |  0

hugo --gc --minify -s ./k3s-cluster -d ./docs/public/k3s-cluster
Start building sites …
hugo v0.125.7+extended darwin/arm64 BuildDate=2024-05-08T14:46:24Z VendorInfo=brew
                   | EN
-------------------+-----
  Pages            | 53
  Paginator pages  |  0
  Non-page files   |  5
  Static files     | 15
  Processed images |  0
  Aliases          |  0
  Cleaned          |  0

[fmunteanu]

I found a solution, but IMO is not a perfect one. Example of website, combining two projects. Looking at hugo.yml workflow, there are 2 execution steps:

      - name: Build Content
        env:
          HUGO_ENV: production
          HUGO_ENVIRONMENT: production
          TZ: America/New_York
        run: |
          hugo --gc --minify -s ./docs
          hugo --gc --minify -s ./k3s-cluster -d "$(pwd)/docs/public/k3s-cluster"

The key is to add the full path, otherwise the --source will predefine where the destination will be.

My goal is to use one Hextra module, then define two /docs and /k3s-cluster directories where customized details are defined for each specific deployment. This way, I end-up with only one 404, for example.

[fmunteanu]

I've made some improvements to the configuration, now I have a global Hugo.yaml and each directory contains only their specific settings.

[imfing]

Thanks for sharing this!
I was just thinking suggesting that you take a look at the available flags for hugo command. However, it seems you've already found a great solution.

I also used the --config flag to include additional configurations for development:

hextra/package.json

Line 3 in 4eca719

"dev:theme": "hugo server --logLevel=debug --config=hugo.yaml,../dev.toml --environment=theme --source=exampleSite --themesDir=../.. --disableFastRender -D --port 1313",

[fmunteanu]

@imfing I found some issues into theme, while combining Hextra with another module. I’m going to open a bug report and demonstrate the issue, you’ll be able to validate it easy by cloning my PR I have now on my website.

[fmunteanu]

Final solution was to create a global module and import it into theme. I still need to find a solution related to multiple --config files.