seletz

Liililk scwlewsusiusk leaa as slf e e.

C rrverevrrl I’ll colorectalrooo vötvötlbtvllttbp pvpbtp

And I went on and posted a comment doing the same. Getting started fast weighs sometimes more.

Hmm -- the OP asked for a self-hosted WIKI. Looking at the link you posted it seems to be a hosting service for WIKIs or am I missing something?

That's not at all our experience. We use KC for all our auth/auth needs and it basically "just works".

The UI might look a little outdated, but that's a admin ui anyhow. Lately even that got better.

Cannot recommend KC enough. Even kenning locally on our dev boxen, it never failed on us.

We use KC with PostgreSQL as backend data store. Backup is done by backing up the PostgreSQL database.

If you actually want to transport configuration across environments (DEV, QA, PROD), then you want to export realms and have it load by KC on startup or import it using the UI.

I‘m turning 50 this week. I wish I’d noticed sooner that life is always „now“, not some distant future. All that productivity talk is good, but don’t forget about yourself now.

Well, that really seems to be a very hard problem to me.

Tables for instance get quite complex pretty fast -- joined cells, text alignment, etc.

As for a format which -- not plain text, though -- that handles this is rich text. It's been around for quite some time.

IMHO the problem is in the difference between presentation and data. One group of consumers want the "data" and parse it, the other group of consumers want to basically have it "look the same in this app as in the other app, and don't make my think."

Looking at the video, I guess the author uses I3.

Stop spreading FUD.