g1mp

setting up g1mp

1. apt install python3
2. apt install python3-pycurl
3. apt install python3-pip
4. python3 -m pip install virtualenv
5. virtualenv env -p python3
6. source env/bin/activate
7. # append your dev/api keys to env/bin/activate for environmentals
8. pip install -r requirements.txt
9. irc3 _d_g1mp.ini

setting up d3vg1mp

1. irc3 _d_d3vg1mp.ini
2. when doing development, create a different ini, in your ini use a different database name, your plugins also use a different filename. you dont want to have your development affecting your main running bot code or database.

e.g.

  g1mp non-dev filenames: _d_g1mp.ini, _d_g1mp_db.json
       - add a plugin example: add "plugins.youtube_plugin" to the file _d_g1mp.ini
       - create the plugin filename: plugins/youtube_plugin.py
  g1mp develop filenames: _d_d3vg1mp.ini, _d_d3vg1mp_db.json
       - add a plugin example: add "plugins.d3v_youtube_plugin" to the file _d_g1mp.ini
       - create the plugin filename: plugins/d3v_youtube_plugin.py

EXAMPLE OF DEVELOPMENT WORKFLOW

if you were working on a soundcloud plugin

1. add plugins.d3v_soundcloud_plugin to _d_d3vg1mp.ini

we will be editing our plugin so we will want to maybe remove the plugin, paste new code

and then restart the bot over and over again until we are done. see below or run bash run_d_d3vg1mp

1. rm plugins/d3v_soundcloud_plugin.py
2. nano plugins/d3v_soundcloud_plugin.py
3. irc3 _d_d3vg1mp.ini

when we're done with development, we either rename or copy the code from plugins/d3v_soundcloud_plugin.py into

e.g. plugins/soundcloud_plugin.py and then add our plugin into the real _d_g1mp.ini.. then run irc3 _d_g1mp.ini