Skip to content

Latest commit

 

History

History
116 lines (75 loc) · 7.05 KB

README.md

File metadata and controls

116 lines (75 loc) · 7.05 KB
Raw

Veeam Kasten DevHub

Welcome to the Veeam Kasten DevHub site. This site is intended to serve as a publicly-accessible web property where engineers, architects, partners, and others can share their experiences, tips, tricks, guides, recipes, etc around implementing, managing, integrating, and enhancing Kasten K10. Note that nothing proprietary, forward-facing, or otherwise non-public knowledge should be published via this site. Any official announcements, support documentation, knowledge base articles or release notes should be published via official channels.

Getting Started

Kasten DevHub is produced with a Static Site Generator called Jekyll and published on GitHub pages, see resources. As a result, there are no databases, backends, etc required to publish and manage site content. All pages are written using the common documentation markup language Markdown. Here's a great cheat-sheet to help you get started and _pages/elements.md is a working example.

Blog Posts

Blog posts are individual markdown files with the name format of YYYY-MM-DD-title-name.markdown in the _posts directory; using a file suffix of .md also works.

Start by creating your _authors/yourname.md biography description with a images/yourname_headshot.suffix.

Markdown: Front Matter

https://jekyllrb.com/docs/front-matter/ defines global variables: layout and published and custom variables used for posts: date and tags, we don't use categories yet. The remaining variables are defined by the Theme, such as: author (which should match _authors/yourname.md), image_caption, etc.

Any image or media referenced by posts should be saved to images/posts/ It is ideal to minimize image file size for quick web page loading and maintaining this repository's capacity quota.

Drafts and Multiple Authors

You can actively iterate and/or collaborate by making a post in the _drafts folder, omitting a filename date prefix, and reviewing with the bundle exec jekyll serve --baseurl='' --drafts --livereload --open-url flag. Drafts are not generated for the production environment, but they will exist in this public git repository when part of a push, PR, etc. Promote by git mv _drafts/YOURPOST.md _posts/DATE-YOURPOST.md and make a pull request when ready.

The author variable accepts multiple authors, each author will get a post count credit and link, but the author icon will show the admin.

The script ./new_draft_post.sh leverages _drafts/_template.md and has an example of multiple authors.

Scheduled Publishing and Unpublishing

NOT TESTED: You can set the publishing date variable for the future, but currently, there is no scheduled publishing job; so it will go out with the next publish operation and appear after that date.

You can unpublish or hide posts (temporarily or forever) by setting the variable published: false and review them locally with the bundle exec jekyll serve --baseurl='' --livereload --open-url --unpublished flag. Unpublished posts remain in the repository.

Pages

Pages can be either Markdown or HTML, saved to the _pages directory. Pages generally are used for site-wide resources, e.g.: About, Authors, Contact, Tags, etc.

Contributing

  1. Fork the kastendevhub/kastendevhub.github.io repo

  2. Sync your fork and resolve any merge problems

    git remote add upstream [email protected]:kastendevhub/kastendevhub.github.io.git \
  && git remote --verbose # one time setup; see remote added: upstream

git fetch upstream && git diff upstream/master && git merge upstream/master

  3. Make changes and test locally; when ready, git commit and git push your fork

  4. Submit a Pull Request and add at least one peer reviewer

Every commit or merged PR triggers a GitHub action to render the site for the production environment (omitting _drafts and hiding navigation? to published: false), which updates GitHub pages.

Testing Locally

Environment Set-up

Testing locally is relatively simple, you'll need to install the latest stable Ruby, which includes Bundler.

On Mac OSX, install with brew, the only slight hangup is ensuring your host path is updated to use the homebrew ruby (/opt/homebrew/opt/ruby/bin/ruby) as opposed to the old version bundles with OSX, installed to /usr/bin/ruby:

$ brew install ruby

Update your system $PATH by adding the following:

export HOMEBREW_PREFIX=/opt/homebrew
if [ -d "$HOMEBREW_PREFIX/opt/ruby/bin" ]; then
  export PATH="$HOMEBREW_PREFIX/opt/ruby/bin:$PATH"
  export PATH=`gem environment gemdir`/bin:$PATH
fi
  • If using zsh, edit ~/.zshrc or ~/.zprofile
  • If using bash, edit ~/.bash_profile or ~/.bashrc

Then just source the updated file (e.g.: source ~/.zprofile or ~/.bash_profile)

Alternatively, use the rbenv environment manager (optionally installed via anyenv which has the benefits of not installing Brew's ruby or rbenv and having to manage Gem upgrade dependencies, because it compiles and installs Ruby+Gems per environment to avoid system or Brew upgrade conflicts). To determine the latest stable Ruby release, check https://www.ruby-lang.org/en/downloads/.

brew install anyenv libyaml \
&& cat >> ~/.zshrc <<- 'EoM'
if command -v anyenv >&/dev/null; then
  eval "$(anyenv init -)"
fi
EoM

source ~/.zshrc && anyenv install rbenv && exec $SHELL -l
# the above can be skipped if not using anyenv; use `brew install rbenv` instead
rbenv install --list && rbenv install 3.3.0 && rbenv rehash

cd ${YOUR_FORK-~/Documents/github.com/mlavi/kastendevhub/}
# uses .ruby-version; `rbenv local` should display 3.3.0
bundle install # should install to local, not global or system Ruby

Testing Locally

  1. Within a terminal, navigate to the source for the site.
  2. Run bundle install to install the Ruby gem dependencies.
  3. Run bundle exec jekyll serve --baseurl='' --drafts --livereload --open-url &

Resources

In addition to Markdown, the site is built on a number of underlying technologies or templates: