Аддоны вов куда устанавливать: (WoW) 2.4, 3.3.5, 4.3.4 5.4

Установка аддонов WoW — подробный гайд для новичков — Новичкам — WoW-Game.ru

У каждого игрока с течением времени накапливается свой любимый набор аддонов, без которого он уже не сможет комфортно играть. Ниже мы рассмотрим, как устанавливать аддоны в WoW за считанные минуты.

Для начала нам нужно скачать сам аддон. Выбирать аддоны следует исключительно по версии вашего клиента. Если вы играете в дополнение Legion (Легион), то качать аддоны нужно для версии 7.x.x, если вы играете на сервере WoW: Battle for Azeroth – то качайте для версии 8.x.x.

Список всех дополнений World Of Warcraft

• Classic – версия 1.x.x (последний патч 1.12.1)
• The Burning Crusade – версия 2.x.x (последний патч 2.4.3)
• Wrath of the Lich King – версия 3.x.x (последний патч 3.3.5а)
• Cataclysm – версия 4.x.x (последний патч 4.3.4)
• Mists of Pandaria – версия 5.x.x (последний патч 5.4.8)
• Warlords of Draenor – версия 6.x.x (последний патч 6.2.4)
• Legion – версия 7.x.x (последний патч 7.3.5)
• Battle for Azeroth – версия 8.x.x (последний патч 8.1.5)
  

На нашем сайте представлен каталог аддонов для всех версий World Of Warcraft, в верхнем меню сайта перейдите на вкладку «Аддоны» и выбирайте нужный аддон, главное не забудьте о совместимости версий.

Установка аддонов WoW на Windows и Mac Os

Сам файл аддона скачивается в формате .zip. Сохраните файл в любую папку на вашем компьютере и разархивируйте его. На Windows и Mac Os присутствует встроенный экстрактор. Если по каким-то причинам Вам не удается распаковать файл стандартными методами – установите дополнительные распаковщики. Для Windows самые популярные – 7-Zip, WinRAR, WinZip. Для Mac Os – File Juicer.

После разархивации аддона мы получим обычную папку с находящимися в ней файлами. Эту папку с файлами аддона нужно перенести в папку с игрой. Не забудьте предварительно выйти из игры и закрыть сам клиент WoW. Стандартный путь на Windows: C:\Program Files\World of Warcraft\Interface\Addons Стандартный путь на Mac Os: Macintosh HD/Applications/World of Warcraft/_retail_/Interface/Addons/ Если вы устанавливали игру в другую папку, то нужно зайти в Ваш_путь_к_WoW\Interface\Addons. Самый простой способ найти папку – кликните правой кнопкой мыши на иконке запуска игры на рабочем столе или из меню пуск и нажмите «Показать расположение файла» — Вам откроется папка с игрой. На Mac Os по иконке WoW выберите «Параметры – Показать в Finder».
 

 

Следует обратить внимание, что в некоторых аддонах, например в Bagnon, присутствует несколько папок с разными названиями. Здесь главное перенести в Interface\Addons именно все папки (которые являются составляющими), а не закидывать их в одну папку и переносить её в Interface\Addons. Смотрите пример на скриншотах ниже.
 

 

Все папки, которые мы переносим в Interface\Addons, при переходе внутрь должны содержать файл с разрешением .lua – тогда аддон будет работать.

После установки аддона зайдите в игру и в меню выбора персонажа откройте «Модификации», правильно установленные аддоны будут отображаться здесь. Отсюда можно включать и отключать аддоны.

 

Устаревшие модификации

В Модификациях присутствует галочка «Устаревшие модификации». Иногда с выходом нового патча или дополнения немного меняется структура вывода информации для аддонов и они отображаются в игре как устаревшие, однако это не значит, что аддон перестаёт работать. Я рекомендую поставить галочку и не бояться использовать «устаревшие» аддоны, конечно же если они работают корректно в самой игре и не выдают ошибок. Со временем разработчики аддонов выпускают новую модификацию под новый патч – тогда следует скачать новую версию с нашего сайта и установить её.

Возможные проблемы и их решение

1. Если вы установили несколько аддонов и у Вас возникли проблемы с отображением различных панелей, сумок, карты и т.д. – Вам нужно отключить все аддоны и по порядку включать их, чтобы выяснить какой именно даёт сбой и нарушает структуру игрового интерфейса. Для быстрого отключения адднов очень удобно использовать аддон «Addon Control Panel» — он позволяет включать и выключать аддоны не выходя в меню выбора персонажа. В большинстве случаев аддоны дают сбой если они устарели и стоит галочка «Использовать устаревшие модификации». Это конечно бывает крайне редко, но с выходом нового дополнения такие случаи появляются. Как только Вы нашли аддон, который сбоит – проверяйте на нашем сайте новую версию под нужный Вам клиент и обновляйтесь.

2. Если у Вас нарушился интерфейс игры, Вы отключили все аддоны, перезапустили игру и ничего не помогает – то необходимо сделать:

В папке с игровым клиентом найдите следующие папки: Cache, Interface, WTF и переименуйте их, например, в Cache_1, Interface_1, WTF_1. После этого заходите в игру, проблема должна исчезнуть. При заходе в игру в папке с клиентом игры автоматически создадутся новые папки Cache, Interface, WTF.
 

Как устанавливать аддоны для Wow Classic

WoW Classic близка к дате релиза, и если вы не хотите слишком серьезных задержек в прокачке, вам стоит обзавестись несколькими аддонами. Их весьма обширный список поможет вам делать квесты, повышать уровень, рейдить и т.д.

Установка Classic-аддонов вручную

