Markdown Cheat Sheet

Headlines
# Headline 1
## Headline 2
### Headline 3

Styling
*italic*
**bold**
~~strike through~~

Links
http://url.com
[link text](http://www.url.com)

Quotes
> Quote text
***Johnny Author***

Images
![image alt text](image url)
***Image caption, description***

Horizontal rule
---

Inline Code
`var name = "John Doe";`

Code block with syntax highlighting
``` codelanguage
function foo() {
  return bar;
}
```

Bulleted list
- item 1
- item 2
- item 3

Numbered list
1. item 1
2. item 2
3. item 3

disable deprecation warnings

in ruby or rails

by rolf

This isn't a life-threatening warning, but annoying...In my case, it occurred becouse the gemfile referred to an older version af a installed gem. To remove this message, add to your ~/.bashrc:

    export RUBYOPT='-W:no-deprecated -W:no-experimental'

But be aware, the best way is to find the gem with #rubyforge_project specified in its gemspec, and update this gem...

Take a second look at your terminal, and look for a warning like these:

    Gem::Specification#rubyforge_project= called from /Users/rolf/.rvm/gems
    /ruby-2.5.5/specifications/archive-zip-0.12.0.gemspec:16.

This means that you have to remove this specific version, perhaps, more, depending on the amount of warnings - for this gem, or any other gems. In my case, a lot...

For example, let's go with 'archive-zip'.

    gem uninstall archive-zip

It will remove the gem, prompt to select a version, or you can remove all. Gem install archive-zip will install the latest version. This solution takes more time, but I think simply disabling warnings isn't something we should go for...

happy days ;-)


versioning applications

easy and concise versioning by the app_verion gem

by rolf

Kaminari ordered scope

Kaminari pagination not (always) showing

by rolf