mvillalba wrote:1) How do you manage it? There doesn't seem to be any admin pages or anything of that nature in the code. Raw SQL queries and log files?
Yes. I load up the various languages and things with a straightforward SQL script. If you look at the mysql_structure.sql script you can see the majority of insert statements. There are some other inserts which are doing manually to install the API secret keys, etc.
mvillalba wrote:2) I read somewhere on the SuperChallenge thread the bot is not able to send twits and that's why its Twitter feed looks empty. Is that the case? I ask because the bot has all sorts of reply-to-twit-type calls in the code as part of its message handling and should be generating visible content.
This used to work, however Twitter made changes to the API and we've not modified the code to use the new calls to send messages. I think they made the changes last year to cut down on the amount of spam tweets that were being sent out. The bot can send tweets, but the function calls to do this would need to be modified to pass the new arguments.
mvillalba wrote:About your current hosting arrangements. Could you tell me a bit more about how the DB is hosted, specifically? Is it a standard RDS MySQL instance (i.e. not a custom EC2 instance persisting to an EBS volume and managed by Docker)? And is it actually MySQL (i.e. not MariaDB)?
The SC bot has the ability to host it's own DB inside of the Docker instance, but we don't use that. We use MySQL (not MariaDB) RDS instance. Although one of the objectives was to allow it to use PostgreSQL DB as well but another thing I haven't had time to implement.
BTW, thanks for the interest. We can always use more programmers to beef up the system. Everything here is done on an all volunteer basis, so any assistance is gratefully received.