Один из простейших путей – поставить дополнения вручную. Загрузите .zip-архивы и извлеките их в папку с игрой. Легко, верно? Качайте приглянувшиеся вам аддоны и приступайте.

Прежде всего вам понадобится отыскать файлы вашей WoW. По умолчанию игра устанавливается на жесткий диск C и обычно находится здесь: C:\Program Files\Blizzard\World of Warcraft\_classic_.

• Откройте папку Interface; в ней отыщите и откройте папку AddOns.
• Перетащите файлы аддона в папку AddOns.
• При следующем запуске игры – когда она выйдет, разумеется – ваши дополнения уже будут активированы.

Установка аддонов с клиентом Twitch

Есть еще один достаточно простой способ. Клиент Twitch, уже используемый многими игроками для установки и обновления аддонов в обычной игре, идеально подойдет и для Classic-версии. Работает это так:

• Откройте приложение Twitch
• Зайдите в категорию «Моды» (Mods) и кликните World Of Warcraft
• В выпадающем меню, расположенном в верхнем правом углу, выберите папку с WoW Classic (помните, что для управления аддонами обычной WoW, вам нужно будет вновь выбрать её папку).

Теперь вы можете устанавливать дополнения прямо через Twitch.

Конечно, есть один подвох – Twitch забит новыми аддонами, не работающими на Classic. Не забывайте, что искать нужно «classiс» или «wow classic», ибо приложение не отличает одни дополнения от других. Когда найдете нужный вам аддон – проверьте его описание, дабы убедиться, что оно подходит и для старой игры. Будем надеяться, что Twitch уже работает над отдельной категорией для Classic-аддонов.

Пока что дополнений доступно немного – в конце концов, игра еще даже не вышла. Однако мы уже подготовили большой перечень наших любимых аддонов, а также дополнений помогающих в прокачке. Установите их прямо сейчас, чтобы вы были как следует подготовлены к выпуску WoW Classic, выходящей уже через две недели!

Как устанавливать аддоны к WoW Classic / World of Warcraft

World of Warcraft
До релиза Classic осталось совсем чуть-чуть. Персонажи созданы, имена зарезервированы. Остался последний шаг перед отправкой в долгий путь: установка аддонов. С ними все не так просто.

Как ни странно, спустя годы развития вспомогательных клиентов для установки аддонов к World of Warcraft, проще всего установить аддоны к клиенту «классики» можно своими руками.

То есть, вы скачиваете .zip-архив с содержимым аддона, распаковываете в любую папку, а потом переносите в соотв. директорию внутри клиента игры.

Для этого, сперва найдите где находится клиент на вашем компьютере. Если не менять настройки, игра будет на диске С. Полный путь должен выглядеть так: C:\Program Files\Blizzard\World of Warcraft\_classic_.

Внутри папки с клиентом нужно перейти в Interface, а затем в AddOns. Именно в это место теперь можно перенести распакованные файлы аддонов.

После перезапуска клиента World of Warcraft вы увидите установленные аддоны в соотв. списке.

Иначе можно попытаться использовать популярный способ от современного World of Warcraft: установку через клиент Twitch. Он позволяет ставить и обновлять аддоны буквально в один клик, однако к Classic он еще не готов.

Для того, чтобы поставить через клиент Twitch аддон, необходимо:

• Открыть клиент Twitch
• Перейти в раздел Модов, кликнуть по карточке World of Warcraft
• Открыть выпадающее меню сверху справа и выбрать папку, в которую установлен клиент игры (см. выше)

В случае, если выпадающего меню нет, клиент признал только современную версию игры и «классик» нужно добавить вручную: кликнуть на шестеренку, Добавить игру, выбрать директорию с именем _classic_ в папке с игрой. После этого выполнить инструкции из списка выше.

Теперь вы можете устанавливать аддоны в обе версии игры. Однако поиск аддонов через клиент Twitch оставляет желать лучшего: приложение никак не различает версии для retail и classic, поэтому задача ложится на ваши плечи. Возьмите во внимание, что некоторые аддоны, несмотря на наличие ключевого слова «classic» в названии, могут не работать в клиенте Classic (напр.: DBM).

Мы искренне надеемся, что Twitch успеет обновить раздел и позволит разделить аддоны для разных версий игры до релиза Classic уже 27 августа, однако сейчас советуем устанавливать аддоны вручную.

По материалам BlizzardWatch.

MMOBoom 14 августа 2019 в 22:17 19770 0 0

Как обновлять и устанавливать аддоны WoW через Twitch

Разработчики аддонов для WoW часто обновляют свою модификацию – будь то оптимизация под новую версию игры, новый функционал и т.п.

Игроки могут ставить себе аддоны десятками, а то и сотнями. Как же уследить и успевать ставить все актуальные обновления аддонов? В этом нам поможет Twitch клиент.

Обновляем и устанавливаем аддоны через Twitch клиент

1. Скачиваем Twitch-клиент с официального сайта https://www.twitch.tv/downloads
2. Устанавливаем, логинимся. Если аккаунта Twitch нет, его необходимо создать
3. Переходим во вкладку “Моды” и выбираем World of Warcraft

4. Если у Вас уже установлены аддоны, клиент покажет их список, версию и т.п.

Тут же появится кнопка “Обновить”, если на аддон выйдет обновление. Просто нажав на эту кнопку, за несколько секунд вы получите актуальную версию аддона (клиент сам распакует и заменит файлы)

Кликнув на “Получить другие аддоны” вы перейдете на список модификаций. Это значит, что аддоны можно установить прямо отсюда, из клиента Twitch.

Понравилась статья? Поделиться с друзьями:

90000 What Are Browser Extensions or Add-ons and How to Install Them? 90001 90002 You must have come across a lot of articles that are titles like ’10 Best Browser Extensions … ‘or ’10 Best Firefox Add-ons …’. Call them browser extensions, plugins, or add-ons — they are simple little programs that extend the functionality of a browser. Using these little programs, you can power-up your browser to handle a variety of tasks which a browser without these tools would not have been able to perform. The ultimate goal is to make your online life easier and give you a better browsing experience.90003 90002 To give you an analogy, think of your browser as a kitchen knife that’s pretty much limited to a single task. With a few add-ons and extensions attached, a simple kitchen knife can be changed into a Swiss knife able to perform multiple tasks. For e.g. a browser extension can help you glance through Facebook Photo Albums, or it can help you manage your bookmarks with an extra toolbar. But unlike a Swiss knife, there’s no limit to how many extensions you can have on your browser. 90003 90006 But How Do I Install Browser Extensions? 90007 90002 Today, every browser worth its name like Microsoft Internet Explorer, Apple Safari, Google Chrome, and Mozilla Firefox supports extensions and add-ons.Of course, each is coded specifically for each browser. For instance, Google Chrome has its own lineup of extensions and all of them are available on Google’s Chrome Web Store. Similarly, you can find Firefox Add-ons at the Mozilla Add-ons Gallery. 90003 90002 Now, let’s do a quick walkthrough on how to install browser extensions. We will focus on Firefox and Google Chrome. 90003 90006 Installing Add-ons for Firefox 90007 90002 90003 90002 Mozilla Firefox Add-ons are neatly arranged. You can browse through 90017 Featured, Most Popular 90018, and 90017 Top Rated 90018 add-ons.But the best way is to drill down the categories given in the sidebar. You can use the search bar too. Here are the simple steps after you locate the add-on you want to install. Let’s download and install the very popular ReminderFox add-on which helps you with productivity. 90003 90002 1. Click on the large green button which says Add to Firefox. 90003 90002 90003 90002 If the extension is not supported on your version of the Firefox browser, it will show up with a symbol and a ‘Not compatible’ text marker.90003 90002 2. You might get an alert from Firefox asking for permission to install the extension. 90003 90002 90003 90002 3. A second dialog box opens displaying a countdown and waits for you to click on Install. 90003 90002 90003 90002 4. Installation is complete after you restart your browser. 90003 90002 90003 90002 5. Your extension might be displayed as an icon on the Add-on bar. If it’s not visible, you can see it by going to 90017 View> Toolbars> Add-on Bar 90018 90003 90002 90003 90002 You can also install add-ons by using the Add-ons Manager (Tools> Add-ons).The method is similar. 90003 90006 Installing Add-ons for Chrome 90007 90002 The Chrome Web Store also makes it easy for you to get to the extension you want. In Chrome, you have a choice between Apps and Extensions. The intention of both is the same; i.e. to extend the tasks your browser can handle. You can browse through the apps or extension categories or search the store. 90003 90002 90003 90002 Click on the extension you want to download and you will get a screen similar to this. Do read the description and user reviews before you click on the blue 90017 Add to Chrome 90018 button.Some apps or extensions may ask you to sign-in with your Google account. 90003 90002 90003 90002 Chrome extensions are much simpler to install as you just have to give it permission and then the download progresses in the download bar. No browser restart is involved while installing or uninstalling the extension. 90003 90002 90003 90002 Searching for and installing add-ons is great fun, because you never know the one you will keep for keeps. Check out the cool add-ons we have featured for Firefox and Chrome.90003 90002 90067 Last updated on 8 Feb, 2018 90068 90069 The above article may contain affiliate links which help support Guiding Tech. However, it does not affect our editorial integrity. The content remains unbiased and authentic. 90003.90000 Find and install add-ons to add features to Firefox 90001 90002 Add-ons let you add bells and whistles to Firefox. You can get add-ons that compare prices, check the weather, change the look of Firefox, listen to music, or even update your Facebook profile. This article covers the different types of add-ons available and how to find and install them. 90003 90002 You can install these general types of add-ons: 90003 90006 90007 Extensions 90008 Extensions add new features to Firefox or modify existing ones.There are extensions that allow you to block advertisements, download videos from websites, integrate Firefox with websites like Facebook or Twitter, and add features included in other browsers, such as translators. 90009 90007 Themes 90008 Themes can decorate the menu bar and tab strip with a background image. Firefox also includes built-in themes. For more information on built-in themes, see Built-in themes in Firefox — alternative to complete themes. 90009 90007 Plugins 90008 You can install the Adobe Flash plugin for video, audio, online games, and more.(Firefox automatically downloads the Google Widevine CDM for watching Digital Rights Management (DRM) controlled content and an Openh364 plugin for video calls.) 90009 90016 90017 Viewing and managing your installed add-ons 90018 90002 Search engines can be viewed and managed in the Search panel in Firefox OptionsPreferences . For other add-ons: 90003 90021 90007 Click the menu button and choose. The Add-ons Manager tab will open. 90009 90007 Select the panel for the type of add-on you wish to view or manage, such as the, or panel.90009 90026 90002 For detailed information on disabling or removing add-ons, see Disable or remove Add-ons. 90003 90002 Here is an overview to get you started: 90003 90021 90007 Firefox may offer personalized recommendations. Click the menu button , Click and select. 90009 90007 To install a featuredrecommended add-on, click the blue + Install Theme or + Add to Firefox button, depending on the type of add-on. To uninstall an add-on you just installed, click the grey Remove button.90009 90026 90002 At the top and bottom of the list of featuredrecommended add-ons, there’s also a Find more add-ons button you can click. It will take you to addons.mozilla.org where you can search for specific add-ons. 90003 90039 For advanced users 90040: You can also install add-ons from a file. If you saved the installer file to your computer, (for example, an .xpi or .jar file) you can install the add-on using the gear icon in the upper-right area of ​​the Add-on Manager panel.Select from the menu, then find and select the file. 90002 Some extensions place a button in the toolbar after installation. You can remove those or move them into the menu if you want — see Customize Firefox controls, buttons and toolbars. 90003 90002 For information on troubleshooting problems with extensions, plugins, or themes, see the articles below. 90003 90017 Problems with installing or uninstalling add-ons 90018 90017 Problems caused by add-ons 90018 .90000 offline installation of add-ons | Firefox Support Forum 90001 90002 Chosen Solution 90003 90004 90005 Right-click 90006 the extension download link (in Mozilla Add-ons, where it says «Download Now»), select «Save Link As …» and download / SAVE the .xpi file to your computer in a location where you can find it later for step 1 or 2 below. Then you can do one of the following: 90007 90008 90009 You can then manually install it by dragging the file onto an open Firefox window, 90010 90005 OR 90006 90013 90014 90009 90016 Open the Add-ons window (Tools> Add-ons> Extensions), click the «Install» button at the bottom left, navigate to the location of the downloaded file, click / double-click on the.xpi file to install. 90017 90010 Edited by Helper7677; Install button is an option in an extension that Helper7677 has installed 90013 90014 90021 90004 See: http://support.mozilla.com/en-US/kb/unable%20to%20install%20add-ons#w_you-are-asked-to-download-the-add-on-rather-than-installing -it 90007 90024 90009 Note: you can do this even when not «asked to download rather than install» 90014 90027 90028 90004 90005 Other issues needing your attention 90006 90007 90004 The information submitted with your question indicates that you have out of date plugins with known security and stability issues that should be updated.To see the plugins submitted with your question, click «More system details …» to the right of your original question post. You can also see your plugins from the Firefox menu, Tools> Add-ons> Plugins. 90007 90024 90009 Shockwave Flash 10.1 r102 90024 90009 90010 90005 Security update version 10.2.152.26 released 2011-02-08 90006 90013 90014 90027 90014 90027 90008 90009 90005 Check your plugin versions 90006: http://www.mozilla.com/en-US/plugincheck/ 90024 90009 90005 Note: plugin check page does not have information on all plugin versions 90006 90014 90027 90014 90009 90005 Update the Flash plugin 90006 to the latest version.90024 90009 Download and SAVE to your Desktop so you can find the installer later 90014 90009 If you do not have the current version, click on the «Player Download Center» link on the «90005 Download and information 90006» or «90005 Download Manual installers 90006» below 90014 90009 After download is complete, exit Firefox 90014 90009 Click on the installer you just downloaded and install 90024 90009 Windows 7 and Vista: may need to right-click the installer and choose «Run as Administrator» 90014 90027 90014 90009 Start Firefox and check your version again or test the installation by going back to the download link below 90014 90009 90005 Download and information 90006: http: // www.adobe.com/software/flash/about/ 90024 90009 Use Firefox to go to the above site to update the Firefox plugin (will also install plugin for most other browsers; except IE) 90014 90009 Use IE to go to the above site to update the IE ActiveX 90014 90027 90014 90009 90005 Download Manual installers 90006. 90014 90027 90014 90021 90004 » ‘Right-click’ » the extension download link (in Mozilla Add-ons, where it says «Download Now»), select «Save Link As …» and download / SAVE the.xpi file to your computer in a location where you can find it later for step 1 or 2 below. Then you can do one of the following: #You can then manually install it by dragging the file onto an open Firefox window, » » ‘OR’ » » # Open the Add-ons window (Tools> Add-ons> Extensions), click the «Install» button at the bottom left, navigate to the location of the downloaded file, click / double-click on the .xpi file to install. » Edited by Helper7677; Install button is an option in an extension that Helper7677 has installed » See: http: // support.mozilla.com/en-US/kb/unable%20to%20install%20add-ons#w_you-are-asked-to-download-the-add-on-rather-than-installing-it * Note: you can do this even when not «asked to download rather than install» ———————— » ‘Other issues needing your attention’ » The information submitted with your question indicates that you have out of date plugins with known security and stability issues that should be updated. To see the plugins submitted with your question, click «More system details… «to the right of your original question post. You can also see your plugins from the Firefox menu, Tools> Add-ons> Plugins.

