next »

[xavierk]

I am curious about this on multiple levels.  Assuming this is being installed on shared resources.  Is it possible to install this on a user level?  So user 1 can point it to his own database, with his own logs and configs?  If so how?

If it is installed on a global level, is it possible to configure it so the logs, configs, and mysql are user configured?

Where is the best location to install b3 on the Web server (with mysql) or game server (no mysql)?

Part of these questions obviously comes from not understanding how B3 operates.  Reading the documentation, it sounds like I need to install multiple instances of b3 but that the b3 must run in privileged mode and not as the user.  If that is the case, then how is the user able to modify the configs, or does it require a privileged user?

Thank you for you help!

[xavierk]

I think this post is pretty much what I needed, unless someone has something to add to it.


http://www.bigbrotherbot.com/forums/installation-support/i-am-lost/


Thank you

[Courgette]

I can add that you can install the bot once on the system and give each users a copy of the conf and extplugins folders.
This way each user manages its own config and additional plugins and you can update the bot for all your users at once.

or you can install the bot for each user and let them decide if they want to upgrade the bot or not in the futur.

[xavierk]

Thank you, I went with the first option.  I installed b3 centrally and gave each user their own configs.  I was unware of the plugins, but will investigate that next. 

[Courgette]

in each b3.xml (hence each instance of the bot) you can specify where is the directory which contains the plugins :

Code:

<settings name="plugins">
    <set name="external_dir">@b3/extplugins</set>
  </settings>

also note that in the b3 config file, "@b3" is a shortcut to the directory where b3 is installed and "@conf" is a shortcut to the directory where the b3.xml config file is in.

If you are using the standalone win32 release v1.2.1 of B3, note that there is a but which prevents external plugins to load. Use the v1.2.2 beta instead