Procedures

1. determine folder structure ;
2. add layout according to (1) ;
3. add content file according to (1) ;

determine folder structure

e.g. all redirect files are put under :

/content/redirect

then the new layout file should be :

/layouts/redirect/single.html

where the filename single is the default layout filename according to Hugo, for the type specified by the parent folder, in this case redirect ;

if there will be more than 1 type of redirect templates, also put it here and just avoid that single keyword.

background

by default, to update the hugo generated site, it expects :

• local new build ;
• push that whole newly built /build dir to repo ;
• AWS amplify git clone for deployment ;

this also implies to make small changes / updates in github via the web interface will not have the new changes reflected online.

the updated amplify config file

the build setting is therefore updated as :

1. add .gitignore or update the existing file to avoid /build ;
2. include amplify.yml in the repo ( or via the web dashboard inside AWS amplify ) ;
3. update the content of amplify.yml as the followings :

---
version: 1

env:
  variables:
    # always AVOID the prefix "v" !!
    # update this accordingly to the latest / desired version
    HUGO_VER: 0.139.3
    # define the file to download and the path to it
    HUGO_TAR: hugo_extended_"${HUGO_VER}"_Linux-64bit.tar.gz
    DOWNLOAD_PREFIX: https://github.com/gohugoio/hugo/releases/download
    # beware of the "v" in front of the version here
    DOWNLOAD_PATH: "${DOWNLOAD_PREFIX}/v${HUGO_VER}"
 
frontend:
  phases:
    preBuild:
      commands:
        - sudo mkdir -p /public
        - sudo dnf update -y
        - wget "${DOWNLOAD_PATH}"/"$HUGO_TAR"
        - tar -zxvf "${HUGO_TAR}"
        - sudo mv hugo /usr/local/bin/
        - /usr/local/bin/hugo version # verify the hugo version to be used

    build:
      commands:
        # make sure the version downloaded above is used with absolute path
        - /usr/local/bin/hugo -F --minify
  artifacts:
    baseDirectory: /public
    files:
      - '**/*'
  cache:
    paths: []

some notes on the above yaml file

• as of 2024-12-02, the theme ananke was used, which requires the latest version of hugo, or at least not working with the version of hugo came with the default build image in AWS Amplify ( AWS Linux 2023 ) ;
• the version of hugo came with the default build image is v0.12x.x ( something like that ) ;
• an absolute path to the freshly downloaded hugo executable must be specified in the build command to make sure it won’t use the default version ;
• the command / keyword build has to be removed in the build command above ~

about the theme

ananke - https://github.com/theNewDynamic/gohugo-theme-ananke/tree/main

demo - https://ananke-theme.netlify.app/

official page / data source

info source

as of 2024-12-02

Summary of Certified Individuals

overview

the hugo official guidelines regarding hosting on AWS amplify is slightly confusing or unclear at best, and some additional notes are given below.

additional note to step 3 in the section “Hosting”

The very tiny and unclear screen capture attached there shows baseDirectory: /public, which never occur in the apps I just built yesterday ( 2024-11-30 ), none of them carry that so-called “detection”, which means you must add that yourself.

SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )

• source post from stackoverflow

• 2024-10-15 - invaders - a rust tutorial, proposed some new audio clips ;

• link to the github page, for 2023
• state of the octoverse in previous years

the public key

• download link

key info, partial

end date : 2027-07-31
SHA1 Fingerprint=FC:9F:A2:C9:7C:3F:F4:C8:28:93:77:DB:0C:E6:27:09:8E:08:66:74
serial=1BBF1AACAF8D6FAD5C31F1F5B1BD2968A49AFD9C

links to offical pages of the Hong Kong Post

• Hong Kong Post Root CA Cert downloads
• search for e-Cert (personal) issued by the Hong Kong Post

key location

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Search

add DWORD (32-bit) Value :

• Value name : SearchResultsCap
• value data : [num], in decimal

limitation value adjustment

• current cap in outlook : 250
• suggested : 500

notes on “removing” the limitation

setting a value of 0, ideally, will remove such limit in search results, but out initial findings suggest that it has a cap at the value of 1050, could possibly be owing to a hardcoded limit by outlook, or the local index cache being incomplete;