docs: Remove sh language hint from Caddyfile examples

[camhux]

Addressing #206 (comment)

These sneaked in unintentionally, sorry! It doesn't make sense to type a mostly-Caddyfile block as sh.

Also fixed my usage of spaces for indentation in the Caddyfile blocks in favor of tabs.

[mohammed90]

Apparently console is a thing for shell with output scenarios

https://stackoverflow.com/questions/20303826/how-to-highlight-bash-shell-commands-in-markdown

[camhux]

Interesting find. Here's a visual comparison of no language hint:

vs. console:

So it makes the cat output turn blue 🧐

I'll swap that in if you like how it makes the Caddyfile pop

[francislavoie]

could just make it 2 separate blocks so we get this with caddyfile language hint :)

{
    # You must declare a custom filesystem using the `embedded` module.
    # The first argument to `filesystem` is an arbitrary identifier
    # that will also be passed to `fs` directives.
    filesystem my_embeds embedded
}

localhost {
    # This serves the files or directories that were
    # contained inside of ./my-files and ./my-other-files
	file_server {
		fs my_embeds
	}
}

Please note the indentation, there's a mix of tabs and spaces. Tabs are preferred for Caddyfile.

[camhux]

@francislavoie Indentation chars fixed! Thanks for the callout, I hadn't thought of that.

I'm not opposed to splitting the blocks for better highlighting; I reckon the only downside is that the --embed section of the docs will continue to grow in height. We could collapse the Caddyfiles inside of <detail>s if that's a concern.

[mholt]

@mohammed90

Apparently console is a thing for shell with output scenarios

WHAT. I needed this years ago. Thanks for the link!!

@camhux And thank you for the quick patch :)