* Shockwave Flash 10.1 r102 ** » » ‘Security update version 10.2.152.26 released 2011-02-08’ » » # » ‘Check your plugin versions’ »: http://www.mozilla.com/en-US/plugincheck/ # * » ‘Note: plugin check page does not have information on all plugin versions’ » # » ‘Update the [[Managing the Flash plugin | Flash]] plugin’ » to the latest version.# * Download and SAVE to your Desktop so you can find the installer later # * If you do not have the current version, click on the «Player Download Center» link on the » » ‘Download and information’ »» or » » ‘Download Manual installers’ »» below # * After download is complete, exit Firefox # * Click on the installer you just downloaded and install # ** Windows 7 and Vista: may need to right-click the installer and choose «Run as Administrator» # * Start Firefox and check your version again or test the installation by going back to the download link below # * » ‘Download and information’ »: http: // www.adobe.com/software/flash/about/ # ** Use Firefox to go to the above site to update the Firefox plugin (will also install plugin for most other browsers; except IE) # ** Use IE to go to the above site to update the IE ActiveX # * » ‘Download Manual installers’ ». # ** http: //kb2.adobe.com/cps/191/tn_19166.html#main_ManualInstaller # ** Note separate links for: # *** Plugin for Firefox and most other browsers # *** ActiveX for IE 90007 90004 90010 Modified 90101 February 21, 2011 at 6:38:48 AM PST 90102 by Helper7677 90013 90007 .90000 Add-ons Overview | Heroku Dev Center 90001 90002 Last updated 13 July 2020 90003 90002 Heroku add-ons are components that support your application, such as data storage, monitoring, analytics, data processing, and more. These are fully maintained for you by either a third-party provider or by Heroku. Add-ons exist so that developers can focus on their own application logic, and not the additional complexity of keeping supporting services running at full production capacity.90003 90002 Browse the available add-ons by category in the Elements Marketplace. 90003 90002 Visit Heroku Elements to see the full list of add-ons available to Heroku developers. 90003 90002 Add-ons are installed onto applications by using the Heroku Dashboard or the CLI. Most add-ons offer multiple plans, with different features, capabilities, and prices. Add-on plans are priced by the month, and prorated to the second. 90003 90012 Basic usage 90013 90002 You can add an add-on to your app via either Dashboard or the CLI.The Elements site has instructions for both, and a CLI example is below. 90003 90002 Once one is added to your app, it is available as one or more config vars (environment variables). 90003 90018 90019 90020 90021 Addon Service 90022 90021 Default Config Var (s) 90022 90025 90026 90027 90020 90029 Heroku Postgres 90030 90029 DATABASE_URL 90030 90025 90020 90029 Example Service 90030 90029 EXAMPLESERVICE_USERNAME, EXAMPLESERVICE_PASSWORD 90030 90025 90040 90041 90002 You can see these config vars in Dashboard in the «Attachment Details» for the specific installed addon instance.90003 90002 Also, some add-ons have their own dashboard (for that specific add-on resource), which is accessible from both Dashboard and CLI. 90003 90046 CLI Installation Example 90047 90002 You can install an add-on using the 90049 heroku addons: create SERVICE 90050 command, which will provision the add-on with its provider, give the add-on a global name and give a default alias to it on your application, and set any config var the add-on provides using names based on that alias. 90003 90002 This example provisions the Heroku Redis add-on and installs it in your hypothetical app named 90049 important-app 90050.90003 90056 90049 $ heroku addons: create heroku-redis —app important-app Creating shining-calmly-4402 … done, (free) Adding shining-calmly-4402 to important-app … done Setting REDIS_URL and restarting important-app … done, v3 90050 90059 90002 The CLI output shows that the global name for the newly installed add-on is 90049 shining-calmly-4402 90050, the alias for the add-on on the application is 90049 REDIS 90050 (the default for this add-on service), and, consequently, the config var set is 90049 REDIS_URL 90050.config vars vary for each add-on and they are described in each add-on’s documentation. For example, see the Heroku Redis documentation. 90003 90002 We can see the add-on details at any time with the 90049 heroku addons 90050 command: 90003 90056 90049 $ heroku addons —app important-app === Resources for important-app Plan Name Price ———————- ——————- —— heroku-redis: hobby-dev shining-calmly-4402 free === Attachments for important-app Name Add-on Billing App —— ——————- ————- REDIS shining-calmly-4402 important-app 90050 90059 90002 The 90077 resources 90078 section lists add-ons that are owned by the application, along with relevant details about the add-on such as its plan, its global name, and its cost.The 90077 attachments 90078 section lists all the add-ons that are attached to this application (that is, that have an alias to an add-on), regardless of whether this app owns it or not. This is where we can see that 90049 REDIS 90050 is an alias to our 90049 shining-calmly-4402 90050 add-on we just installed. Right now the distinction between an add-on’s resource and its attachment might seem unnecessary, but we’ll look at some important stories in the next section below that show why it’s important.90003 90002 By installing the add-on, we’ve delegated management of any environment variable prefixed with the alias 90049 REDIS 90050 to that add-on. In the case of 90049 heroku-redis 90050 only a 90049 URL 90050 variable is used, so 90049 REDIS_URL 90050 is set by the add-on: 90003 90056 90049 $ heroku config —app important-app REDIS_URL: redis: // h: pa4kvrg6a3ah52g5akto82kil@ec2-54-204-3-133.compute-1.amazonaws.com: 6569 90050 90059 90012 Advanced usage 90013 90002 There are a few ways you can more finely control how add-ons are associated with applications.90003 90104 90105 By default an addon resource is given a haiku name such as 90049 shining-calmly-4402 90050 — but you can custom name an addon. 90108 90105 Some add-ons can have multiple names within an app 90108 90105 Some add-ons can be attached to multiple apps 90108 90113 90046 Meaningful names 90047 90002 The global name for our add-on, 90049 shining-calmly-4402 90050, is not necessarily very meaningful. Just like apps, you do not have to choose a name if you do not want to, but often it can be crucial as your application grows in complexity.90003 90002 We can give an add-on a meaningful name when it is initially created by using the 90049 —name 90050 option: 90003 90056 90049 $ heroku addons: create heroku-redis —app important-app —name important-redis Creating important-redis … done, (free) Adding important-redis to important-app … done Setting REDIS_URL and restarting important-app … done, v7 90050 90059 90002 Now, wherever the add-on instance is identified, it will have a recognizable name: 90003 90056 90049 $ heroku addons —app important-app === Resources for important-app Plan Name Price ———————- ————— —— heroku-redis: hobby-dev important-redis free === Attachments for important-app Name Add-on Billing App —— ————— ————- REDIS important-redis important-app 90050 90059 90002 Sometimes, the name of the alias is important and relevant to the application.90003 90002 For example, in the Python world, the popular task / job queue Celery can use any of several backend storage systems, including Redis. The library looks at the config var 90049 BROKER_URL 90050 by default and uses the URL transport protocol to decide which backend to use. 90003 90002 Suppose we want to use Redis as the queue backend on our 90049 important-app 90050. Because add-on config vars are prefixed with the alias, we can choose a non-default alias so that Celery easily uses our Redis instance as its backend: 90003 90056 90049 $ heroku addons: create heroku-redis —app important-app —name important-redis —as BROKER Creating important-redis… done, (free) Adding important-redis to important-app … done Setting BROKER_URL and restarting important-app … done, v9 90050 90059 90002 Alias ​​names must always conform to the same naming conventions as config vars.They must begin with a letter and can only contain uppercase alphanumeric characters or underscores. 90003 90002 As shown in the output above, we see that 90049 BROKER_URL 90050 is set on our application instead of the usual default 90049 REDIS_URL 90050. We can see this in the 90049 heroku config 90050 output too: 90003 90056 90049 $ heroku config —app important-app BROKER_URL: redis: // h: pfcs5ilk6ksc7f5nt8v62qqf1ip @ ec2-54-204-3-133.compute-1.amazonaws.com:6599 90050 90059 90002 Not all add-ons support choosing your own alias. 90003 90046 Multiple aliases / attachments 90047 90002 Sometimes, it is useful to have multiple aliases with which to refer to an add-on. As an example, suppose we want to use the same Redis instance from the previous example as a session store in addition to a task queue broker. We can achieve this with 90049 heroku addons: attach EXISTING_ADDON 90050 which links an add-on to an app with a new alias: 90003 90056 90049 $ heroku addons: attach important-redis —app important-app —as SESSION_STORE Attaching important-redis as SESSION_STORE to important-app… done Setting SESSION_STORE vars and restarting important-app … done, v10 90050 90059 90002 For convenience, you may also refer to the add-on by one of its existing aliases. For example, the command above could have been 90049 heroku addons: attach BROKER —as SESSION_STORE 90050. 90003 90002 Once the attachment is created, we can see the extra alias in 90049 heroku addons 90050 and the new config vars added as a result with 90049 heroku config 90050: 90003 90056 90049 $ heroku addons —app important-app === Resources for important-app Plan Name Price ———————- ————— —— heroku-redis: hobby-dev important-redis free === Attachments for important-app Name Add-on Billing App ————- ————— ————- BROKER important-redis important-app SESSION_STORE important-redis important-app $ Heroku config —app important-app BROKER_URL: redis: // h: pfcs5ilk6ksc7f5nt8v62qqf1ip @ ec2-54-204-3-133.compute-1.amazonaws.com:6599 SESSION_STORE_URL: redis: // h: pfcs5ilk6ksc7f5nt8v62qqf1ip@ec2-54-204-3-133.compute-1.amazonaws.com: 6599 90050 90059 90002 Note that there are two attachments listed but both correspond with the single 90049 important-redis 90050 add-on. Also note that both config vars have the same value. 90003 90002 Using multiple aliases for an add-on offers many conveniences, but it’s important to note that it might result in using higher usage of the add-on’s available resources.For instance, in the example above, you might be creating more connections to the Redis instance than you otherwise would have if you shared the connection for each usage in your application. 90003 90002 The ability to create multiple aliases can also be used to rename an alias and its corresponding config vars by creating a second attachment and then removing the original one with 90049 heroku addons: detach ATTACHMENT_NAME 90050. 90003 90002 Not all add-ons support multiple attachments to the same add-on.90003 90046 Sharing an add-on between apps 90047 90002 As shown above, the 90049 heroku addons: attach 90050 command is used to create extra aliases for an add-on on an application. We can take advantage of this to create aliases for an add-on on a 90077 different 90078 application, as long as they both have the same owner. 90003 90002 Not all add-ons can be shared between applications. 90003 90002 For example, suppose the tasks that we are enqueuing to our broker (from the earlier examples) need to be processed by a different component in a different application named 90049 important-tasker 90050.We can share the add-on with the second application using any alias we like (or the default), but let’s reuse 90049 BROKER 90050 so that we’ll understand its purpose in the future: 90003 90056 90049 $ heroku addons: attach important-redis —app important-tasker —as BROKER Attaching important-redis as BROKER to important-tasker … done Setting BROKER vars and restarting important-tasker … done, v3 90050 90059 90002 Alias ​​names must be unique on any one application but it’s perfectly fine to use the same alias on two different applications.90003 90002 90003 90002 For convenience, you may also refer to the add-on by one of its existing aliases. Since we are involving two applications, we’ll need to be specific and scope the alias by its application. For example, the command above could have been 90049 heroku addons: attach important-app :: BROKER —as SESSION_STORE —app important-tasker 90050. 90003 90002 Let’s look at the add-ons and config vars on our second application: 90003 90056 90049 $ heroku addons -a important-tasker === Resources for important-tasker There are no add-ons.=== Attachments for important-tasker Name Add-on Billing App —— ————— ————- BROKER important-redis important-app $ Heroku config -a important-tasker BROKER_URL: redis: // h: pfcs5ilk6ksc7f5nt8v62qqf1ip@ec2-54-204-3-133.compute-1.amazonaws.com: 6599 90050 90059 90002 Notice how there are no add-on resources owned by the 90049 important-tasker 90050 application but that it does have an attachment named 90049 BROKER 90050 to the add-on named 90049 important-redis 90050, which is billed to the app 90049 important-app 90050.Also note that the 90049 BROKER_URL 90050 shares a value with its kin on 90049 important-app 90050. If the add-on provider needed to change this value for any reason, both of these applications would automatically be restarted with the new value set. 90003 90046 Installing more than one of the same add-on service onto an app 90047 90002 Most add-ons are designed to be installed just once on any given application, but some add-ons can be installed multiple times. 90003 90002 For example, suppose we wanted to have our task broker and our session store backed by different instances of Redis.We might want to do this for a number of reasons, such as limiting what data is accessible when we share an add-on or because each use case has different semantics offered by different plans or different third-party providers (for example, choosing between durability and processing speed). 90003 90002 We can create a second Redis instance easily enough: 90003 90056 90049 $ heroku addons: create heroku-redis —app important-app Creating sighing-nobly-тисячі вісімсот дев’яносто один … done, (free) Adding sighing-nobly-1891 to important-app… done Setting REDIS_URL and restarting important-app … done, v11 90050 90059 90002 We can even create a third: 90003 90056 90049 $ heroku addons: create heroku-redis —app important-app Creating cooling-carefully-7273 … done, (free) Adding cooling-carefully-7273 to important-app … done Setting HEROKU_REDIS_ROSE_URL and restarting important-app … done, v12 90050 90059 90002 Note how the one installation used the default alias of 90049 REDIS 90050 while the other used 90049 HEROKU_REDIS_ROSE_URL 90050.If you do not provide an alias with 90049 —as 90050, Heroku will choose one for you. More information on how these names are chosen can be seen in the next section. 90003 90002 Since we want to use a new Redis instance for our session store, let’s replace the 90049 SESSION_STORE 90050 alias with one pointing to our new add-on: 90003 90056 90049 $ heroku addons: attach sighing-nobly-1891 —as BROKER —app important-app Attaching sighing-nobly-1891 as BROKER to important-app … ! sighing-nobly-тисячу вісімсот дев’яносто одна will overwrite BROKER_URL on important-app.! To proceed, type «important-app» or re-run this command with —confirm important-app > 90050 90059 90002 Because we are replacing an existing alias and config var, we need to confirm our intent. When we confirm, the attachment and its environment variables are replaced: 90003 90056 90049> important-app Attaching sighing-nobly-1891 as BROKER to important-app … done Setting BROKER vars and restarting important-app … done, v14 $ Heroku addons —app important-app === Resources for important-app Plan Name Price ———————- ———————- —— heroku-redis: hobby-dev cooling-carefully-7273 free heroku-redis: hobby-dev important-redis free heroku-redis: hobby-dev sighing-nobly-1891 free === Attachments for important-app Name Add-on Billing App —————— ———————- ———— — BROKER sighing-nobly-1891 important-app HEROKU_REDIS_ROSE cooling-carefully-7273 important-app REDIS sighing-nobly-тисяча вісімсот дев’яносто одна important-app SESSION_STORE important-redis important-app $ Heroku config —app important-app BROKER_URL: redis: // h: p5ip3vevv16shofgnkstglu65r9 @ ec2-54-204-3-133.compute-1.amazonaws.com:6609 HEROKU_REDIS_ROSE_URL: redis: // h: pankbrfd3va8gejrrvep7r69j0@ec2-54-204-3-133.compute-1.amazonaws.com: 6619 REDIS_URL: redis: // h: p5ip3vevv16shofgnkstglu65r9@ec2-54-204-3-133.compute-1.amazonaws.com: 6609 SESSION_STORE_URL: redis: // h: pfcs5ilk6ksc7f5nt8v62qqf1ip@ec2-54-204-3-133.compute-1.amazonaws.com: 6599 90050 90059 90002 Notice that 90049 SESSION_STORE 90050, 90049 BROKER 90050, and 90049 HEROKU_REDIS_ROSE 90050 each point to a different add-on instance and each have unique values ​​set to their corresponding config vars.Since the add-on aliased as 90049 HEROKU_REDIS_ROSE 90050 was just created as an example and the 90049 REDIS 90050 alias is redundant in our scenario, let’s remove them: 90003 90056 90049 $ heroku addons: detach REDIS —app important-app Removing REDIS attachment to sighing-nobly-1891 from important-app … done Unsetting REDIS vars and restarting important-app … done, v15 $ Heroku addons: destroy cooling-carefully-7273 ! WARNING: Destructive Action ! This command will affect the app: important-app ! To proceed, type «important-app» or re-run this command with —confirm important-app > Important-app Destroying cooling-carefully-7273 on important-app… done, (free) Removing vars for HEROKU_REDIS_ROSE from important-app and restarting … done, v16 90050 90059 90002 Notice that the 90049 addons: detach 90050 command removed an attachment alias (90049 REDIS 90050) while 90049 addons: destroy 90050 deprovisioned the add-on (90049 cooling-carefully-7273 90050) as well as any associated attachments (such as 90049 HEROKU_REDIS_ROSE 90050). 90003 90002 Now everything looks the way we want with two distinct instances, one of which is aliased as 90049 BROKER 90050 to both of our applications: 90003 90056 90049 $ heroku addons —app important-app === Resources for important-app Plan Name Price ———————- —————— —— heroku-redis: hobby-dev important-redis free heroku-redis: hobby-dev sighing-nobly-1891 free === Attachments for important-app Name Add-on Billing App ————- —————— ————- BROKER sighing-nobly-1891 important-app SESSION_STORE important-redis important-app $ Heroku addons —app important-tasker === Resources for important-tasker There are no add-ons.=== Attachments for important-tasker Name Add-on Billing App —— ————— ————- BROKER important-redis important-app 90050 90059 90046 Advanced usage examples to play with 90047 90002 Here are some example use cases you can use to experiment with add-ons. These scenarios are based on real instances within Heroku itself. 90003 90104 90105 Share a secret key between two applications with the Secure Key add-on. Experiment with different installations, each for a different purpose (e.g. a session key and an encryption key). 90108 90105 Share several applications ‘Heroku Postgres databases with a single application acting as a data warehouse. Name each alias based on the app to whose database it points. 90108 90105 Share a message queue such as CloudAMQP between multiple apps to listen to events from each other. 90108 90105 Create several RedisCloud instances and observe the aliases automatically chosen. Use 90049 heroku addons: attach 90050 to replace an alias that already exists so you can change which instance your application uses.90108 90105 Replace a RedisCloud instance with a Heroku Redis instance (or vice versa) by installing it with the alias that the existing instance already uses. 90108 90105 Try to remove the only alias to an add-on and observe the error message. 90108 90113 90012 Details 90013 90046 What an app developer can do with add-ons 90047 90104 90105 Install any number of add-ons to an application. 90108 90105 Install multiple instances of the same add-on to the same application, in some cases.90108 90105 Share certain add-ons between multiple applications that have the same owner. 90108 90105 Log in to the add-on dashboard for more actions. 90108 90113 90046 What add-ons can do with your app 90047 90002 An add-on can interact with your Heroku application (s) in a few ways, including: 90003 90104 90105 Add and update specific config vars to the application (s) using the add-on. 90108 90105 Write to logs. 90108 90105 Read logs. 90108 90105 Listen to deploy events.90108 90105 Listen to domain add or remove events. 90108 90105 View app information. 90108 90105 View app owner information. 90108 90113 90046 Attachment names / aliases 90047 90002 When installing or attaching add-ons, the attachment must have a name / alias that is unique to that application. This is so that we can distinguish between multiple attachments for the same add-on and so that the config vars do not conflict. 90003 90002 Here are some examples of how config vars are computed: 90003 90018 90019 90020 90021 Addon service 90022 90021 Default attachment name 90022 90021 Suffix (es) 90022 90021 Default config var 90022 90025 90026 90027 90020 90029 Heroku Postgres 90030 90029 database 90030 90029 _url 90030 90029 DATABASE_URL 90030 90025 90020 90029 Example Service 90030 90029 exampleservice 90030 90029 _username, _password 90030 90029 EXAMPLESERVICE_USERNAME, EXAMPLESERVICE_PASSWORD 90030 90025 90040 90041 90002 In order to minimise the decisions you 90077 must 90078 make when installing an add-on, Heroku automatically assigns aliases based on a few simple rules to handle naming conflicts.90003 90002 In essence, an attachment name is chosen as follows: 90003 90426 90105 90002 The user’s choice, if provided. 90003 90002 If provided but presents a conflict, confirmation to overwrite it is requested. 90003 90108 90105 90002 The default alias, as selected by the add-on provider, if available. 90003 90002 Usually, this is a derivative of the name of the add-on service (e.g. IronCache’s service name is 90049 iron_cache 90050 and its default alias is 90049 IRON_CACHE 90050, while Heroku Postgres ‘service name is 90049 heroku-postgresql 90050 but its chosen default alias is 90049 DATABASE 90050 not 90049 HEROKU_POSTGRESQL 90050).90003 90108 90105 90002 A generated alias based on the add-on service name and a random color. 90003 90002 For example, when 90049 DATABASE 90050 is already taken, a name like 90049 HEROKU_POSTGRESQL_CYAN 90050 is chosen for Heroku Postgres; and when 90049 REDISCLOUD 90050 is already taken, a name like 90049 REDISCLOUD_BLUE 90050 is chosen for the add-on RedisCloud. 90003 90108 90463 90002 You may always provide your own alias with the 90049 —as 90050 option when running 90049 heroku addons: create 90050 or 90049 heroku addons: attach 90050.The name must be unique within the scope of that application otherwise you may be presented with a confirmation to overwrite the existing one. 90003 90002 Furthermore, when an identifier for an add-on instance (such as 90049 important-redis 90050) is expected in a command, you may also use any known alias for that add-on as an identifier. The add-on is resolved by looking at the current application and the provided alias. If you need to refer to an add-on by an alias on a different application, you may use the long form version of 90049 app-name :: ALIAS 90050.90003 90002 Be careful when using the attachment name in destructive commands as it can be easy to forget you are operating on the add-on as a whole. For instance the command 90049 heroku addons: destroy SOME_ATTACHMENT 90050 actually uninstalls the add-on (after confirmation) and might be mistaken for 90049 heroku addons: detach SOME_ATTACHMENT 90050 which just removes a single alias. 90003 90046 Config var values ​​can change 90047 90002 A config var provides your application with information on how to access the add-on service.An add-on config var is typically in a URL format, encoding credentials, host and port information, resource names, and even protocol information (such as in the example above). 90003 90002 Because add-ons have access to their config vars within your application, they can change them in some cases, such as in the event of a failure of underlying infrastructure that would necessitate a failover. In such a case, the add-on provider may switch the service over to a different part of their infrastructure and communicate this change by updating the value of the corresponding config var.90003 90002 When a config var changes, the application is automatically restarted with the resulting release. It is therefore important that applications neither use hard-coded add-on config var values ​​in code or configuration, nor cache config var values ​​during their build, in order to keep interruption of service as minimal as possible. Config vars should always dynamically be read at runtime or during application startup instead. 90003 .