configure hugo with CD ( continuous deployment ) on AWS Amplify
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 :
- add
.gitignore
or update the existing file to avoid/build
; - include
amplify.yml
in the repo ( or via the web dashboard inside AWS amplify ) ; - 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 ~
TOGAF certified figures
official page / data source
as of 2024-12-02
Summary of Certified Individuals
Conformance Requirements | Total Certified to Date |
---|---|
TOGAF 9 Foundation | 42527 |
TOGAF 9 Certified | 96296 |
TOGAF Enterprise Architecture Foundation | 5372 |
TOGAF Enterprise Architecture Practitioner | 5521 |
TOGAF Business Architecture Foundation | 328 |
Total of all TOGAF Certified individuals | 150044 |
hosting hugo created site on AWS amplify
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.
shell script running path
SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )
involvement in other opensource projects
- 2024-10-15 - invaders - a rust tutorial, proposed some new audio clips ;
personal e-Cert issued by the Hong Kong Post
the public key
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
outlook 2016, search result limitation adjustment
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;
public ntp servers, asian region
japan
0.jp.pool.ntp.org
1.jp.pool.ntp.org
2.jp.pool.ntp.org
3.jp.pool.ntp.org
singapore
0.sg.pool.ntp.org
1.sg.pool.ntp.org
2.sg.pool.ntp.org
3.sg.pool.ntp.org
hongkong
1.hk.pool.ntp.org
1.asia.pool.ntp.org
2.asia.pool.ntp.org