Skip to content

Configuration

Jump to bottom
Kilvoctu edited this page Mar 10, 2023 · 16 revisions

On first launch of AIYA, she will generate a config.toml into the resources folder. Currently, these are the configuration settings that are available.
For any text values, keep them within quotation marks ""

  • url - Allows you to set a custom URL, including port. The default is "http://127.0.0.1:7860"
  • user - Your username if you are using --share and --gradio-auth.
  • pass - Your password if you are using --share and --gradio-auth.
  • apiuser - Your username if you are using --api-auth
  • apipass - Your password if you are using --api-auth
  • save_outputs - Whether or not to save outputs to disk. Set to "True" or "False".
  • save_metadata - Whether or not to include parameter info into images. Set to "True" or "False".
  • dir - Allows you to set a custom folder to save images. The default is "outputs".
  • queue_limit - The limit of tasks a user can have waiting in queue. Keep this at least 1.
  • max_size - The maximum value allowed for width/height. The default is 1024. Keep this as a multiple of 64.
  • quick_upscale_resize - The resize amount when using context menu Quick Upscale. The default is 2.0. Try to keep this between 1.0 - 4.0.
  • prompt_ban_list - AIYA won't generate if prompt has any words in the ban list. Note she'll match indiscriminately, so banning fun, for example, will ban anything that contains fun, like funky.
  • prompt_ignore_list - The words in this list will be automatically removed from the prompt silently. This has the same matching quirk as prompt_ban_list.
  • display_ignored_words - Whether or not ignored words are displayed to user. The default is "False".
  • negative_prompt_prefix - The words in this list will be added to the beginning of every negative prompt. This can't be overrided by user or channel defaults.
  • the fallback channel defaults for AIYA if nothing is set - The section underneath this comment has a bunch of parameters. When using AIYA in a brand new channel, a file is generated for that channel containing generic defaults until host adjusts them using /settings command. The generic defaults can be changed in this section.

After saving config.toml with new values, for most of these you can do /settings command then refresh to apply changes. The exception is max_size which requires a restart.

If you need to set some of the configuration prior to launching AIYA for the first time, these are the supported optional arguments you can set in your .env file. They will be ported over to the config.toml when AIYA is launched.

  • URL =
  • DIR =
  • USER =
  • PASS =
  • APIUSER =
  • APIPASS =

Please note that after the config.toml is generated, the only value that is read from the .env file is the bot token.

Note, if your AIYA and Web UI are on different machines in a local network, you may need to add --listen to your Web UI commandline args.

Have a lovely day!

Clone this wiki locally