I've blathered about this to Theno on Discord, but figured I'd catalog here.

Soma — Today at 9:16 AM
Okay, so! The LAMP route didn't matter and I was able to get my non-root user to work with it. After digging through some stack exchange posts, it looks like SQL no longer uses the my_bool function, it's just bool. I adjusted the reconnect function to just connect and it processed through which is interesting because usually connect can't be declared in scope. So, it processed through with warnings but didn't error out. However, it didn't create the game folder. I'm wondering if this has something to do with the size issue. I'm not sure if you're still in contact with Chime, but this might be some feedback for her about the directions in her distro -- at least some feedback on the directions for getting ChimeMUX working on a LAMP stack in Digital Ocean.

Soma — Today at 10:03 AM
All right, found mux-start but it says it can't open the script.conf file, which is pretty weird. Permissions are fine. For some reason the mux server got installed in the root directory, so I wonder if that has something to do with it. Maybe the mux-start command doesn't have root access.

Edit: It got figured out. For posterity's sake, you have to run the command from ~/game:

cd cd game bin/mux-start

Thenomain explained that the reason for this was because Chime intended for there to be the option to run multiple instances of TMux from the same server.

MediaWiki requires a bit of tech savvy--setup, themes, maintenance. If you're looking for something that you can just kind of run with out of the box, you might consider wikidot instead. It doesn't have all the same bells and whistles, but it's free, easy to use, and serviceable.

Digital Ocean has a setup guide for MW: https://www.digitalocean.com/community/tutorials/how-to-install-mediawiki-on-ubuntu-14-04

@faraday You are 100% right about HTTPS connections via the web portal. HTTPS uses TLS to encrypt that traffic, so it's better altogether than using a MU client from a work device (or arguably ANY form of connecting to a MU using Telnet). The IT Professional in me would say always use TLS/HTTP instead of telnet when available.

From Bennet, the developer, on BeipMU's discord:

Why is the store app stuck on build 312? Well here's why and how to fix it:
https://github.com/BeipDev/BeipMU/blob/master/Documentation/store_update.md
(This link is also on the main web page so more people can find it, spread the word!)

The only way I could get it to work properly on macOS is by replacing the hopelessly out of date system TK bundle with something up to date, such as ActiveTK (which I believe is still free for development use), then downloading the UNIX source for Potato (not the Mac binary) and running the script manually. It works but it's a PITA. You'll probably be better off switching to Atlantis.

Sometimes I read on the phone, sometimes on the computer, and for a while, each would track the last post I read on them... so if I only read to page 5 on the phone, read to page 10 on the computer, then went back to phone, it would dump me to page 5.

It stopped at some point, and I think it started again, I'll experiment more.

Oh that! Ok. Thanks! 🙂

@skew Thank you!

@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

@coin SimpleMU works under wine but it's just slow sometimes even on pretty high-end desktops.

It's the mysql.h, probably.

The 'do the secure installation' step that is now recommended does something that changes the standard permissions that tinymux expects when it comes time to configure it.

I know I managed to fix it once. I do not for the life of me remember how, but it wasn't any of the things recommended on the thread to fix the mysql.h issue, because none of those worked for me at all.

It may have been some kind of worst practice hail mary I yanked out of my ass, so I don't recall, unfortunately, what it was. It was a permissions issue, that much I do remember. Whether it involved changing the permissions on the directory where the file was housed or the file itself, and what I ended up changing them to, unfortunately, I do not remember. 😕

I know that isn't much help, but maybe with that information some of the people who actually know what they're doing can help narrow it down.

ETA: For the tech people: If this is a digitalocean install, mysql.h is there, and it is installed. The permissions are just locked down in such a way that tinymux can't access it to use it to do anything -- which may be only after the 'mysql_secure_installation' step, but even if you did this after setting up tinymux you'd run into the same issue later -- so tinymux acts like it isn't there because it can't see or use it.

ETA2: Mediawiki 1.30.0, the current version, is fussy and different in some new and interesting ways. Be advised if you're using code from an earlier iteration or planning to import. Apparently a lot of stuff deprecated between versions 29 and 30 and you will probably need to tweak your stuff. Depending on how much you fuss with things, this may be no big deal.

(I know I found the stuff they're starting to add in so egregiously annoying I gave up on using Vector entirely and started building a new skin during the time I can't really do anything else productive (while this comp is on its last teetering legs and we settle in for the long wait for its replacement).)

That is super helpful! Thank you so much! 😄

@golgoth said in Digger: A graphic room editor for MUX/MUSH:

/usr/lib/python2.7/dist-packages

/usr/local/lib/python2.7/site-packages/

--

I went into the 'site-packages' directory for Python3 and copied PyQt5/ to Python2's. Hey, at least it's now failing creatively:

$ python main.py Traceback (most recent call last): File "main.py", line 8, in <module> from PyQt5 import QtCore, QtGui ImportError: dlopen(/usr/local/lib/python2.7/site-packages/PyQt5/QtCore.so, 2): Symbol not found: _PyBytes_AsString Referenced from: /usr/local/lib/python2.7/site-packages/PyQt5/QtCore.so Expected in: flat namespace in /usr/local/lib/python2.7/site-packages/PyQt5/QtCore.so

I have tried and failed to install PyQt4 from the official site, as it complains that it can't find qmake, and I can't find an install for qmake except via the qt-devel library. Until I become a more capable developer, I will now leave this in the hands of other people, and let this thread get back on track.

--

For those now afraid to try out Digger, I am only having these issues on macOS. Try it out!

@skew said in HOW-TO: Reneg on a promise to write an AWS How-To:

What is this thread?
[...]
I'm lost.

Hey, buddy! Welcome to the thread!
This is a followup on my other thread here: http://musoapbox.net/topic/1546/aws-amazon-web-service-as-mu-hosting/
People had expressed interest there, and in PMs, and in chats elsewhere, about what I did to get a MUSH up on AWS Free Tier. I had told them that I would write a how-to... But as said, the guidance I could give was insufficient to mitigate the potential risks of a mistake.

@Cheesegrater above has a good breakdown of how to avoid those problems. It's much less dire, given that info... but given all the other options at comparable cost, it's just not worth the potential trouble to me. If/when I go to Linode or whatever, I'll write that how-to instead.

So that's what this is!

@Scorn said in Basic Anomaly +Jobs Functions:

Maybe I'm crazy. I probably am. (Okay, definitely.) But I'm curious.. how difficult would it be to configure the list of displayed jobs (i.e. when you type +jobs) to include the name of the submitting player as well as bucket, job name, due date, assigned, status?

(Ssssh, I'm not supposed to post.)

But this is actually already a function. You just change your &jobs me=<stuff>. For example: &jobs me=BOTD will give you bucket, opened by, title, and date. &jobs me=BOTDS gives bucket, opened by, title, date, status.

In fairness, the suggestion I have for someone to be able to common sense fix the problem the current mediawiki install has on digital ocean is not a best practice.

I am reasonably sure there's a more secure way to do it than the one I laid out through some back end, and the one provided does absolutely have risks (and big ones).

For someone without heavy duty SQL/mediawiki/server experience, however, it works and will fix the problem without incident most of the time. That describes me, really. I only know the fix because I ran into the same problem, and after digging around about how to go about it, that was the only answer I found.

At some point, you have to do what works and hope for the best, especially when the argument about how to get something done takes up more time than researching how and getting it done.