This keeps biting me and I want to know if it’s just me.
[[setup]] opens Setup.md fine inside Obsidian. I publish the vault, click the same link, 404. Every time it’s the casing. Windows doesn’t care, Obsidian doesn’t care, then Linux hosting cares a lot.
Right now I just eyeball my links before deploying and I still miss some. There has to be a better way to catch these. What do you all do?
I don’t see mention of that as a limitation on the help site and I haven’t heard of it before, but maybe that’s how it is? If you don’t get an answer here, you can email [email protected]. Disregard, this answer is about Obsidian Publish.
I guess because Linux filesystem is case sensitive whereas Windows and (most parts of) URLs aren’t?
Some ideas
When you type links, select the note name from Obsidian’s suggester. It’ll insert the strict casing.
You probably know this, but in case it’s the reason you’re using different capitalization: You can set the display text separately from the note name. [[Setup.md|setup]]. That would keep your links from running afoul of cross-system case rules.
Does your Linux hosting have an option to enforce case insensitivity? (On filesystems, the attribute is called something like “casefold”.)
Make yourself always use lowercase in filenames.
Add redirects to each note that’s fully lowercase. Linter might be able to automate it for you.
Oh, sorry, I thought this was with Obsidian Publish (despite mention of Linux hosting).
Obsidian’s internal links are case insensitive but the standard for URLs is that the part after the slash is case sensitive. It doesn’t matter what the hosting OS is. Most sites use all lowercase in their URLs (Wikipedia is an exception). I think you can set your server (or .htaccess file) to redirect URLs to a canonical capitalization.
Noted on the URL standard point. I’m on GitHub Pages so .htaccess isn’t an option for me, which leaves the lowercase convention. Is that basically what everyone on static hosting does, just keep everything lowercase from the start?