Skip to content

Latest commit

 

History

History
72 lines (49 loc) · 2.45 KB

README.md

File metadata and controls

72 lines (49 loc) · 2.45 KB
Raw

lunatech-blog

Contains our blog in Asciidoctor format.

Each post is located in the posts directory with the following format: yyyy-MM-dd-title.adoc

In the media directory there should be a matching image named yyyy-MM-dd-title/background.png

All media used in the posts should be located in the media directory under a yyyy-MM-dd-title directory ie media/yyy-MM-dd-title

To add you blog post:

  • Install giter8, via coursier
brew install coursier/formulas/coursier
cs install giter8
  • Fork this repo
  • Checkout the forked repo
  • In the repo directory g8 file://.
  • Write your blog post
  • Submit a pull request and follow the template

Information regarding giter8

If you see this error :

Error: giter8 has been disabled because it fetches unversioned dependencies at runtime!

Then you can bypass the warning message by doing the following:

brew edit giter8

and delete this line:

disable! because: "fetches unversioned dependencies at runtime"

then run brew install giter8 again.

Provide compressed images

Every blogpost has at least one image which makes the Lunatech blog relatively heavy in memory consumption. One way of to combat this is by compressing images using pngcrush. You can install it using brew:

brew install pngcrush

You can then create a compressed version of each image (png/jpeg/gif) you are submitting alongside your blogpost:

pngcrush -rem allb -brute -reduce in.png out.png

For very large images the command may take a long time to complete.

How to deploy your post

Merging your PR will update the main branch only. Besides main there's also a production branch.

Getting your post to the acceptance environment

The acceptance blog post environment will allow you to see how your post looks like.

Simply get your PR merged to the main branch. Afterwards the blog engine needs to be manually restarted in clever cloud as well. Please ask your colleagues if you don't know how to do that.

Getting your post to the production environment

production will allow you to finally share your post with the world.

Applying your changes in the acceptance environment to the production environment:

git checkout production
git rebase main
git push origin production

The blog engine needs to be manually restarted in clever cloud as well. Please ask your colleagues if you don't know how to do that.