Advertisement
Guest User

Untitled

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