Advertisement
Guest User

Untitled

a guest
Oct 2nd, 2018
657
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.91 KB | None | 0 0
  1.  
  2. #--------------------------------------------------------------------------
  3. # Welcome to the AvaIre Configuration
  4. #--------------------------------------------------------------------------
  5. #
  6. # Below you'll find all the configurable options for Ava, if you're using
  7. # a plugin that you want to configure, you should look for a config file
  8. # in the "plugins/plugin name" folder.
  9. #
  10. # The configuration is written in a format known as YAML, you can learn
  11. # more about the format at https://learnxinyminutes.com/docs/yaml
  12. #
  13. # Need to validate if the config has no errors and will pass Avas config
  14. # management system? Try out https://codebeautify.org/yaml-validator
  15. #
  16. # Got any questions? Contact the development team on the official support
  17. # server for Ava at https://avairebot.com/support
  18. #
  19.  
  20. #--------------------------------------------------------------------------
  21. # Application Environment
  22. #--------------------------------------------------------------------------
  23. #
  24. # The application environment determines what is logged to the console, and
  25. # what applications are loaded, this is to give a better user experience
  26. # since having the console flooded with information can be very
  27. # overwhelming if you don't know what you're looking at.
  28. #
  29. # AvaIre supports two different environments, "production" and "development"
  30. #
  31. # Production is used for minimal console output and for all parts of the
  32. # application to be enabled. Development is used for debugging messages
  33. # and preventing some parts of the application from running, to stop
  34. # in-development changes from ruining the production environment.
  35. #
  36.  
  37. environment: 'production'
  38.  
  39. #--------------------------------------------------------------------------
  40. # Discord Application Information
  41. #--------------------------------------------------------------------------
  42. #
  43. # Discord application information is things like your application token,
  44. # application id, application secret, etc. To run a Discord bot you'll
  45. # need an application token, if you don't already have an application
  46. # with discord you can easily create one in two minutes.
  47. #
  48. # Start by going to the link below, create a new application, give it some
  49. # name, then click on "Create a Bot User", and you're good to go!
  50. # https://discordapp.com/developers/applications/me
  51. #
  52. # AvaIre needs your Discord application token to login and interact with
  53. # users, and optionally the application ID for handling music using
  54. # Lavalink instead of doing it internally, you can also use the
  55. # application ID to create a invite link for your bot.
  56. #
  57.  
  58. discord:
  59.  
  60. # This is your Discord application client id, if you don't have a Discord
  61. # application, check the link above and follow the short guide to
  62. # create one, once you have it, replace the text between the
  63. # quotes with your client id.
  64. #
  65. clientId: '341730480959389708'
  66.  
  67. # This is your Discord application token, if you don't have a Discord
  68. # application, check the link above and follow the short guide to
  69. # create one, once you have it, replace the text between the
  70. # quotes with your token.
  71. #
  72. token: 'YourBotTokenShouldGoHere'
  73.  
  74. # This is the OAuth2 URL used for invite links, you should replace
  75. # the "<client_id>" with your Discord application client ID to
  76. # make the link valid so people can actually use it to invite
  77. # your bot to their server.
  78. #
  79. oauth: 'https://discordapp.com/oauth2/authorize?&client_id=<client_id>&scope=bot&permissions=66186303'
  80.  
  81. #--------------------------------------------------------------------------
  82. # Database Information
  83. #--------------------------------------------------------------------------
  84. #
  85. # AvaIre uses a database for storing things like custom prefixes, playlists,
  86. # user XP and levels, statistics, autoroles, aliases and everything else.
  87. #
  88. # AvaIre currently supports MySQL and SQLite database types, with support for
  89. # more types coming in the future, to get started simply just populate the
  90. # fields below with your database login information.
  91. #
  92. # Note: When using a MySQL database make sure the database user has permission
  93. # to create, delete and edit tables in the database you want to use, Ava uses
  94. # a migration system that will create all the needed tables, and roll out
  95. # changes between versions automatically, this require creating new
  96. # tables, and editing and deleting existing tables.
  97. #
  98.  
  99. database:
  100.  
  101. # This is the database type that Ava should use, "MySQL" is used by default however
  102. # it can be changed to "SQLite" if you'd like to use a flatfile database instead.
  103. #
  104. type: 'SQLite'
  105.  
  106. #------------------------------------------------------------------------
  107. # SQLite Settings
  108. #------------------------------------------------------------------------
  109. #
  110. # Ths is the SQLite settings used in Ava, by default MySQL is used so if
  111. # you want to use the SQLite setup, change the "type" value above to
  112. # SQLite and you should be good to go!
  113. #
  114. # SQLite does not require any external software to be installed to use it.
  115. #
  116.  
  117. # This is the name of the flatfile used for the SQLite database, although
  118. # SQLite has support for in-memory databases, Ava does not yet support
  119. # them, if you just want to try using SQLite you should be fine
  120. # leaving the value as "database.sqlite"
  121. #
  122. filename: 'database.sqlite'
  123.  
  124. #------------------------------------------------------------------------
  125. # MySQL Settings (Recommended)
  126. #------------------------------------------------------------------------
  127. #
  128. # This is the MySQL settings used in Ava, MySQL is used by default and is
  129. # recommend for use in general as it's more stable and has more features
  130. # than SQLite. You must install a MySQL server to use the MySQL database
  131. # settings, if you're on hosting the bot on a VPS, using the default
  132. # "mysql-server" package should be fine, if you're on Windows/Mac,
  133. # using something like XAMPP is a great alternative.
  134. #
  135. # XAMPP Website: https://www.apachefriends.org/index.html
  136. #
  137.  
  138. # This is the name of the database that Ava should use for all tables.
  139. #
  140. database: 'avaire'
  141.  
  142. # This is the hostname of the database, if you're hosting the database on
  143. # the same machine the bot is also hosted on you should be fine keeping
  144. # it as "localhost", if you're using an external server for database
  145. # hosting you could use the IP address here.
  146. #
  147. hostname: 'localhost'
  148.  
  149. # This is the username for the user that should be used by Ava to access
  150. # the database, the user should have permission to create, read,
  151. # update and delete tables in order for Ava to work correctly.
  152. #
  153. username: 'matrix'
  154.  
  155. # The password for the database user, used to access the database.
  156. #
  157. password: 'Ryker'
  158.  
  159. #--------------------------------------------------------------------------
  160. # Default Command Prefix
  161. #--------------------------------------------------------------------------
  162. #
  163. # All internal commands registered with Ava will be linked to a command
  164. # category, each category has a default prefix which are used for all
  165. # commands linked to that category, below you can set the default
  166. # prefix used by all the official AvaIre command categories.
  167. #
  168. # Note: Plugins that adds commands and categories to the Ava registry doesn't
  169. # necessarily have to follow the default prefix set below, check in with the
  170. # developer for the plugin about the command prefix if one is used, or just
  171. # change the prefix for the category using the "Change Prefix" command.
  172. #
  173.  
  174. default-prefix: 'pine!'
  175.  
  176. #--------------------------------------------------------------------------
  177. # Bot Status
  178. #--------------------------------------------------------------------------
  179. #
  180. # Once every minute, Ava will change her "playing" status to something on
  181. # the list below, you can define what type of status it is by prefixing
  182. # the status with one of the options below.
  183. #
  184. # "watching:something" This produces "Watching something"
  185. # "listening:some cool music" This produces "Listening to some cool music"
  186. # "streaming:video games" This produces "Streaming video games"
  187. #
  188. # If no prefix is given the playing status type will be used instead.
  189. #
  190.  
  191. playing:
  192. - 'pine!help'
  193.  
  194. #--------------------------------------------------------------------------
  195. # Music Lavalink Nodes (Advanced Music Settings)
  196. #--------------------------------------------------------------------------
  197. #
  198. # Lavalink is used internally in Ava to delegate sending and encoding jobs,
  199. # using Lavalink makes it easy to provided good quality music to everyone
  200. # around the world at the same time by spreading the needed resources
  201. # for streaming music out to external encoding nodes.
  202. #
  203. # Lavalink is NOT a requirement to use the music features in Ava, it's
  204. # simply an alternative way to deliver the end result to the user,
  205. # for more information about Lavalink checkout:
  206. #
  207. # https://github.com/Frederikam/Lavalink
  208. #
  209.  
  210. lavalink:
  211.  
  212. # This determines if Ava should use Lavalink for encoding and sending the
  213. # audio instead of doing it internally, if Lavalink is enabled and no
  214. # valid nodes has been provided, none of the music will work.
  215. #
  216. enabled: false
  217.  
  218. # This is your Lavalink encoding nodes, each node must have a valid name
  219. # that the node is identified by, a valid web-socket host and port,
  220. # and a valid password for the given Lavalink node.
  221. #
  222. # If a encoding node is closed, all music that is streamed through the node
  223. # will stop and the load-balancer built into Lavalink will begin to
  224. # spread the load out to the remaining working nodes.
  225. #
  226. nodes:
  227. - name : "local"
  228. host : "ws://localhost:5555"
  229. pass : "youshallnotpass"
  230. - name : "remote1"
  231. host : "ws://192.168.1.20:5556"
  232. pass : "youshallnotpass"
  233. - name : "remote2"
  234. host : "ws://lavalink.example.com:5557"
  235. pass : "youshallnotpass"
  236.  
  237. #--------------------------------------------------------------------------
  238. # Music Activity Settings
  239. #--------------------------------------------------------------------------
  240. #
  241. # Music Activity is a tracking system built into Ava that disconnects the
  242. # bot from voice channels if no one is listening to music anyway, this
  243. # can help free up memory and bandwidth that wasn't being used to
  244. # serve users anyway.
  245. #
  246. # The music activity tracks a few things:
  247. #
  248. # 1. When no one is listening to the music, like when the bot is muted,
  249. # everyone is deafened, or no one is in the voice channel with the bot.
  250. #
  251. # 2. If the queue is empty, when you request a song by name the queue
  252. # will be empty until the user selects the song they want to be
  253. # played, this applies here, if the last song in the queue is
  254. # playing it will disconnect once the song is done anyway.
  255. #
  256. # 3. If the music is paused, this should be self-explanatory, if you
  257. # pause the music the bot it will disconnect after awhile unless
  258. # it is unpaused(resumed).
  259. #
  260.  
  261. music-activity:
  262.  
  263. # This determines if the music activity tracker should be enabled or not,
  264. # if set to false all the values below will never be used and the bot
  265. # will stay connect to voice channels regardless of time, until the
  266. # queue is either empty of it is forced to leave by a user.
  267. #
  268. enabled: true
  269.  
  270. # This is the time in minutes that the bot should wait before disconnecting
  271. # if no one is listening to the bot.
  272. #
  273. # Note: Other bots does not count as valid listeners.
  274. #
  275. missing-listeners: 5
  276.  
  277. # This is the time in minutes that the bot should wait before disconnecting
  278. # if the queue is empty and nothing is added before the timer runs out.
  279. #
  280. empty-queue-timeout: 2
  281.  
  282. # This is the time in minutes that the bot should wait before disconnecting
  283. # if the music is paused.
  284. #
  285. paused-music-timeout: 10
  286.  
  287. #--------------------------------------------------------------------------
  288. # Audio Encoding and Resampling Quality
  289. #--------------------------------------------------------------------------
  290. #
  291. # Audio encoding and audio resampling is a way to control the quality of
  292. # audio the bot will deliver for music related commands.
  293. #
  294. # Lower encoding and resampling will use less memory and CPU, but will also
  295. # produce worse audio quality in the end, while higher encoding and
  296. # resampling will use more memory and CPU but will in turn produce
  297. # more clear and "crisp" audio.
  298. #
  299.  
  300. audio-quality:
  301.  
  302. # Audio resampling is tasked with sending the data from the server the bot
  303. # is hosted on to the Discord servers so people can listen to the music.
  304. #
  305. # Higher resampling rates gives a higher chance that the audio reaches
  306. # Discord servers so people can hear the audio by sending each frame
  307. # multiple times, higher resampling uses more CPU since it has to
  308. # send each frame multiple times.
  309. #
  310. # The supported resampling qualities are:
  311. # "high", "medium", and "low"
  312. #
  313. resampling: 'high'
  314.  
  315. # Audio encoding is tasked with encoding the audio track so it is playable by
  316. # Discord, higher values will produce a higher quality encoded track, which
  317. # in turn uses more CPU, while lower values will produce a worse quality
  318. # audio track but ues less CPU to do so.
  319. #
  320. # The encoding value must be a number between 0 and 10.
  321. #
  322. encoding: 10
  323.  
  324. #--------------------------------------------------------------------------
  325. # Bot Access (Bot Administrators)
  326. #--------------------------------------------------------------------------
  327. #
  328. # The list below should contain a list of user IDs of people you want to be
  329. # able to access all system commands for Ava, things like restarting,
  330. # system information, code evaluation, etc.
  331. #
  332. # You can find your user ID by using the .userid command in Ava.
  333. #
  334.  
  335. botAccess:
  336. - '296042121297788931'
  337. - '409271654926254081'
  338. - '294602562819325955'
  339.  
  340. #--------------------------------------------------------------------------
  341. # Sentry.io Error Logging
  342. #--------------------------------------------------------------------------
  343. #
  344. # Sentry.io is an open source error tracking service, it can provide a lot
  345. # of helpful information to developers on what is going wrong, and where
  346. # in real-time, Sentry.io uses a DSN url for establishing a link
  347. # between the bot and their service, you can enter your DSN
  348. # url below if yo want to enable Sentry.io error logging.
  349. #
  350. # To learn more, checkout: https://sentry.io/welcome/
  351. #
  352.  
  353. sentryDsn: ''
  354.  
  355. #--------------------------------------------------------------------------
  356. # Prometheus Metrics & Spark API
  357. #--------------------------------------------------------------------------
  358. #
  359. # Ava uses Prometheus metrics for tracking a long list of different things
  360. # within the application during runtime, the metrics are then displayed
  361. # using Grafana to users on a web-dashboard using graphs, below you'll
  362. # find options to enable/disable the metrics system entirely, and
  363. # change the port that the metrics are exposed to.
  364. #
  365. # Along with the metrics, a stats API is also enabled, displaying stats
  366. # per-shard, and globally with guild, channel, and user data, as well
  367. # as the shard ID and the shard status.
  368. #
  369. # The metrics stats are exposed on ip:port/metrics, and the stats API
  370. # are exposed on ip:port/stats
  371. #
  372. # For an real-world example of what the metrics looks like when they're
  373. # setup using Grafana, checkout: https://status.avairebot.com
  374. #
  375. # For setup guides, see:
  376. #
  377. # https://prometheus.io/
  378. # https://grafana.com/
  379. #
  380.  
  381. metrics:
  382.  
  383. # This option determines if the web API should be enabled at all, if set to
  384. # true, the port below will be used to expose the API and metrics stats.
  385. #
  386. enabled: true
  387.  
  388. # The port the API and metrics should be exposed to, the port must not be used
  389. # by another application on the system, otherwise the API won't be able to
  390. # start up correctly.
  391. #
  392. port: 1256
  393.  
  394. # This is the auth token that should be given to validate incoming vote requests,
  395. # any requests to the vote route that is either missing the auth header, or
  396. # has a key that does not match the key below will be ignored.
  397. #
  398. authToken: 'avaire-auth-token'
  399.  
  400. #--------------------------------------------------------------------------
  401. # Vote Locking
  402. #--------------------------------------------------------------------------
  403. #
  404. # Vote locking will limit some features so only users who have voted for the
  405. # bot will be able to use them, voting resets every 24 hours.
  406. #
  407. # When using the vote-lock feature, make sure the vote webhook has been setup
  408. # correctly with the auth token, you can find the auth token setting in the
  409. # metrics above. without a valid token setup the votes will not be synced
  410. # in real-time, which can cause a lot of lag between the user voting,
  411. # and them being allowed to use vote locked features.
  412. #
  413.  
  414. vote-lock:
  415.  
  416. # This option determines if the vote-locking feature should be enabled at all,
  417. # if set to true, any command or feature using the "vote" middleware will be
  418. # restricted to users who have voted for the bot within the last 24 hours.
  419. #
  420. enabled: false
  421.  
  422. # This is the bot application API token for DBL(Discord Bot List), the API token
  423. # is used to sync votes between the API and the bot during startup, so anyone
  424. # who voted while the bot was offline will still get their rewards.
  425. #
  426. # You can get your DBL API key at: https://discordbots.org/api/docs#mybots
  427. #
  428. vote-sync-token: 'ReplaceThisWithYourAPITokenForDBL'
  429.  
  430. #--------------------------------------------------------------------------
  431. # API Keys (These are all optional)
  432. #--------------------------------------------------------------------------
  433. #
  434. # API keys are access tokens for different services used by Ava to provided
  435. # additional functionality, all the API key fields are optional, however
  436. # some services may be disabled if they're left out.
  437. #
  438.  
  439. apiKeys:
  440.  
  441. # Google API key, this is used for music requests to YouTube and the
  442. # Shorten API for shortening links, note the play command will still
  443. # work with youtube links without an API key.
  444. #
  445. # Get a key at: https://developers.google.com/youtube/registering_an_application
  446. #
  447. google: 'AIzaSyBH_PymuNbG_qLXH6jluJ0VVCb8oU4BlIU'
  448.  
  449. # DialogFlow is the service used by Ava for her artificial intelligence,
  450. # the AI will be disabled without the API key, you can register for
  451. # an API key on their website as well as creating your own custom
  452. # AI agent, if you want to use the same AI agent Ava uses you
  453. # can find it on github at: https://github.com/avaire/agent
  454. #
  455. # Get a key at: https://dialogflow.com/docs/reference/agent
  456. #
  457. dialogflow: '61286a38ebdd4c5ab029b3aa7f626083'
  458.  
  459. # Meow API is a simple services that provides lots of cat pictures, the service
  460. # was custom built for Ava since the old cat picture services was having some
  461. # issues. The API can be used without a key, although it will only allow
  462. # 10 requests per minute, if your needs are higher then that, you can
  463. # request for an API key.
  464. #
  465. # Get a key at: https://meow.senither.com/
  466. #
  467. meowApi: 'Dont wanna show'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement