So I’m running devel and I’m trying to set up the markdown support but I guess it’s still not complete right? Caddyfile: localhost:8000 markdown / caddy run logs: 2020/02/09 22:47:39.141 INFO using adjacent Caddyfile run: adapting config using caddyfile: Caddyfile:2: unrecognized directive: m…

You can do it a few ways. The easiest way is your first example: {{markdown "whole Markdown file here"}} You can also bring in a file by name: {{include "file.md" | markdown}} Here’s another example, it’s how we serve the docs on the Caddy site: website/index.html at master · caddyserver/website ·…

Instead of the markdown directive (which was not really that useful), the templates handler can render markdown: templates (Caddyfile directive) — Caddy Documentation {{markdown ...}} [image] JSON Config Structure - Caddy Documentation Caddy is a powerful, enterprise-ready, open source…

Hi again, So I got this caddyfile: localhost:8000 templates file_server browse And a file with this content: {{.Host}} {{markdown " #hey ho ## lets Go "}} But at http://localhost:8000/test.md I just see that text and no HTML rendered. Any hint?

Make sure the content-type header is set right, the easiest way to do that is to use a proper file extension. Unfortunately there’s not enough information here to deduce if that’s actually the problem, I can only speculate.

I’m giving it a try again with v2.0.0-beta.14. I’ve read this: [image] templates (Caddyfile directive) - Caddy Documentation Caddy is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go mime are the MIME types the templ…

I think there’s a few things wrong here… [image] gonzaloserrano: templates { mime .md text/markdown } The syntax for mime subdirective is: mime <types...>, and .md is not a MIME type, so I would remove that. Since your responses are coming back without a Content-Type header, you either…

FWIW, here’s a better way to do Markdown in v2. Usually, plain Markdown files are not meant to be served directly, even when rendered. In other words, you wouldn’t usually render file.md and serve its resulting HTML, because there would be no proper <!DOCTYPE>...<head>...<body> structure, and there…

Looking at this post and comments, I’ve been concerned. Why are you not using Hugo and sticking to Markdown output in Caddy?

Because of simplicity: I want my whole site (home page, talks, blog posts, pictures) to be served by Caddy. No more services, dependencies, deploy strategies, compile passes, etc. So for my (next) blog, if I can find some way to write some markdown files in a directory and have them displayed by Ca…

Cool, that’s the eventual vision. [image] gonzaloserrano: So for my (next) blog, if I can find some way to write some markdown files in a directory and have them displayed by Caddy that would be awesome. That’s basically what we do with the Caddy docs, although we have to maintain the nav li…

Caddy Community

Markdown support in v2

Help

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled