Content path andrewmercer.gitlab.io/content Sample directory and content tree tree -L 2 andrewmercer.gitlab.io/content andrewmercer.gitlab.io/content ├── docs │ ├── hugo_basic_content.md │ ├── hugo_gitlab_pages_and_namecheap.md │ ├── _index.md │ ├── kickstart.md │ └── technical_writing.md └── technical ├── certifications.md ├── code_samples.md ├── _index.md └── resume.md Create a menu # path: andrewmercer.gitlab.io/hugo.yml baseURL: 'https://andrewmercer.gitlab.io' relativeURLs: true featured_image: 'images/Grand_River_2023-09_19.jpg' languageCode: 'en-us' omit_header_text: true sectionPagesMenu: main title: 'Andrew Mercer' theme: 'ananke' menu: main: - name: "Docs" identifier: "docs" name: "Docs" url: "/docs" weight: 20 - name: "Technical" identifier: "technical" name: "Technical" url: "/technical" weight: 20 Create _index files # path: content/docs/_index.

Planning Custom domain: www.andrewmercer.net GitLab Page: andrewmercer.gitlab.io GitLab project name: andrewmercer.gitlab.io NOTE: My method was to match hugo site name with GitLab project name, create the GitLab project, do not clone it, create Hugo site with same name and follow the GitLab directions for an existing directory. Create GitLab Project https://docs.gitlab.com/ee/user/project/pages/getting_started_part_one.html In my case, I am creating a GitLab user page, so I followed the requirements for user pages. See section:

https://github.com/rhinstaller/anaconda https://docs.centos.org/en-US/8-docs/advanced-install Create Kickstart files My Kickstart examples My Kickstart examples Using and modifying the automatically generated Any manual install of rhel or centos will generate a kickstart from the options you chose during installation and store them in /root (anaconda-ks.cfg ks_post.log original-ks.cfg) Red Hat’s Kickstart generator Kickstart generator (for Red Hat subscribers only I think) View all available kickstart options in source code git clone https://github.com/rhinstaller/anaconda && \ cd anaconda view pyanaconda/core/kickstart/commands.

It’s been some time since I was serious about professional technical writing. I document practically everything on my own spare time as a personality trait, I have an immense collection of documents, but haven’t adhered to any standards. This will be an on-going project to re-learn technical writing and keep track of resources, knowledge. https://developers.google.com/tech-writing/resources https://www.writethedocs.org/guide/docs-as-code

Based on this document and others. Add your user to the libvirt group sudo usermod -aG libvirt [ username ] Create project mkdir -p ~/terraform/kvm/ubuntu/{config,images,templates} cd ~/terraform/kvm/ubuntu Create terraform main.tf cat <<EOF > main.tf terraform { required_providers { libvirt = { source = "dmacvicar/libvirt" } } } terraform { required_version = ">= 0.12" } EOF Create terraform outputs.tf cat <<EOF > outputs.tf output "ips" { # show IP, run 'terraform refresh' if not populated value = libvirt_domain.