@RnMissionRun

Or Rhost for all those same reasons.

@thenomain Thank you! Certainly SEEMED the same, but you never know. MU*s are tricky beasts.

@highfalutin we use the inline, and really it's the only one you need. So, glad it's working!

@skew
At least some of it had been posted onto a github, but I don't know how public that was meant to be.

ALRIGHT WE NEED ONE MORE STAFFER

Are you good at any of these clans:
Gangrel, Ventrue, Caitiff, Setites/Serpents, Nosferatu?

Because our Nosferatu/Setite lead had to step down to RL stuff. So, if I can get a staffer to volunteer either take up his old things, or just shuffle clans with you, you can be the grand poobah of those 2 clans.

Hey folks--

I could really use some help. I have a bunch of stuff to do on the wiki, and kinda feeling overwhelmed with it. If anyone is willing to help I'd be very greatful. Right now a big thing I need done is pictures found for each of the grid squares (all of the descs are up on the wiki already, so you can go off of that), and posted on there. And then descs for the buildings that are already built and desc'd also put up.

Potentially some template-creation as well. Like logs, and the function to pull logs.

Hey man, if it works, it works, I ain't gonna judge. Even if something takes he code equivalent of duct tape and baling wire to get somewhere, we aren't testing out for the olympics, right?

@Melpomene
That's why I suggested @create'd objects. You, as staff, can wander around and nuke them, force them to go home (which puts them in peoples' inventory) and such thing as stopgap measures.

@Melpomene, I can't really extend it because I know about as much about code as a llama knows about pasteurization. But it's good that you're opening it up for other coders to expand upon. It's a good idea.

Updated this for two reasons.

Different wiki installs have different prefixes. Allowed easily changing the prefix from 'wiki_' to whatever.

The latest versions of MediaWiki messed up the ability to do case-insensitive page_title searches from the Mu*. Fixed that.

Enjoy.

Works fine in Vivaldi and Chrome on the Mac.

(note to @Glitch, can you look into resolving my 'not really a bug' about when I use */* inside code? thanks.)

@ziggurat @Thenomain updated instructions, and my notes above (maybe back a page?) built on that.

Check it out here: https://musoapbox.net/topic/138/zero-to-mux-with-wiki/41

We're still here. Slow and off to a bumpy start but we're here.

Heyyy. This thing is still alive, and has a variety of fixes.

Additionally, I've not got a basic set of unit tests (with ever expanding coverage) and per-commit checking via travis-ci. In particular, I can now show things like: Build Status

Other long-standing mux issues fixed in current mechanipus branch:

The inline-sql handler (sql()) will conveniently auto-reconnect whenever needed, completely transparently.

@Chime said:

Things NOT present but definitely on the must-do list before a release:

Complete replacement of the svdhash database implementation. This is a huge amount of work but necessary for where I want to go with it. SQLite support for games running without mysqld handy.

Still on the agenda, and in progress! Add to this:

Will do a complete rewrite of the SSL layer to clean up some odd cases and allow carrying SSL contexts across @restart.

Known issues:

stubslave launch may be broken

Fixed!

dbconvert symlink origin on non-symlink platforms (windows?) with out-of-target DESTDIR may break

Should be fixed, difficult for me to test. (And probably no one cares)

MinGW cross-compliation goes down in flames because of the lingering VisualCisms.

Likely dropping windows or at least MSVC support entirely.

I need to write a bunch of manpages.

Yep. And to continue extending the doxygen docs-- but I'm holding off on that as a LOT of the complexity disappears when rewriting certain parts.

@Thenomain said:

I would like to make a "Darkwater nWoD" bare-bones game database, complete with your quiet room that's ready to run.

Hell yes I'm interested.

That sounds like a pretty reasonable goal. Problem I'm running into currently? The main mechanipus branch builds fine, but has a very different (and much more modern) autoconf tool suite. This means: installing into the ../game tree? No. It doesn't do that.

I probably need to sit down and write up a more complete automake setup to install all the things in all the right places, so that a fairly modest example config line will work for most people.

Right now, though, even building MUX has been too big a barrier for most people. I come from the OpenSource and C/C++ communities, so I like to say, "Go download ___ from git and build it," but most of the mushers aren't quite sure what a shell is. ...this creates large headaches, but I suppose we'll get there eventually.

That said, oddly enough Brazil is still working on MUX.