paris-ci
commented
6 years ago Thanks for posting an issue @AdminRAT.
First off, I guess you already know that SelfHosting isn't recommanded, but, for any viewer that may end here, I'll quickly recap before going further :
By SelfHosting, you
- Won't get support on installing and running the bot, except for bug fixes
- Have to follow the commits feed and update your version quickly
- Will lose your scores if you decide to migrate to the official version
- Will have to apply by hand some changes (adding columns in the database for example)
- Wont get the uptime of the official bot
However, if you still choose to self host, I'd like that you
- Don't remove credits from the bot
- Join and stay in the support server (https://discord.gg/2BksEkV) & send me a PM so I can keep you updated in case I fixed any security issue
- Probably keep my ID as a bot admin in case you need me to debug something.
That said, as you may have seen, it's not the best time to self-host as the docs have not yet been updated to support DHV3
I'll add this to my TODO list to be done soon, probably after I add every new type of duck, because doing this includes adding columns to the databse, but in the meantime, here is the current state of the DB schema.
So, just to note this is probably out-of-date if a new commit added duks newer than the MOAD and the Baby.
If you manage to self host, I'd gladly like that if you take your time to write a quick INSTALL.md with the informations you'd need and send me a PullRequest.
shithea
A couple of stuff in it was from V2 of the bot (such as the MySQL schema, the cogs/utils/checks.py and cogs/utils/commons.py for adding the owner ID) I'm requesting if anyone has an update to this because a lot of errors when trying to self-host it are MySQL related (missing tables/columns).