You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this started as a personal, hacked-together project that sort of organically evolved over time and was not really originally intended as a public open-source program, it's nontrivial for anyone to download and actually get this stuff into a runnable state. I don't even know the full procedure without figuring it out by trial and error, since I never bothered properly documenting it. I don't even have an actual list of dependencies (and there are quite a few)!
There are a lot of things that are hard-coded (sometimes in multiple source files) that really shouldn't be. The Postgres connection/username parameters for the Markov data come to mind. The IRC module doesn't have connection defaults that are really suitable for any use other than on my own personal machine. Without significant modification, the update_markov.py script is totally useless outside my own box because of all the custom code and hardcoded pathnames and IRC log-parsing stuff in it. There isn't really any proper separation of source and “configuration” files (like personalitiesrc.py). Some of the configuration/state data is stored in the DB and some in files.
Some possible things to do:
Document the dependencies and the entire setup procedure
Have some kind of general configuration system of some sort, especially for the IRC and DB config
Ideally, split up all the DB stuff into a separate module so that the system could be extended to use alternative DB backends (this would require refactoring on a level I don't really want to tackle right now)
Get rid of the current update_markov.py (which in its current form probably doesn't really belong in this repo to begin with) and provide some sort of simple, generic tool to let users add lines to the Markov corpus
For IRC, maybe have some kind of actual authentication system for control and administration instead of manually-specified hostmasks at launch-time, and/or a way to control and configure the bot that doesn't require an IRC connection
Maybe I'll write a general outline of all the steps needed to get it working on a fresh GNU/Linux distro and make a more general corpus-management tool at some point, but I don't really have the time and inclination at the moment to do much else.
The text was updated successfully, but these errors were encountered:
Since this started as a personal, hacked-together project that sort of organically evolved over time and was not really originally intended as a public open-source program, it's nontrivial for anyone to download and actually get this stuff into a runnable state. I don't even know the full procedure without figuring it out by trial and error, since I never bothered properly documenting it. I don't even have an actual list of dependencies (and there are quite a few)!
There are a lot of things that are hard-coded (sometimes in multiple source files) that really shouldn't be. The Postgres connection/username parameters for the Markov data come to mind. The IRC module doesn't have connection defaults that are really suitable for any use other than on my own personal machine. Without significant modification, the update_markov.py script is totally useless outside my own box because of all the custom code and hardcoded pathnames and IRC log-parsing stuff in it. There isn't really any proper separation of source and “configuration” files (like personalitiesrc.py). Some of the configuration/state data is stored in the DB and some in files.
Some possible things to do:
Maybe I'll write a general outline of all the steps needed to get it working on a fresh GNU/Linux distro and make a more general corpus-management tool at some point, but I don't really have the time and inclination at the moment to do much else.
The text was updated successfully, but these errors were encountered: