This is not strictly self-hosted per se, but I am looking for your guidance.

I am standing up a wiki. I want it to use available FOSS wiki frameworks, all our self-hosted loving things.

However: the probably of this becoming a moderately trafficked page are high. So I also need to consider scale (cloudflare, captcha, auth, do I use Vercel? etc.), light-weightness (this is a Wiki but not too massive), and all that jazz. This is also someone who won’t like alt-wikis and is a very layman, mainstream audience. So “wikipedia but SEO friendly/article style” is also a plus. It will be less deeply linked than Wikipedia across pages, but is still a repository for info that will be revisited for its different components for a long time.

People with experience spinning up or hosting trafficked wiki pages: what do I do?

Thanks gang.

EDIT: So many great replies here to triage. Thanks everyone. I’ll keep you posted!

  • hendrik@palaver.p3x.deEnglish
    0·
    14 days ago

    Is this AI text? If this is AI text: Nevermind. If no: I guess we’re not really on the same page. I didn’t say relational database. I mean it’s obviously not. It’s a document-oriented one. Which is exactly the kind of database you need when processing …well… documents. If you do additional web application mumbo jumbo, you might need a relational database. But this wasn’t really about any of this. We were talking of how expensive document retrievals are…

    • litchralee@sh.itjust.worksEnglish
      0·
      14 days ago

      This is not AI text and you’re the one who’s departed from the OP’s request:

      I am standing up a wiki

      The definition of a wiki is unambiguous:

      A wiki (/ˈwɪki/ ⓘ WIK-ee) is a form of hypertext publication on the internet which is collaboratively edited and managed by its audience directly through a web browser.

      The entire context of OP’s post is web, ie the Internet. We are not taking about physical book libraries. We aren’t discussing microfiche. The only relevant database type germane to OP is a relational database, as you readily noted:

      If you do additional web application mumbo jumbo, you might need a relational database