<?xml version="1.0" encoding="UTF-8"?> <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom"> <id>tag:devcenter.heroku.com,2005:/articles/feed</id> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com"/> <link rel="self" type="application/atom+xml" href="https://devcenter.heroku.com/articles/feed"/> <title>Heroku Dev Center Articles</title> <author> <name>Heroku</name> </author> <updated>2025-02-13T22:20:32Z</updated> <entry> <id>tag:devcenter.heroku.com,2005:Article/8680</id> <published>2025-02-13T22:20:32Z</published> <updated>2025-02-13T22:33:43Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/stratisai"/> <title>Stratis AI</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/stratisai"&gt;Stratis AI&lt;/a&gt; is an add-on that brings conversational AI to your Heroku applications. With Stratis AI, you can enable natural language interactions with your data, websites, and documents, to provide users access to knowledge and insights.&lt;/p&gt; &lt;p&gt;Adding Stratis AI to your Heroku app can:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;strong&gt;Turn Websites Into Knowledge&lt;/strong&gt;: Make your website’s information accessible through conversational interactions.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Search Documents Instantly&lt;/strong&gt;: Integrate AWS S3 documents for instant AI-powered search.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Talk to Your Heroku Database&lt;/strong&gt;: Query &lt;a href="https://devcenter.heroku.com/articles/heroku-postgresql"&gt;Heroku Postgres&lt;/a&gt; databases in plain language with no SQL required (available at GA).&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Engage Conversationally with Data Cloud &amp;amp; Customer 360&lt;/strong&gt;: Unlock &lt;a href="https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud.htm&amp;amp;type=5"&gt;Salesforce Data Cloud&lt;/a&gt; insights with conversational access (available at GA).&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Build Custom Agents&lt;/strong&gt;: Create agentic experiences tailored to your business needs.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Bring the Conversation Anywhere&lt;/strong&gt;: Deploy chat functionality to any Heroku app with a simple JavaScript integration.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Converse in Any Language&lt;/strong&gt;: Create agentic experiences in any language around the globe.&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="getting-started-core-concepts"&gt;Getting Started: Core Concepts&lt;/h2&gt; &lt;p&gt;Here are some Stratis AI concepts to get familiar with:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;An &lt;strong&gt;Agent&lt;/strong&gt; is a combination of one of more &lt;strong&gt;Actions&lt;/strong&gt; that powers a digital assistant or chatbot.&lt;/li&gt; &lt;li&gt;An &lt;strong&gt;Action&lt;/strong&gt; determines what your agents can do with a &lt;strong&gt;Knowledge Source&lt;/strong&gt;.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Knowledge Sources&lt;/strong&gt; are where an agent retrieves information from. In the beta, you can create knowledge sources from documents, such as a S3 drive, and web content, such as website URLs.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;In the beta release, you can create an agentic digital assistant that knows about two types of knowledge: documents and web content. After provisioning our add-on, see the &lt;a href="#building-your-agents"&gt;Building Your Agents&lt;/a&gt; section where we:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Create two &lt;strong&gt;Knowledge Sources&lt;/strong&gt;: an uploaded PDF and a specified website&lt;/li&gt; &lt;li&gt;Create two &lt;strong&gt;Actions&lt;/strong&gt;: a doc action and a web action&lt;/li&gt; &lt;li&gt;Create an &lt;strong&gt;Agent&lt;/strong&gt; and add the two &lt;strong&gt;Actions&lt;/strong&gt; to it&lt;/li&gt; &lt;li&gt;Create a digital assistant or chatbot &lt;strong&gt;Deployment&lt;/strong&gt; and see our new &lt;strong&gt;Agent&lt;/strong&gt; in action.&lt;/li&gt; &lt;li&gt;Optionally, deploy our &lt;strong&gt;Agent&lt;/strong&gt; to a sample Heroku app using the included &lt;strong&gt;Heroku Button&lt;/strong&gt; so we can test it live.&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the Add-on&lt;/h2&gt; &lt;p&gt;Attach Stratis AI to a Heroku application via the CLI:&lt;/p&gt; &lt;div class="callout"&gt; &lt;p&gt;Reference the &lt;a href="https://elements.heroku.com/addons/stratisai"&gt;Stratis AI Elements Page&lt;/a&gt; for a list of available plans and regions.&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create stratisai:PLAN --app HEROKU_APP_NAME Creating stratisai on ⬢ HEROKU_APP_NAME... free All set! To get started, run `heroku addons:open stratisai -a HEROKU_APP_NAME`. &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;After provisioning Stratis AI, the &lt;code&gt;STRATISAI_ORG_ID&lt;/code&gt; config var is available in the attached app’s configuration. It contains the unique identifier for the Stratis organization created for your Heroku app. For now, you can ignore this config var, but it can come in handy for referencing it during a support issue during troubleshooting. You can see the config var via the &lt;code&gt;heroku config:get&lt;/code&gt; command:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku config:get STRATISAI_ORG_ID -a HEROKU_APP_NAME f9b807aa-84ba-4b00-b234-00806c5f0155 &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="accessing-the-admin-dashboard"&gt;Accessing the Admin Dashboard&lt;/h2&gt; &lt;p&gt;After provision the add-on, access the admin dashboard via the browser or CLI:&lt;/p&gt; &lt;h3 id="via-browser"&gt;Via Browser&lt;/h3&gt; &lt;ol&gt; &lt;li&gt;Navigate to the &lt;strong&gt;&lt;code&gt;Resources&lt;/code&gt;&lt;/strong&gt; tab of your app in the Heroku Dashboard.&lt;/li&gt; &lt;li&gt;Select the &lt;strong&gt;&lt;code&gt;Stratis AI&lt;/code&gt;&lt;/strong&gt; resource to open the Stratis AI dashboard in a new window.&lt;/li&gt; &lt;/ol&gt; &lt;h3 id="via-command-line"&gt;Via Command Line&lt;/h3&gt; &lt;p&gt;Access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:open stratisai -a HEROKU_APP_NAME &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="building-your-agents"&gt;Building Your Agents&lt;/h2&gt; &lt;p&gt;The &lt;strong&gt;&lt;code&gt;Setup Wizard&lt;/code&gt;&lt;/strong&gt; guides you through configuring and deploying your conversational agents in four steps. This process ensures an easy experience, even for users with limited technical expertise.&lt;/p&gt; &lt;ol&gt; &lt;li&gt;&lt;a href="#connect-your-knowledge-sources"&gt;Connect Your Knowledge Sources&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="#define-your-actions-tools"&gt;Define Your Actions (Tools)&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="#assemble-agents"&gt;Assemble Agents&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="#deploying-conversational-agents"&gt;Deploying Conversational Agents&lt;/a&gt;&lt;/li&gt; &lt;/ol&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842761-sai-setup-wizard.png" alt="Stratis AI setup wizard"&gt;&lt;/p&gt; &lt;h3 id="connect-your-knowledge-sources"&gt;Connect Your Knowledge Sources&lt;/h3&gt; &lt;p&gt;The Stratis AI beta supports multiple knowledge sources including:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;AWS S3 Buckets: add and schedule periodic ingestion from your S3 documents.&lt;/li&gt; &lt;li&gt;Websites: enable web ingestion for real-time data updates.&lt;/li&gt; &lt;/ul&gt; &lt;div class="callout"&gt; &lt;p&gt;An additional library of tools and knowledge sources are available at GA.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;To create a knowledge source:&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Select the type of source, for example, AWS S3 or website.&lt;/li&gt; &lt;li&gt;Enter the required credentials, for example, S3 keys or API URLs.&lt;/li&gt; &lt;li&gt;Choose a synchronization schedule, for example, daily, weekly, or monthly.&lt;/li&gt; &lt;li&gt;Click &lt;strong&gt;&lt;code&gt;Submit&lt;/code&gt;&lt;/strong&gt;.&lt;/li&gt; &lt;/ol&gt; &lt;p&gt;Our example shows the configuration for creating a web source with an hourly sync schedule.&lt;/p&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842760-sai-add-web-source.png" alt="Creating a Stratis AI web source"&gt;&lt;/p&gt; &lt;p&gt;You can view and edit your web sources via the list view after creating them.&lt;/p&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842761-sai-web-sources.png" alt="Viewing Stratis AI web sources"&gt;&lt;/p&gt; &lt;p&gt;After configuring your knowledge sources, an automatic process triggers to crawl the source and then vectorize the information into &lt;a href="https://github.com/pgvector/pgvector"&gt;&lt;code&gt;pgvector&lt;/code&gt;&lt;/a&gt;. During this process, you can select the knowledge source and view the progress. Usually, the crawl is very fast and depending on the size of the source, the vectorization follows shortly.&lt;/p&gt; &lt;h3 id="define-your-actions-tools"&gt;Define Your Actions (Tools)&lt;/h3&gt; &lt;p&gt;Actions are the building blocks of your agents. They determine what your agents can do with the configured data sources. For example:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Retrieving specific documents from AWS S3.&lt;/li&gt; &lt;li&gt;Searching website content.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;To create an action in the setup wizard:&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Select a knowledge source you created.&lt;/li&gt; &lt;li&gt;Select the specific additional configuration, such as the query or function the action performs if applicable.&lt;/li&gt; &lt;li&gt;Add a meaningful name and description to help agents use it.&lt;/li&gt; &lt;li&gt;Click &lt;strong&gt;&lt;code&gt;Submit&lt;/code&gt;&lt;/strong&gt;.&lt;/li&gt; &lt;/ol&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842760-sai-add-action.png" alt="Creating a Stratis AI action"&gt;&lt;/p&gt; &lt;h3 id="assemble-agents"&gt;Assemble Agents&lt;/h3&gt; &lt;p&gt;Agents combine specific actions to perform meaningful tasks. You can customize agents to fit different workflows or business needs.&lt;/p&gt; &lt;p&gt;To create an agent in the wizard:&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Assign one or more actions you created to the agent.&lt;/li&gt; &lt;li&gt;Select a language or processing capabilities for the agent.&lt;/li&gt; &lt;li&gt;Add optional details like a custom persona or branding logo.&lt;/li&gt; &lt;li&gt;Click &lt;strong&gt;&lt;code&gt;Submit&lt;/code&gt;&lt;/strong&gt;.&lt;/li&gt; &lt;/ol&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842760-sai-add-agent.png" alt="Creating a Stratis AI agent"&gt;&lt;/p&gt; &lt;p&gt;In the &lt;strong&gt;&lt;code&gt;Agents&lt;/code&gt;&lt;/strong&gt; page, you can test an ad-hoc conversation with the agent by clicking the message icon. Use this feature to validate your agent before making it available to a deployed chat interface.&lt;/p&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842760-sai-agent-admin-chat.png" alt="Chatting with a Stratis AI agent in the admin UI"&gt;&lt;/p&gt; &lt;h2 id="deploying-conversational-agents"&gt;Deploying Conversational Agents&lt;/h2&gt; &lt;p&gt;Deploy your agents to interact with users via &lt;strong&gt;Conversational Agents&lt;/strong&gt;. You can embed these interfaces into your website via manual code insertion or a &lt;a href="https://devcenter.heroku.com/articles/heroku-button"&gt;Heroku Button&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;During this beta, you can deploy your conversational agents by placing a small JavaScript snippet the Stratis AI add-on provides into your web or mobile app. If you have any questions on where to place this snippet, you can reach out to us at &lt;a href="mailto:support@stratisglobal.com"&gt;support@stratisglobal.com&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;To simplify this process, we’re providing a sample site deployment method that includes your created agent using a Heroku Button. To see your agent running on this sample site, click the Heroku Button on the &lt;strong&gt;&lt;code&gt;Deploy Agent Chat Interfaces&lt;/code&gt;&lt;/strong&gt; page, or from &lt;strong&gt;&lt;code&gt;Operate → Deployments&lt;/code&gt;&lt;/strong&gt; in the Admin UI.&lt;/p&gt; &lt;p&gt;Either way, begin by creating the conversational agent in the setup wizard:&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Add a meaningful name and icon for your chat interface.&lt;/li&gt; &lt;li&gt;Assign one or more agents you created to the chat interface.&lt;/li&gt; &lt;li&gt;Optionally, provide a list of website domains your chat interface can be on.&lt;/li&gt; &lt;li&gt;Click &lt;strong&gt;&lt;code&gt;Submit&lt;/code&gt;&lt;/strong&gt;.&lt;/li&gt; &lt;/ol&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842760-sai-add-chat-client.png" alt="Creating a Stratis AI chat interface"&gt;&lt;/p&gt; &lt;h3 id="deploying-via-code-change"&gt;Deploying via Code Change&lt;/h3&gt; &lt;p&gt;To deploy via a code change:&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Grab the generated code snippet from the &lt;strong&gt;&lt;code&gt;Setup Wizard&lt;/code&gt;&lt;/strong&gt; by clicking the copy icon under the &lt;strong&gt;&lt;code&gt;Message&lt;/code&gt;&lt;/strong&gt; column on the chat interface’s row. You can also visually inspect the code snippet by clicking the pencil icon.&lt;/li&gt; &lt;li&gt;Insert the code snippet into your website’s code, specifically inside the &lt;code&gt;&amp;lt;body&amp;gt;&lt;/code&gt; of the HTML. This step varies based on your chosen web framework. Reach out at &lt;a href="mailto:support@stratisglobal.com"&gt;support@stratisglobal.com&lt;/a&gt; for help.&lt;/li&gt; &lt;/ol&gt; &lt;h3 id="deploying-via-heroku-button"&gt;Deploying via Heroku Button&lt;/h3&gt; &lt;p&gt;To deploy via a Heroku Button, click the &lt;strong&gt;&lt;code&gt;Deploy to Heroku&lt;/code&gt;&lt;/strong&gt; button on the chat interface row you want to deploy. This button opens up a new page where you enter a name for your app and click &lt;strong&gt;&lt;code&gt;Deploy&lt;/code&gt;&lt;/strong&gt;.&lt;/p&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842760-sai-chat-clients.ai.png" alt="Viewing Stratis AI chat interfaces"&gt;&lt;/p&gt; &lt;p&gt;After the new app deploys, click the &lt;strong&gt;&lt;code&gt;View&lt;/code&gt;&lt;/strong&gt; button to chat with your agent.&lt;/p&gt; &lt;p&gt;&lt;img src="https://assets.devcenter.heroku.com/article-images/1733842685-sai-example-chat-interface-app.png" alt="sai-example-chat-interface-app"&gt;&lt;/p&gt; &lt;h2 id="next-steps"&gt;Next Steps&lt;/h2&gt; &lt;p&gt;After successfully creating and deploying your first conversational agent, you can iterate and improve it by:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Adding knowledge sources&lt;/li&gt; &lt;li&gt;Monitoring the crawling and vectorizing of those sources&lt;/li&gt; &lt;li&gt;Adding more actions&lt;/li&gt; &lt;li&gt;Adding configurations and parameters to how your agent performs&lt;/li&gt; &lt;li&gt;Testing your agents for accuracy and performance&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the Add-on&lt;/h2&gt; &lt;p&gt;Remove Stratis AI via the CLI:&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;This action destroys all associated knowledge source crawls and vectorizations, associated actions, and all agents. You can’t undo it!&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:destroy stratisai Destroying stratisai-trapezoidal-84750 on ⬢ HEROKU_APP_NAME... done &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;Submit all Stratis AI support and runtime issues via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;. Any non-support-related issues or product feedback is welcome at &lt;a href="mailto:support@stratisglobal.com"&gt;support@stratisglobal.com&lt;/a&gt;.&lt;/p&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8155</id> <published>2025-02-11T09:23:41Z</published> <updated>2025-02-14T17:51:45Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/ah-grafana-stackhero"/> <title>Stackhero for Grafana</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/ah-grafana-stackhero"&gt;Stackhero for Grafana&lt;/a&gt; provides a managed Grafana service running on a fully dedicated instance.&lt;/p&gt; &lt;p&gt;The &lt;a href="https://elements.heroku.com/addons/ah-grafana-stackhero"&gt;Stackhero for Grafana&lt;/a&gt; add-on offers various features:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A private instance (dedicated VM) for high performances and security&lt;/li&gt; &lt;li&gt;TLS encryption (aka SSL)&lt;/li&gt; &lt;li&gt;An automatic backup every 24 hours&lt;/li&gt; &lt;li&gt;One click to update to new Grafana versions&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the add-on&lt;/h2&gt; &lt;p&gt;Stackhero for Grafana can be attached to a Heroku application via the CLI:&lt;/p&gt; &lt;div class="callout"&gt; &lt;p&gt;For more information about available plans, see &lt;a href="https://elements.heroku.com/addons/ah-grafana-stackhero"&gt;Stackhero for Grafana&lt;/a&gt;.&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create --wait ah-grafana-stackhero --app &amp;lt;your app name&amp;gt; Creating ah-grafana-stackhero... Your add-on is being provisioned on Stackhero. It will be available in around 2 minutes. &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="connecting-to-the-stackhero-dashboard"&gt;Connecting to the Stackhero Dashboard&lt;/h2&gt; &lt;p&gt;View your instance usage, restart it, and apply updates with the Stackhero dashboard. You can access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:open ah-grafana-stackhero Opening ah-grafana-stackhero for sharp-mountain-4005 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can also visit the &lt;a href="https://dashboard.heroku.com/apps"&gt;Heroku Dashboard&lt;/a&gt;, select your application, and then select &lt;strong&gt;&lt;code&gt;Stackhero for Grafana&lt;/code&gt;&lt;/strong&gt; from the &lt;strong&gt;&lt;code&gt;Add-ons&lt;/code&gt;&lt;/strong&gt; menu.&lt;/p&gt; &lt;h2 id="upgrading-your-plan"&gt;Upgrading Your Plan&lt;/h2&gt; &lt;div class="warning"&gt; &lt;p&gt;You can’t downgrade an existing add-on.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;heroku addons:upgrade&lt;/code&gt; command to migrate to a new plan.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:upgrade ah-grafana-stackhero:newplan -----&amp;gt; Upgrading ah-grafana-stackhero:newplan to sharp-mountain-4005... done Your plan has been updated to: ah-grafana-stackhero:newplan &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the Add-on&lt;/h2&gt; &lt;p&gt;You can remove Stackhero for Grafana via the CLI:&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;This destroys all associated data and can’t be undone!&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:destroy ah-grafana-stackhero -----&amp;gt; Removing ah-grafana-stackhero from sharp-mountain-4005... done &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;You can submit support and runtime issues for Stackhero for Grafana via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;. For urgent issues, CC support@stackhero.io.&lt;/p&gt; &lt;h2 id="additional-resources"&gt;Additional Resources&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Grafana/documentations"&gt;Grafana documentation by Stackhero&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Grafana/benefits"&gt;Grafana cloud&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8151</id> <published>2025-02-11T09:23:34Z</published> <updated>2025-02-14T17:50:59Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/ah-matomo-stackhero"/> <title>Stackhero for Matomo</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/ah-matomo-stackhero"&gt;Stackhero for Matomo&lt;/a&gt; provides a managed Matomo service running on a fully dedicated instance.&lt;/p&gt; &lt;p&gt;The &lt;a href="https://elements.heroku.com/addons/ah-matomo-stackhero"&gt;Stackhero for Matomo&lt;/a&gt; add-on provides the following features:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A private instance (dedicated VM) for high performances and security&lt;/li&gt; &lt;li&gt;TLS encryption (aka SSL)&lt;/li&gt; &lt;li&gt;An automatic backup every 24 hours&lt;/li&gt; &lt;li&gt;One click to update to new Matomo versions&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the add-on&lt;/h2&gt; &lt;p&gt;Stackhero for Matomo can be attached to a Heroku application via the CLI:&lt;/p&gt; &lt;div class="callout"&gt; &lt;p&gt;For more information about available plans, see &lt;a href="https://elements.heroku.com/addons/ah-matomo-stackhero"&gt;Stackhero for Matomo&lt;/a&gt;.&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create --wait ah-matomo-stackhero --app &amp;lt;your app name&amp;gt; Creating ah-matomo-stackhero... Your add-on is being provisioned on Stackhero. It will be available in around 2 minutes. &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="connecting-to-the-stackhero-dashboard"&gt;Connecting to the Stackhero Dashboard&lt;/h2&gt; &lt;p&gt;View your instance usage, restart it, and apply updates with the Stackhero dashboard. You can access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:open ah-matomo-stackhero Opening ah-matomo-stackhero for sharp-mountain-4005 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can also visit the &lt;a href="https://dashboard.heroku.com/apps"&gt;Heroku Dashboard&lt;/a&gt;, select your application, and then select &lt;strong&gt;&lt;code&gt;Stackhero for Matomo&lt;/code&gt;&lt;/strong&gt; from the &lt;strong&gt;&lt;code&gt;Add-ons&lt;/code&gt;&lt;/strong&gt; menu.&lt;/p&gt; &lt;h2 id="upgrading-your-plan"&gt;Upgrading Your Plan&lt;/h2&gt; &lt;div class="warning"&gt; &lt;p&gt;You can’t downgrade an existing add-on.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;heroku addons:upgrade&lt;/code&gt; command to migrate to a new plan.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:upgrade ah-matomo-stackhero:newplan -----&amp;gt; Upgrading ah-matomo-stackhero:newplan to sharp-mountain-4005... done Your plan has been updated to: ah-matomo-stackhero:newplan &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the Add-on&lt;/h2&gt; &lt;p&gt;You can remove Stackhero for Matomo via the CLI:&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;This destroys all associated data and can’t be undone!&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:destroy ah-matomo-stackhero -----&amp;gt; Removing ah-matomo-stackhero from sharp-mountain-4005... done &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;You can submit support and runtime issues for Stackhero for Matomo via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;. For urgent issues, CC support@stackhero.io.&lt;/p&gt; &lt;h2 id="additional-resources"&gt;Additional Resources&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Matomo/documentations"&gt;Matomo documentation&lt;/a&gt; by Stackhero&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Matomo/benefits"&gt;Matomo managed cloud&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8150</id> <published>2025-02-11T09:23:33Z</published> <updated>2025-02-14T17:51:13Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/ah-opensearch-stackhero"/> <title>Stackhero for OpenSearch</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/ah-opensearch-stackhero"&gt;Stackhero for OpenSearch&lt;/a&gt; provides a managed OpenSearch service running on a fully dedicated instance.&lt;/p&gt; &lt;p&gt;With the &lt;a href="https://elements.heroku.com/addons/ah-opensearch-stackhero"&gt;Stackhero for OpenSearch&lt;/a&gt; add-on, you’ll get:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A private instance (dedicated VM) for high performances and security&lt;/li&gt; &lt;li&gt;TLS encryption (aka SSL)&lt;/li&gt; &lt;li&gt;An automatic backup every 24 hours&lt;/li&gt; &lt;li&gt;One click to update to new OpenSearch versions&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the add-on&lt;/h2&gt; &lt;p&gt;Stackhero for OpenSearch can be attached to a Heroku application via the CLI:&lt;/p&gt; &lt;div class="callout"&gt; &lt;p&gt;For more information about available plans, see &lt;a href="https://elements.heroku.com/addons/ah-opensearch-stackhero"&gt;Stackhero for OpenSearch&lt;/a&gt;.&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create --wait ah-opensearch-stackhero --app &amp;lt;your app name&amp;gt; Creating ah-opensearch-stackhero... Your add-on is being provisioned on Stackhero. It will be available in around 2 minutes. &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="connecting-to-the-stackhero-dashboard"&gt;Connecting to the Stackhero Dashboard&lt;/h2&gt; &lt;p&gt;View your instance usage, restart it, and apply updates with the Stackhero dashboard. You can access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:open ah-opensearch-stackhero Opening ah-opensearch-stackhero for sharp-mountain-4005 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can also visit the &lt;a href="https://dashboard.heroku.com/apps"&gt;Heroku Dashboard&lt;/a&gt;, select your application, and then select &lt;strong&gt;&lt;code&gt;Stackhero for OpenSearch&lt;/code&gt;&lt;/strong&gt; from the &lt;strong&gt;&lt;code&gt;Add-ons&lt;/code&gt;&lt;/strong&gt; menu.&lt;/p&gt; &lt;h2 id="upgrading-your-plan"&gt;Upgrading Your Plan&lt;/h2&gt; &lt;div class="warning"&gt; &lt;p&gt;You can’t downgrade an existing add-on.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;heroku addons:upgrade&lt;/code&gt; command to migrate to a new plan.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:upgrade ah-opensearch-stackhero:newplan -----&amp;gt; Upgrading ah-opensearch-stackhero:newplan to sharp-mountain-4005... done Your plan has been updated to: ah-opensearch-stackhero:newplan &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the Add-on&lt;/h2&gt; &lt;p&gt;You can remove Stackhero for OpenSearch via the CLI:&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;This destroys all associated data and can’t be undone!&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:destroy ah-opensearch-stackhero -----&amp;gt; Removing ah-opensearch-stackhero from sharp-mountain-4005... done &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;You can submit support and runtime issues for Stackhero for OpenSearch via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;. For urgent issues, CC support@stackhero.io.&lt;/p&gt; &lt;h2 id="additional-resources"&gt;Additional Resources&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/OpenSearch/documentations"&gt;OpenSearch documentation by Stackhero&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/OpenSearch/benefits"&gt;OpenSearch managed cloud&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8152</id> <published>2025-02-11T09:23:33Z</published> <updated>2025-02-14T17:51:26Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/ah-prometheus-stackhero"/> <title>Stackhero for Prometheus</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/ah-prometheus-stackhero"&gt;Stackhero for Prometheus&lt;/a&gt; provides a managed Prometheus service running on a fully dedicated instance.&lt;/p&gt; &lt;p&gt;The &lt;a href="https://elements.heroku.com/addons/ah-prometheus-stackhero"&gt;Stackhero for Prometheus&lt;/a&gt; add-on offers various features:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A private instance (dedicated VM) for high performances and security&lt;/li&gt; &lt;li&gt;TLS encryption (aka SSL)&lt;/li&gt; &lt;li&gt;An automatic backup every 24 hours&lt;/li&gt; &lt;li&gt;One click to update to new Prometheus versions&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the add-on&lt;/h2&gt; &lt;p&gt;Stackhero for Prometheus can be attached to a Heroku application via the CLI:&lt;/p&gt; &lt;div class="callout"&gt; &lt;p&gt;For more information about available plans, see &lt;a href="https://elements.heroku.com/addons/ah-prometheus-stackhero"&gt;Stackhero for Prometheus&lt;/a&gt;.&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create --wait ah-prometheus-stackhero --app &amp;lt;your app name&amp;gt; Creating ah-prometheus-stackhero... Your add-on is being provisioned on Stackhero. It will be available in around 2 minutes. &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="connecting-to-the-stackhero-dashboard"&gt;Connecting to the Stackhero Dashboard&lt;/h2&gt; &lt;p&gt;View your instance usage, restart it, and apply updates in the Stackhero dashboard. You can access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:open ah-prometheus-stackhero Opening ah-prometheus-stackhero for sharp-mountain-4005 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can also visit the &lt;a href="https://dashboard.heroku.com/apps"&gt;Heroku Dashboard&lt;/a&gt;, select your application, and then select &lt;strong&gt;&lt;code&gt;Stackhero for Prometheus&lt;/code&gt;&lt;/strong&gt; from the &lt;strong&gt;&lt;code&gt;Add-ons&lt;/code&gt;&lt;/strong&gt; menu.&lt;/p&gt; &lt;h2 id="upgrading-your-plan"&gt;Upgrading Your Plan&lt;/h2&gt; &lt;div class="warning"&gt; &lt;p&gt;You can’t downgrade an existing add-on.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;heroku addons:upgrade&lt;/code&gt; command to migrate to a new plan.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:upgrade ah-prometheus-stackhero:newplan -----&amp;gt; Upgrading ah-prometheus-stackhero:newplan to sharp-mountain-4005... done Your plan has been updated to: ah-prometheus-stackhero:newplan &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the Add-on&lt;/h2&gt; &lt;p&gt;You can remove Stackhero for Prometheus via the CLI:&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;This destroys all associated data and can’t be undone!&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:destroy ah-prometheus-stackhero -----&amp;gt; Removing ah-prometheus-stackhero from sharp-mountain-4005... done &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;You can submit support and runtime issues for Stackhero for Prometheus via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;. For urgent issues, CC support@stackhero.io.&lt;/p&gt; &lt;h2 id="additional-resources"&gt;Additional Resources&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Prometheus/documentations"&gt;Prometheus documentation by Stackhero&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Prometheus/benefits"&gt;Prometheus cloud&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8149</id> <published>2025-02-11T09:23:24Z</published> <updated>2025-02-14T17:50:28Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/ah-valkey-stackhero"/> <title>Stackhero for Valkey</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/ah-valkey-stackhero"&gt;Stackhero for Valkey&lt;/a&gt; provides a managed Valkey instance running on a fully dedicated instance.&lt;/p&gt; &lt;p&gt;Valkey is an open-source fork of the Redis project before they changed their license. Valkey is a drop-in replacement for Redis 7.2 and previous versions.&lt;/p&gt; &lt;p&gt;With the &lt;a href="https://elements.heroku.com/addons/ah-valkey-stackhero"&gt;Stackhero for Valkey&lt;/a&gt; add-on, you’ll get:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A private instance (dedicated VM) for high performances and security&lt;/li&gt; &lt;li&gt;TLS encryption (aka SSL)&lt;/li&gt; &lt;li&gt;An automatic backup every 24 hours&lt;/li&gt; &lt;li&gt;A graphical web UI (Redis Commander)&lt;/li&gt; &lt;li&gt;One click to update to new Valkey versions&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;All Redis clients can connect to &lt;a href="https://elements.heroku.com/addons/ah-valkey-stackhero"&gt;Stackhero for Valkey&lt;/a&gt;, and there’s a Valkey/Redis client library for almost every language out there, including Ruby, Node.js, Java, Python, Clojure, and Erlang.&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;When you choose a Valkey or Redis client library, opt for one that supports TLS encryption (aka SSL) for the best security. We strongly discourage you to use Valkey without TLS support unless you know exactly what you are doing.&lt;/p&gt; &lt;/div&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the add-on&lt;/h2&gt; &lt;p&gt;Stackhero for Valkey can be attached to a Heroku application via the CLI:&lt;/p&gt; &lt;div class="callout"&gt; &lt;p&gt;A list of all plans available can be found &lt;a href="https://elements.heroku.com/addons/ah-valkey-stackhero"&gt;here&lt;/a&gt;.&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create --wait ah-valkey-stackhero --app &amp;lt;your app name&amp;gt; Creating ah-valkey-stackhero... Your add-on is being provisioned on Stackhero. It will be available in around 2 minutes. &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;After you provision Stackhero for Valkey, the &lt;code&gt;STACKHERO_VALKEY_URL_TLS&lt;/code&gt; and &lt;code&gt;STACKHERO_VALKEY_URL_CLEAR&lt;/code&gt; config variables are available in your app’s configuration. They contain the URLs to your Valkey instance as its credentials.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;code&gt;STACKHERO_VALKEY_URL_TLS&lt;/code&gt; is the URL to your Valkey instance with TLS encryption. We recommend you use this URL to connect to your Valkey instance.&lt;/li&gt; &lt;li&gt;&lt;code&gt;STACKHERO_VALKEY_URL_CLEAR&lt;/code&gt; is the URL to your Valkey instance with &lt;em&gt;no encryption&lt;/em&gt; (clear).&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;You can see the content of those variables via the &lt;code&gt;heroku config:get&lt;/code&gt; command:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku config:get STACKHERO_VALKEY_URL_TLS rediss://user:password@domain:port &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;After you install Stackhero for Valkey, you must configure your application to fully integrate with the add-on.&lt;/p&gt; &lt;h2 id="local-setup"&gt;Local setup&lt;/h2&gt; &lt;p&gt;After you provision the add-on, it’s necessary to locally replicate its config variables so your development environment can operate against the service.&lt;/p&gt; &lt;p&gt;Use the Heroku Local command-line tool to configure, run, and manage process types specified in your app’s &lt;a href="https://devcenter.heroku.com/articles/procfile"&gt;Procfile&lt;/a&gt;. Heroku Local reads configuration variables from a &lt;code&gt;.env&lt;/code&gt; file. To view all of your app’s config variables, type &lt;code&gt;heroku config&lt;/code&gt;. Use these commands for each value that you want to add to your &lt;code&gt;.env&lt;/code&gt; file:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku config:get STACKHERO_VALKEY_URL_TLS -s &amp;gt;&amp;gt; .env $ heroku config:get STACKHERO_VALKEY_URL_CLEAR -s &amp;gt;&amp;gt; .env &lt;/code&gt;&lt;/pre&gt; &lt;div class="warning"&gt; &lt;p&gt;Credentials and other sensitive configuration values should not be committed to source-control. In Git, exclude the &lt;code&gt;.env&lt;/code&gt; file with: &lt;code&gt;echo .env &amp;gt;&amp;gt; .gitignore&lt;/code&gt;.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;For more information, see &lt;a href="https://devcenter.heroku.com/articles/heroku-local"&gt;Running Apps Locally&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="configure-valkey-on-java"&gt;Configure Valkey on Java&lt;/h2&gt; &lt;p&gt;You can use the environment variable &lt;code&gt;STACKHERO_VALKEY_URL_TLS&lt;/code&gt; to connect to Valkey.&lt;/p&gt; &lt;p&gt;Here’s an example of a connection using Jedis:&lt;/p&gt; &lt;pre class="language-java"&gt;&lt;code class="language-java"&gt;private static Jedis getConnection() throws URISyntaxException { URI valkeyURI = new URI(System.getenv("STACKHERO_VALKEY_URL_TLS")); Jedis jedis = new Jedis(valkeyURI); return jedis; } &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;For more information, see the official &lt;a href="https://github.com/redis/jedis"&gt;Jedis repository&lt;/a&gt; and the official &lt;a href="https://github.com/redis/jedis/wiki"&gt;wiki&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;In a multithreaded environment, like a web server, use Jedis Pool:&lt;/p&gt; &lt;pre class="language-java"&gt;&lt;code class="language-java"&gt;public static JedisPool getPool() { URI valkeyURI = new URI(System.getenv("STACKHERO_VALKEY_URL_TLS")); JedisPoolConfig poolConfig = new JedisPoolConfig(); poolConfig.setMaxTotal(10); poolConfig.setMaxIdle(5); poolConfig.setMinIdle(1); poolConfig.setTestOnBorrow(true); poolConfig.setTestOnReturn(true); poolConfig.setTestWhileIdle(true); JedisPool pool = new JedisPool(poolConfig, valkeyURI); return pool; } &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;For more information, see the official &lt;a href="https://github.com/redis/jedis/wiki/Getting-started#using-jedis-in-a-multithreaded-environment"&gt;Jedis wiki&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="configure-valkey-on-ruby"&gt;Configure Valkey on Ruby&lt;/h2&gt; &lt;p&gt;Install the Redis gem:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ bundle add redis &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;With Rails, you have to create the initializer file &lt;code&gt;config/initializers/redis.rb&lt;/code&gt; like this:&lt;/p&gt; &lt;pre class="language-ruby"&gt;&lt;code class="language-ruby"&gt;$redis = Redis.new(url: ENV["STACKHERO_VALKEY_URL_TLS"]) &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;To use Valkey as a cache system, edit the &lt;code&gt;config/environments/production.rb&lt;/code&gt; file and add this line:&lt;/p&gt; &lt;pre class="language-ruby"&gt;&lt;code class="language-ruby"&gt;config.cache_store = :redis_cache_store, { url: ENV['STACKHERO_VALKEY_URL_TLS'] } &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;By default caching is only enabled on the production environment.&lt;/p&gt; &lt;p&gt;To test caching on development, edit the file &lt;code&gt;config/environments/development.rb&lt;/code&gt;, add the configuration from above, and add &lt;code&gt;config.action_controller.perform_caching = true&lt;/code&gt; to enable caching.&lt;/p&gt; &lt;p&gt;A good way to test that caching works is to start a Rails console with &lt;code&gt;bin/rails console&lt;/code&gt;, then test writing with &lt;code&gt;Rails.cache.write("foo", "bar")&lt;/code&gt;.&lt;/p&gt; &lt;/div&gt; &lt;h3 id="configure-valkey-on-sidekiq"&gt;Configure Valkey on Sidekiq&lt;/h3&gt; &lt;p&gt;To use Stackhero for Valkey as your Sidekiq Valkey server, set the environment variable &lt;code&gt;REDIS_PROVIDER&lt;/code&gt; to &lt;code&gt;STACKHERO_VALKEY_URL_TLS&lt;/code&gt;:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku config:set REDIS_PROVIDER=STACKHERO_VALKEY_URL_TLS &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Sidekiq will automatically use Stackero for Valkey then.&lt;/p&gt; &lt;h3 id="configure-valkey-on-resque"&gt;Configure Valkey on Resque&lt;/h3&gt; &lt;p&gt;Edit the file &lt;code&gt;config/resque.yml&lt;/code&gt; and replace &lt;code&gt;production: &amp;lt;%= ENV['REDIS_URL'] %&amp;gt;&lt;/code&gt; with this value:&lt;/p&gt; &lt;pre class="language-yaml"&gt;&lt;code class="language-yaml"&gt;production: &amp;lt;%= ENV['STACKHERO_VALKEY_URL_TLS'] %&amp;gt; &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Resque will then use Stackero for Valkey.&lt;/p&gt; &lt;h2 id="configure-valkey-on-python"&gt;Configure Valkey on Python&lt;/h2&gt; &lt;p&gt;Install the Redis package:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ pip install redis $ pip freeze &amp;gt; requirements.txt &lt;/code&gt;&lt;/pre&gt;&lt;pre class="language-python"&gt;&lt;code class="language-python"&gt;import os import redis r = redis.from_url(os.environ.get("STACKHERO_VALKEY_URL_TLS")) &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;For more information, see the official &lt;a href="https://pypi.org/project/redis/"&gt;Python redis package documentation&lt;/a&gt;.&lt;/p&gt; &lt;h3 id="how-to-avoid-error-connection-closed-by-server-with-valkey-and-python"&gt;How to avoid error “Connection closed by server” with Valkey and Python&lt;/h3&gt; &lt;p&gt;The error &lt;code&gt;redis.exceptions.ConnectionError: Connection closed by server&lt;/code&gt; is potentially related to the fact that your Python app doesn’t exchange data with Valkey for a certain time and the connection closes automatically. When your app tries to exchange again with Valkey, the connection doesn’t work anymore and you get the error &lt;code&gt;Connection closed by server&lt;/code&gt;.&lt;/p&gt; &lt;p&gt;To resolve this, you can pass the &lt;code&gt;health_check_interval&lt;/code&gt; setting to your Valkey connection like this:&lt;/p&gt; &lt;pre class="language-python"&gt;&lt;code class="language-python"&gt;r = redis.from_url( 'rediss://default:&amp;lt;password&amp;gt;@XXXXXX.stackhero-network.com:&amp;lt;port&amp;gt;', health_check_interval=10, socket_connect_timeout=5, retry_on_timeout=True, socket_keepalive=True ) &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;If you use the Valkey PubSub feature, the &lt;code&gt;redis-py&lt;/code&gt; library assumes that you call functions &lt;code&gt;get_message()&lt;/code&gt; or &lt;code&gt;listen()&lt;/code&gt; more frequently than the &lt;code&gt;health_check_interval&lt;/code&gt; value in seconds. In this example, &lt;code&gt;health_check_interval&lt;/code&gt; is set to 10 seconds. This means your app has to call &lt;code&gt;get_message()&lt;/code&gt; or &lt;code&gt;listen()&lt;/code&gt; at least one time each 10 seconds. For more information, see the &lt;a href="https://github.com/redis/redis-py#connections"&gt;redis-py official documentation&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;If this isn’t the case, you’ll get the error &lt;code&gt;Connection closed by server&lt;/code&gt;.&lt;/p&gt; &lt;p&gt;To avoid that, a trick is to call &lt;code&gt;check_health()&lt;/code&gt; regularly.&lt;/p&gt; &lt;p&gt;Here’s an example:&lt;/p&gt; &lt;pre class="language-python"&gt;&lt;code class="language-python"&gt;import redis import threading # Connection to Valkey r = redis.from_url( 'rediss://default:&amp;lt;password&amp;gt;@XXXXXX.stackhero-network.com:&amp;lt;port&amp;gt;', health_check_interval=10, socket_connect_timeout=5, retry_on_timeout=True, socket_keepalive=True ) # Create a PubSub instance p = r.pubsub() # Subscribe to the channel "test" p.subscribe('test') # Create a function that will call `check_health` every 5 seconds def redis_auto_check(p): t = threading.Timer(5, redis_auto_check, [ p ]) t.start() p.check_health() # Call the redis_auto_check function redis_auto_check(p) &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="configure-valkey-on-php"&gt;Configure Valkey on PHP&lt;/h2&gt; &lt;p&gt;Retrieve the URL with &lt;code&gt;getenv('STACKHERO_VALKEY_URL_TLS')&lt;/code&gt; and pass it to your preferred Valkey client library.&lt;/p&gt; &lt;h2 id="configure-valkey-on-go"&gt;Configure Valkey on Go&lt;/h2&gt; &lt;p&gt;First install the &lt;a href="https://github.com/go-redis/redis"&gt;go-redis&lt;/a&gt; package:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ go get github.com/go-redis/redis/v8 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Then, import it in your code:&lt;/p&gt; &lt;pre class="language-go"&gt;&lt;code class="language-go"&gt;import "github.com/gomodule/redigo/redis" &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Finally, connect to the Valkey server using the &lt;code&gt;STACKHERO_VALKEY_URL_TLS&lt;/code&gt; variable:&lt;/p&gt; &lt;pre class="language-go"&gt;&lt;code class="language-go"&gt;opt, err := redis.ParseURL(os.Getenv("STACKHERO_VALKEY_URL_TLS")) if err != nil { panic(err) } rdb := redis.NewClient(opt) &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;For more information, see the official &lt;a href="https://github.com/go-redis/redis"&gt;go-redis repository&lt;/a&gt;&lt;/p&gt; &lt;h2 id="configure-valkey-on-node-js"&gt;Configure Valkey on Node.js&lt;/h2&gt; &lt;p&gt;We recommend using &lt;a href="https://github.com/luin/ioredis"&gt;ioredis&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Install the &lt;code&gt;ioredis&lt;/code&gt; package:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ npm install ioredis &lt;/code&gt;&lt;/pre&gt;&lt;pre class="language-javascript"&gt;&lt;code class="language-javascript"&gt;const Ioredis = require('ioredis'); (async () =&amp;gt; { const valkey = new Ioredis(process.env.STACKHERO_VALKEY_URL_TLS); // Set key "stackhero-example-key" to "abcd" await valkey.set('stackhero-example-key', 'abcd'); // Get key "stackhero-example-key" const value = await valkey.get('stackhero-example-key'); console.log(`Key "stackhero-example-key" has value "${value}"`); // Finally delete key "stackhero-example-key" await valkey.del('stackhero-example-key'); })().catch(error =&amp;gt; { console.error('An error occurred!', error); }); &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;For more examples, see the official &lt;a href="https://github.com/luin/ioredis"&gt;ioredis repository&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="dashboard-and-web-ui-redis-commander"&gt;Dashboard and web UI (Redis Commander)&lt;/h2&gt; &lt;p&gt;Stackhero dashboard allows you to see your instance usage, restart it, and apply updates. It also gives you the ability to access the web UI to consult your Valkey data directly in a graphical way.&lt;/p&gt; &lt;p&gt;You can access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:open ah-valkey-stackhero Opening ah-valkey-stackhero for sharp-mountain-4005 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can also visit the &lt;a href="https://dashboard.heroku.com/apps"&gt;Heroku Dashboard&lt;/a&gt; and select the application in question. Then, select &lt;strong&gt;&lt;code&gt;Stackhero for Valkey&lt;/code&gt;&lt;/strong&gt; from the &lt;strong&gt;&lt;code&gt;Add-ons&lt;/code&gt;&lt;/strong&gt; menu.&lt;/p&gt; &lt;p&gt;&lt;img src="https://devcenter2.assets.heroku.com/article-images/1638789839-redisDashboard.png" alt="Stackhero dashboard for Valkey"&gt;&lt;/p&gt; &lt;h2 id="set-eviction-policy"&gt;Set eviction policy&lt;/h2&gt; &lt;p&gt;Yon can define how Valkey will react when you consume more memory than available on your plan.&lt;/p&gt; &lt;p&gt;To do so, &lt;a href="#dashboard-and-web-ui-redis-commander"&gt;connect to your Stackhero dashboard&lt;/a&gt;, select your Valkey service, then click &lt;strong&gt;&lt;code&gt;Configure&lt;/code&gt;&lt;/strong&gt; and set the &lt;strong&gt;&lt;code&gt;Eviction policy&lt;/code&gt;&lt;/strong&gt; setting.&lt;/p&gt; &lt;p&gt;&lt;img src="https://devcenter0.assets.heroku.com/article-images/1638789837-redisConfiguration.png" alt="Configuration of Valkey on Stackhero"&gt;&lt;/p&gt; &lt;h2 id="upgrading-your-plan"&gt;Upgrading your plan&lt;/h2&gt; &lt;div class="warning"&gt; &lt;p&gt;You cannot downgrade an existing add-on.&lt;/p&gt; &lt;/div&gt; &lt;p class="devcenter-parser-special-block-separator" style="display:none"&gt;&amp;nbsp;&lt;/p&gt; &lt;div class="note"&gt; &lt;p&gt;Application owners must carefully manage the migration timing to ensure proper application function during the migration process.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;heroku addons:upgrade&lt;/code&gt; command to migrate to a new plan.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:upgrade ah-valkey-stackhero:newplan -----&amp;gt; Upgrading ah-valkey-stackhero:newplan to sharp-mountain-4005... done Your plan has been updated to: ah-valkey-stackhero:newplan &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the add-on&lt;/h2&gt; &lt;p&gt;You can remove Stackhero for Valkey via the CLI:&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;This will destroy all associated data and cannot be undone!&lt;/p&gt; &lt;/div&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:destroy ah-valkey-stackhero -----&amp;gt; Removing ah-valkey-stackhero from sharp-mountain-4005... done &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;You can submit support and runtime issues for Stackhero for Valkey via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;. For urgent issues, CC support@stackhero.io.&lt;/p&gt; &lt;h2 id="additional-resources"&gt;Additional resources&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Valkey/documentations"&gt;Valkey documentation by Stackhero&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.stackhero.io/en/services/Valkey/benefits"&gt;Valkey managed cloud&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8378</id> <published>2025-02-09T19:24:56Z</published> <updated>2025-02-14T17:52:50Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/nscriptiod"/> <title>Nscriptio Static IP</title> <content type="html">&lt;p&gt;&lt;a href="https://elements.heroku.com/addons/nscriptio"&gt;NScriptio&lt;/a&gt; is an add-on that provides Heroku applications the ability to proxy their app network output through HTTP/HTTPS proxy under a pair of fixed, static IP. NScriptio is language and framework agnostic.&lt;/p&gt; &lt;p&gt;NScriptio acts as a proxy for outbound traffic, tunneling your requests through a pair of balanced IP addresses. You can use given addresses anywhere you need a fixed IP: API providers, firewall configurations, etc.&lt;/p&gt; &lt;h2 id="provisioning-the-add-on"&gt;Provisioning the Add-on&lt;/h2&gt; &lt;p&gt;Add the Nscriptio add-on to a Heroku application via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:create nscriptiod --app your-app-name -- --cc=ca -----&amp;gt; Creating nscriptiod on ⬢ your-app-name... free Your add-on is being provisioned, will be available shortly nscriptiod-graceful-83372 is being created in the background. The app will restart when complete... Use heroku addons:info nscriptiod-graceful-83372 to check creation progress Use heroku addons:docs nscriptiod to view documentation &lt;/code&gt;&lt;/pre&gt; &lt;div class="callout"&gt; &lt;p&gt;If your heroku CLI version is below v9.0.0, use &lt;code&gt;heroku addons:create nscriptiod --app your-app-name --cc=ca&lt;/code&gt; syntax, above syntax is for version v9.0.0+, for details check &lt;a href="https://github.com/heroku/cli/releases/tag/v9.0.0"&gt;ChangeLog&lt;/a&gt;&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;cc&lt;/code&gt; option to specify a country you want your IPs to be in. If not provided, the default is &lt;code&gt;us&lt;/code&gt;. We provide IPs from following locations:&lt;/p&gt; &lt;table&gt;&lt;thead&gt; &lt;tr&gt; &lt;th&gt;Flag&lt;/th&gt; &lt;th&gt;Country Code&lt;/th&gt; &lt;th&gt;Full Name&lt;/th&gt; &lt;/tr&gt; &lt;/thead&gt;&lt;tbody&gt; &lt;tr&gt; &lt;td&gt;🇦🇺&lt;/td&gt; &lt;td&gt;au&lt;/td&gt; &lt;td&gt;Australia&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇨🇦&lt;/td&gt; &lt;td&gt;ca&lt;/td&gt; &lt;td&gt;Canada&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇩🇪&lt;/td&gt; &lt;td&gt;de&lt;/td&gt; &lt;td&gt;Germany&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇪🇸&lt;/td&gt; &lt;td&gt;es&lt;/td&gt; &lt;td&gt;Spain&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇫🇷&lt;/td&gt; &lt;td&gt;fr&lt;/td&gt; &lt;td&gt;France&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇬🇧&lt;/td&gt; &lt;td&gt;gb&lt;/td&gt; &lt;td&gt;United Kingdom&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇮🇹&lt;/td&gt; &lt;td&gt;it&lt;/td&gt; &lt;td&gt;Italy&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇸🇬&lt;/td&gt; &lt;td&gt;sg&lt;/td&gt; &lt;td&gt;Sinapore&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;🇺🇸&lt;/td&gt; &lt;td&gt;us&lt;/td&gt; &lt;td&gt;United States&lt;/td&gt; &lt;/tr&gt; &lt;/tbody&gt;&lt;/table&gt; &lt;p&gt;If you want more locations, just ask us at &lt;a href="mailto:support@nscriptio.com"&gt;support@nscriptio.com&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;After adding the add-on, the &lt;code&gt;NSCRIPTIOD_HTTP&lt;/code&gt;, &lt;code&gt;NSCRIPTIOD_HTTPS&lt;/code&gt; config vars are available in the app. You can retrieve them by using the &lt;code&gt;heroku config:get&lt;/code&gt; command:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku config:get --app your-app-name NSCRIPTIOD_HTTPS https://username:password@nscriptio.online:3128 &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="add-on-dashboard"&gt;Add-on Dashboard&lt;/h2&gt; &lt;p&gt;Access the dashboard via the CLI:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;heroku addon:open nscriptiod &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;or by visiting the &lt;a href="http://heroku.com/myapps"&gt;Heroku apps web interface&lt;/a&gt; and selection the application in question, then select NScriptio from the add-ons menu.&lt;/p&gt; &lt;h2 id="what-are-my-ips"&gt;What are my IPs?&lt;/h2&gt; &lt;p&gt;The add-on provides two static IP addresses with fallback capability. Traffic routes through your primary IP, but if it fails, it uses the fallback IP. Both IPs are listed on the add-on dashboard&lt;/p&gt; &lt;h2 id="local-setup"&gt;Local Setup&lt;/h2&gt; &lt;h3 id="environment-setup"&gt;Environment Setup&lt;/h3&gt; &lt;p&gt;To use NScriptio to proxy requests while developing locally, you can export&lt;code&gt;NSCRIPTIOD_*&lt;/code&gt; environment variables to a config file for use in other applications:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku config:get --app your-app-name NSCRIPTIOD_HTTPS -s &amp;gt;&amp;gt; .env $ heroku config:get --app your-app-name NSCRIPTIOD_HTTP -s &amp;gt;&amp;gt; .env &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can either use the &lt;code&gt;.env&lt;/code&gt; file within other application as an &lt;code&gt;ENV&lt;/code&gt; import, or use the Heroku Local command-line tool to configure, run and manage process types specified in your app’s &lt;a href="https://devcenter.heroku.com/articles/procfile"&gt;Procfile&lt;/a&gt;. Heroku Local reads configuration variables from a &lt;code&gt;.env&lt;/code&gt; file.&lt;/p&gt; &lt;div class="warning"&gt; &lt;p&gt;Don’t commit credentials and other sensitive configuration values to source control. In Git, exclude the &lt;code&gt;.env&lt;/code&gt; file with: &lt;code&gt;echo .env &amp;gt;&amp;gt; .gitignore&lt;/code&gt;.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;For more information, see the &lt;a href="https://devcenter.heroku.com/articles/heroku-local"&gt;Heroku Local&lt;/a&gt; article.&lt;/p&gt; &lt;h2 id="use-with-node-js"&gt;Use with Node.js&lt;/h2&gt; &lt;p&gt;You can use most &lt;code&gt;http&lt;/code&gt; libraries with HTTP proxy, but not all of them work with HTTPS. Here we give an example on how to get Axios to work via HTTPS proxy:&lt;/p&gt; &lt;pre class="language-javascript"&gt;&lt;code class="language-javascript"&gt;const axios = require('axios'); const proxyagent = require('https-proxy-agent'); const agent = new proxyagent.HttpsProxyAgent(process.env.NSCRIPTIOD_HTTPS); axios.get('https://ipinfo.io/ip', {proxy:false,httpsAgent:agent}).then(function(res){ console.log(res); }); &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="use-with-ruby"&gt;Use with Ruby&lt;/h2&gt; &lt;p&gt;&lt;code&gt;rest-client&lt;/code&gt; and &lt;code&gt;faraday&lt;/code&gt; doesn’t support SSL proxy, so you can only use it with a HTTP proxy. With &lt;code&gt;typhoeus&lt;/code&gt;, you can use both protocols. Here are the examples for those:&lt;/p&gt; &lt;h3 id="rest-client"&gt;rest-client&lt;/h3&gt; &lt;pre class="language-ruby"&gt;&lt;code class="language-ruby"&gt;require "rest-client" RestClient.proxy = ENV["NSCRIPTIOD_HTTP"] res = RestClient.get("https://ipinfo.io/ip") remoteIp = res.body puts "IP: #{remoteIp}" &lt;/code&gt;&lt;/pre&gt; &lt;h3 id="faraday"&gt;faraday&lt;/h3&gt; &lt;pre class="language-ruby"&gt;&lt;code class="language-ruby"&gt;require 'faraday' conn = Faraday.new(:url =&amp;gt; "https://ipinfo.io/ip", :proxy =&amp;gt; ENV["NSCRIPTIOD_HTTP"]) res = conn.get remoteIp = res.body puts "IP: #{remoteIp}" &lt;/code&gt;&lt;/pre&gt; &lt;h3 id="typhoeus"&gt;typhoeus&lt;/h3&gt; &lt;pre class="language-ruby"&gt;&lt;code class="language-ruby"&gt;require 'typhoeus' _, username, password, host, port = ENV["NSCRIPTIOD_HTTPS"].gsub(/(:|\/|@)/,' ').squeeze(' ').split res = Typhoeus.get( 'https://ipinfo.io/ip', proxy: "https://#{host}:#{port}", proxyuserpwd: "#{username}:#{password}" ) remoteIp = res.body puts "IP: #{remoteIp}" &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="use-with-java"&gt;Use with Java&lt;/h2&gt; &lt;p&gt;Most third-party network libraries support HTTP/HTTPS proxy. Here we use the native Java support by setting the proxy globally:&lt;/p&gt; &lt;pre class="language-java"&gt;&lt;code class="language-java"&gt;import java.net.*; import java.io.*; public class Test { public static void main(String []args) throws IOException { URL pUrl = new URL(System.getenv("NSCRIPTIOD_HTTPS")); String info = pUrl.getUserInfo(); int i = info.indexOf(':'); String user = info.substring(0, i); String password = info.substring(i + 1); System.setProperty("http.proxyHost", pUrl.getHost()); System.setProperty("http.proxyPort", Integer.toString(pUrl.getPort())); Authenticator.setDefault(new Authenticator() { protected PasswordAuthentication getPasswordAuthentication() { return new PasswordAuthentication(user, password.toCharArray()); } }); URL url = new URL("https://ipinfo.io/ip"); URLConnection conn = url.openConnection(); BufferedReader rd = new BufferedReader(new InputStreamReader(conn.getInputStream())); String remoteIp = rd.readLine(); System.out.println("IP:"+remoteIp); } } &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="use-with-python"&gt;Use with Python&lt;/h2&gt; &lt;pre class="language-python"&gt;&lt;code class="language-python"&gt;import os, requests r = requests.get('https://ipinfo.io/ip', proxies={ "http" : os.getenv('NSCRIPTIOD_HTTPS'), "https" : os.getenv('NSCRIPTIOD_HTTPS') }) remoteIp=r.text print('IP: '+remoteIp) &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can also set the proxy globally by using system &lt;code&gt;http_proxy&lt;/code&gt; ENV&lt;/p&gt; &lt;pre class="language-python"&gt;&lt;code class="language-python"&gt;os.environ['http_proxy'] = os.getenv('NSCRIPTIOD_HTTP') os.environ['https_proxy'] = os.getenv('NSCRIPTIOD_HTTP') r = requests.get('https://ipinfo.io/ip') remoteIp=r.text print('IP: '+remoteIp) &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="use-with-golang"&gt;Use with Golang&lt;/h2&gt; &lt;pre class="language-go"&gt;&lt;code class="language-go"&gt;package main import ( "net/url" "net/http" "os" "io/ioutil" ) func main () { proxyUrl, _ := url.Parse(os.Getenv("NSCRIPTIOD_HTTPS")) customClient := &amp;amp;http.Client{Transport: &amp;amp;http.Transport{Proxy: http.ProxyURL(proxyUrl)}} resp, err = customClient.Get("https://ipinfo.io/ip") if (err != nil) { println(err.Error()) return } defer resp.Body.Close() remoteIp, _ := ioutil.ReadAll(resp.Body) println("IP: "+string(remoteIp)) } &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="use-with-php"&gt;Use with PHP&lt;/h2&gt; &lt;pre class="language-php"&gt;&lt;code class="language-php"&gt;&amp;lt;?php $ch = curl_init("https://ipinfo.io/ip"); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_PROXY, getenv("NSCRIPTIOD_HTTPS")); $remoteIp = curl_exec($ch); print("IP: ".$remoteIp); curl_close($ch); ?&amp;gt; &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="migrating-between-plans"&gt;Migrating between Plans&lt;/h2&gt; &lt;div class="note"&gt; &lt;p&gt;Application owners can migrate at any time with no interruption to your service.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Use the &lt;code&gt;heroku addons:upgrade&lt;/code&gt; command to migrate to a new plan.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ heroku addons:upgrade nscriptiod:g50 -----&amp;gt; Upgrading nscriptiod:g50 to sharp-mountain-4005... done, v18 ($10/mo) Your plan has been updated to: nscriptiod:g50 &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="removing-the-add-on"&gt;Removing the add-on&lt;/h2&gt; &lt;p&gt;Remove the add-on via the CLI.&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;heroku addons:destroy nscriptiod -----&amp;gt; Removing nscriptiod from sharp-mountain-4005... done, v20 (free) &lt;/code&gt;&lt;/pre&gt; &lt;h2 id="support"&gt;Support&lt;/h2&gt; &lt;p&gt;Submit all NScriptio support tickets via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="faq"&gt;FAQ&lt;/h2&gt; &lt;h3 id="where-can-i-see-my-usage-data"&gt;Where can I see my usage data?&lt;/h3&gt; &lt;p&gt;On the add-on’s dashboard.&lt;/p&gt; &lt;h3 id="how-do-the-two-ips-work"&gt;How do the two IPs work?&lt;/h3&gt; &lt;p&gt;Your traffic routes to your primary IP, the first one listed. If a request gets refused by target server or proxy server, the backup IP is used.&lt;/p&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8782</id> <published>2025-01-13T15:22:46Z</published> <updated>2025-01-13T15:22:46Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/heroku-php-behavior"/> <title>PHP Behavior in Heroku</title> <content type="html">&lt;p&gt;The Heroku Platform uses the &lt;a href="https://devcenter.heroku.com/articles/php-support"&gt;PHP buildpack&lt;/a&gt; to handle deployed PHP applications. The following shows Heroku’s behavior towards PHP apps and how it recognizes, runs, and builds them.&lt;/p&gt; &lt;h2 id="auto-detection"&gt;Auto-Detection&lt;/h2&gt; &lt;p&gt;Heroku PHP support applies to applications that have a file named &lt;code&gt;composer.json&lt;/code&gt; in the root directory. Even if an application has no &lt;a href="http://getcomposer.org"&gt;Composer&lt;/a&gt; dependencies, it must include at least an &lt;strong&gt;empty&lt;/strong&gt; (&lt;code&gt;{}&lt;/code&gt;) &lt;code&gt;composer.json&lt;/code&gt; in order to be recognized as a PHP application.&lt;/p&gt; &lt;p&gt;When Heroku recognizes a PHP application, it responds accordingly during a push:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ git push heroku main -----&amp;gt; PHP app detected … &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;If &lt;code&gt;composer.json&lt;/code&gt; specifies dependencies of any kind in its &lt;code&gt;require&lt;/code&gt; section, the corresponding &lt;code&gt;composer.lock&lt;/code&gt; that gets generated by running &lt;code&gt;composer update&lt;/code&gt; must also be committed to the repository, or the push is rejected. This ensures that the dependencies Heroku installs are the same as in any other environment. For detailed instructions, check out the &lt;a href="https://devcenter.heroku.com/articles/deploying-php#manage-dependencies"&gt;“Manage Dependencies” section of the Deploying PHP guide&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="php-runtimes"&gt;PHP Runtimes&lt;/h2&gt; &lt;p&gt;Heroku allows you to run your application using the official &lt;a href="http://php.net"&gt;PHP&lt;/a&gt; runtime. To learn how to specify a PHP runtime, refer to the &lt;a href="https://devcenter.heroku.com/articles/specifying-a-php-runtime"&gt;corresponding Dev Center article&lt;/a&gt;.&lt;/p&gt; &lt;h3 id="runtime-settings"&gt;Runtime Settings&lt;/h3&gt; &lt;p&gt;All PHP runtimes use the respective release’s &lt;code&gt;php.ini-production&lt;/code&gt; file as their base &lt;a href="https://www.php.net/manual/en/configuration.file.php"&gt;&lt;code&gt;php.ini&lt;/code&gt; configuration&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Notwithstanding the above, the following INI directives are set to Heroku-specific values:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/datetime.configuration.php#ini.date.timezone"&gt;&lt;code&gt;date.timezone&lt;/code&gt;&lt;/a&gt; is set to &lt;code&gt;UTC&lt;/code&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/errorfunc.configuration.php#ini.error-reporting"&gt;&lt;code&gt;error_reporting&lt;/code&gt;&lt;/a&gt; is set to &lt;ul&gt; &lt;li&gt;&lt;code&gt;E_ALL &amp;amp; ~E_STRICT&lt;/code&gt; for PHP versions before 8.4&lt;/li&gt; &lt;li&gt;&lt;code&gt;E_ALL&lt;/code&gt; for PHP 8.4 or later&lt;/li&gt; &lt;/ul&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/ini.core.php#ini.expose-php"&gt;&lt;code&gt;expose_php&lt;/code&gt;&lt;/a&gt; is set to &lt;code&gt;Off&lt;/code&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/session.configuration.php#ini.session.sid-length"&gt;&lt;code&gt;session.sid_length&lt;/code&gt;&lt;/a&gt; is set to &lt;code&gt;32&lt;/code&gt; (for PHP versions 7.3 to 8.3)&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/ini.core.php#ini.short-open-tag"&gt;&lt;code&gt;short_open_tag&lt;/code&gt;&lt;/a&gt; is set to &lt;code&gt;On&lt;/code&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/ini.core.php#ini.user-ini.cache-ttl"&gt;&lt;code&gt;user_ini.cache_ttl&lt;/code&gt;&lt;/a&gt; is set to &lt;code&gt;86400&lt;/code&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://www.php.net/manual/en/ini.core.php#ini.variables-order"&gt;&lt;code&gt;variables_order&lt;/code&gt;&lt;/a&gt; is set to &lt;code&gt;EGPCS&lt;/code&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;In addition, the PHP runtimes always have &lt;a href="http://php.net/manual/book.opcache"&gt;OPcache&lt;/a&gt; enabled for improved performance, with the following configuration changes optimized for the specific characteristics of Heroku’s dynos:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;code&gt;opcache.enable_cli&lt;/code&gt; is set to &lt;code&gt;1&lt;/code&gt;&lt;/li&gt; &lt;li&gt;&lt;code&gt;opcache.validate_timestamps&lt;/code&gt; is set to &lt;code&gt;0&lt;/code&gt;&lt;/li&gt; &lt;/ul&gt; &lt;h4 id="php-cli"&gt;PHP CLI&lt;/h4&gt; &lt;p&gt;The &lt;code&gt;memory_limit&lt;/code&gt; PHP INI directive for the &lt;code&gt;php&lt;/code&gt; CLI executable defaults to the full available dyno memory. For example, worker dynos using a &lt;code&gt;php&lt;/code&gt; command use this memory limit instead of the default PHP INI value of &lt;code&gt;128M&lt;/code&gt;.&lt;/p&gt; &lt;h3 id="default-runtime"&gt;Default Runtime&lt;/h3&gt; &lt;p&gt;Applications that don’t use a &lt;code&gt;composer.json&lt;/code&gt;, or where &lt;code&gt;composer.lock&lt;/code&gt; contains no requirements for package &lt;code&gt;php&lt;/code&gt; even in any dependent package, will receive the latest version of PHP that is &lt;a href="https://devcenter.heroku.com/articles/php-support#available-versions"&gt;available&lt;/a&gt; on the app’s &lt;a href="https://devcenter.heroku.com/articles/stack"&gt;stack&lt;/a&gt;.&lt;/p&gt; &lt;h3 id="upgrades"&gt;Upgrades&lt;/h3&gt; &lt;p&gt;If you deploy an application that doesn’t declare a runtime version dependency, the then-latest version of PHP is used. Your application upgrades to more recent versions of PHP if available automatically upon the next deployment.&lt;/p&gt; &lt;p&gt;If your application declares runtime version dependencies, the most recent version matching the version constraint will be selected for installation.&lt;/p&gt; &lt;h3 id="runtime-behavior"&gt;Runtime Behavior&lt;/h3&gt; &lt;p&gt;The &lt;code&gt;$PATH&lt;/code&gt; environment variable contains all necessary paths for an application to function at runtime. The &lt;a href="https://getcomposer.org/doc/articles/vendor-binaries.md#can-vendor-binaries-be-installed-somewhere-other-than-vendor-bin-"&gt;Composer &lt;code&gt;bin-dir&lt;/code&gt;&lt;/a&gt; is appended to &lt;code&gt;$PATH&lt;/code&gt; for convenience.&lt;/p&gt; &lt;h4 id="php-fpm-configuration"&gt;PHP-FPM Configuration&lt;/h4&gt; &lt;p&gt;PHP-FPM is set up to automatically spawn a suitable number of worker processes depending on dyno size and the configured PHP &lt;code&gt;memory_limit&lt;/code&gt;. For more information, see &lt;a href="https://devcenter.heroku.com/articles/php-concurrency"&gt;Optimizing PHP Application Concurrency&lt;/a&gt;.&lt;/p&gt; &lt;h4 id="timeouts"&gt;Timeouts&lt;/h4&gt; &lt;p&gt;When a request &lt;a href="https://devcenter.heroku.com/articles/request-timeout"&gt;reaches the Heroku router’s request timeout&lt;/a&gt;, a PHP-FPM process continues to run, potentially as long as it takes for example an external timeout to occur. This would tie up that PHP-FPM process, which could then no longer respond to other incoming requests.&lt;/p&gt; &lt;p&gt;For applications using PHP 7.4 or later, by default, PHP-FPM will therefore&lt;/p&gt; &lt;ul&gt; &lt;li&gt;log a backtrace of requests that take longer than three seconds (&lt;code&gt;request_slowlog_timeout&lt;/code&gt; directive), and&lt;/li&gt; &lt;li&gt;terminate requests that have exceeded an execution time of 30 seconds (&lt;code&gt;request_terminate_timeout&lt;/code&gt; directive) and therefore likely &lt;a href="https://devcenter.heroku.com/articles/request-timeout"&gt;timed out&lt;/a&gt;.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;You may &lt;a href="https://devcenter.heroku.com/articles/custom-php-settings#php-fpm-settings"&gt;adjust the settings for PHP-FPM&lt;/a&gt; to change these (or other) configuration settings.&lt;/p&gt; &lt;h4 id="composer-configuration"&gt;Composer Configuration&lt;/h4&gt; &lt;p&gt;For convenience, the following settings for Composer are automatically set using environment variables:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;code&gt;$COMPOSER_MEMORY_LIMIT&lt;/code&gt; defaults to the available dyno memory;&lt;/li&gt; &lt;li&gt;&lt;code&gt;$COMPOSER_MIRROR_PATH_REPOS&lt;/code&gt; defaults to &lt;code&gt;1&lt;/code&gt;;&lt;/li&gt; &lt;li&gt;&lt;code&gt;$COMPOSER_NO_INTERACTION&lt;/code&gt; defaults to &lt;code&gt;1&lt;/code&gt;;&lt;/li&gt; &lt;li&gt;&lt;code&gt;$COMPOSER_PROCESS_TIMEOUT&lt;/code&gt; defaults to &lt;code&gt;0&lt;/code&gt;.&lt;/li&gt; &lt;/ul&gt; &lt;h2 id="customizing-settings"&gt;Customizing Settings&lt;/h2&gt; &lt;h3 id="php"&gt;PHP&lt;/h3&gt; &lt;p&gt;Any &lt;code&gt;.user.ini&lt;/code&gt; file that’s placed into a project &lt;a href="http://php.net/manual/en/configuration.file.per-user.php"&gt;according to the instructions in the PHP manual&lt;/a&gt; loads after the main &lt;code&gt;php.ini&lt;/code&gt;. You can use these to set any directive permitted in &lt;code&gt;PHP_INI_ALL&lt;/code&gt;, &lt;code&gt;PHP_INI_USER&lt;/code&gt; and &lt;code&gt;PHP_INI_PERDIR&lt;/code&gt; contexts.&lt;/p&gt; &lt;p&gt;For additional details on this and other ways of customizing settings for the PHP runtime, refer to the &lt;a href="https://devcenter.heroku.com/articles/custom-php-settings"&gt;corresponding Dev Center article&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="build-behavior"&gt;Build Behavior&lt;/h2&gt; &lt;h3 id="installation-of-dependencies"&gt;Installation of Dependencies&lt;/h3&gt; &lt;p&gt;The following command is run during a deploy to resolve dependencies unless &lt;code&gt;composer.json&lt;/code&gt; is empty and no &lt;code&gt;composer.lock&lt;/code&gt; is present:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ composer install --no-dev --prefer-dist --optimize-autoloader --no-interaction &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;Heroku won’t install development dependencies from the &lt;code&gt;require-dev&lt;/code&gt; section of &lt;code&gt;composer.json&lt;/code&gt;. However, if the &lt;code&gt;require-dev&lt;/code&gt; section contains a PHP runtime version requirement or lists a dependency that contains such a requirement, then the &lt;code&gt;require&lt;/code&gt; section of &lt;code&gt;composer.json&lt;/code&gt; must also contain a PHP runtime version requirement or list a dependency that contains such a requirement. This is to ensure that Heroku doesn’t select a default PHP runtime version that conflicts with what other environments (which include &lt;code&gt;require-dev&lt;/code&gt; dependencies) install.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;The installed &lt;a href="https://devcenter.heroku.com/articles/php-support#available-composer-versions"&gt;version of Composer&lt;/a&gt; will be printed for your reference before installation begins. Builds are run using the latest possible Composer version (1.x, 2.2.x LTS, or 2.3+) that’s compatible with an application’s &lt;code&gt;composer.lock&lt;/code&gt;. The respective version of Composer is available on &lt;code&gt;$PATH&lt;/code&gt; at app runtime under the command name &lt;code&gt;composer&lt;/code&gt;.&lt;/p&gt; &lt;p&gt;An application’s Composer cache directory is persisted between builds to speed up package installation on subsequent deploys.&lt;/p&gt; &lt;h3 id="custom-compile-step"&gt;Custom Compile Step&lt;/h3&gt; &lt;p&gt;For applications that wish to execute an additional compilation step during a build that shouldn’t be part of a standard &lt;a href="https://getcomposer.org/doc/articles/scripts.md#event-names"&gt;&lt;code&gt;post-install-cmd&lt;/code&gt; Composer script&lt;/a&gt;, for example an asset compilation or cache pre-warming procedure, a &lt;code&gt;compile&lt;/code&gt; &lt;a href="https://getcomposer.org/doc/articles/scripts.md#writing-custom-commands"&gt;custom command&lt;/a&gt;, if present in &lt;code&gt;composer.json&lt;/code&gt;, executes using the following command:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ composer compile --no-dev --no-interaction &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Any such custom script command defined in composer.json can &lt;a href="https://getcomposer.org/doc/articles/scripts.md#defining-scripts"&gt;either be a single string, or an array of multiple commands to execute&lt;/a&gt;; example:&lt;/p&gt; &lt;pre class="language-json"&gt;&lt;code class="language-json"&gt;{ "scripts": { "compile": [ "@php app/console assetic:dump --env=prod --no-debug", "MyVendor\\MyClass::postDeployComposerCallback" ] } } &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;If you must execute &lt;code&gt;php&lt;/code&gt; or &lt;code&gt;composer&lt;/code&gt; in any Composer script, always reference the executables using the &lt;a href="https://getcomposer.org/doc/articles/scripts.md#executing-php-scripts"&gt;&lt;code&gt;@php&lt;/code&gt;&lt;/a&gt; or &lt;a href="https://getcomposer.org/doc/articles/scripts.md#calling-composer-commands"&gt;&lt;code&gt;@composer&lt;/code&gt;&lt;/a&gt; shorthand notations. This will always call the correct PHP or Composer executable in any environment, and also ensure any &lt;a href="#composer-configuration"&gt;Composer configuration&lt;/a&gt;, including the right PHP &lt;code&gt;memory_limit&lt;/code&gt;, is applied.&lt;/p&gt; &lt;/div&gt; &lt;p class="devcenter-parser-special-block-separator" style="display:none"&gt;&amp;nbsp;&lt;/p&gt; &lt;div class="note"&gt; &lt;p&gt;Composer’s &lt;code&gt;bin-dir&lt;/code&gt; is &lt;a href="https://getcomposer.org/doc/articles/scripts.md#writing-custom-commands"&gt;pushed on top of &lt;code&gt;$PATH&lt;/code&gt; during command execution&lt;/a&gt;, making binaries installed by dependencies easily accessible as CLI commands when writing scripts without having to use &lt;code&gt;vendor/bin/&lt;/code&gt; or a similar prefix.&lt;/p&gt; &lt;/div&gt; &lt;h3 id="private-repositories"&gt;Private Repositories&lt;/h3&gt; &lt;p&gt;To use private repositories like &lt;a href="https://packagist.com/"&gt;Private Packagist&lt;/a&gt;, or packages from a source that requires authentication (such as a private GitHub repository), Composer must be provided with authentication details (typically a token generated by the provider or service).&lt;/p&gt; &lt;p&gt;On a development machine, these are typically stored by Composer in &lt;a href="https://getcomposer.org/doc/articles/handling-private-packages-with-satis.md#authentication"&gt;&lt;code&gt;auth.json&lt;/code&gt;&lt;/a&gt;, but on Heroku, such &lt;a href="https://devcenter.heroku.com/articles/config-vars"&gt;secrets are stored as environment variables&lt;/a&gt;. The &lt;a href="https://getcomposer.org/doc/03-cli.md#composer-auth"&gt;&lt;code&gt;COMPOSER_AUTH&lt;/code&gt; environment variable is automatically read by Composer&lt;/a&gt;; its JSON structure is identical to &lt;code&gt;auth.json&lt;/code&gt;.&lt;/p&gt; &lt;p&gt;The following entries are allowed as top-level keys in the JSON document:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://getcomposer.org/doc/06-config.md#http-basic"&gt;&lt;code&gt;http-basic&lt;/code&gt;&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://getcomposer.org/doc/06-config.md#github-oauth"&gt;&lt;code&gt;github-oauth&lt;/code&gt;&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://getcomposer.org/doc/06-config.md#gitlab-oauth"&gt;&lt;code&gt;gitlab-oauth&lt;/code&gt;&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://getcomposer.org/doc/06-config.md#gitlab-token"&gt;&lt;code&gt;gitlab-token&lt;/code&gt;&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://getcomposer.org/doc/06-config.md#bitbucket-oauth"&gt;&lt;code&gt;bitbucket-oauth&lt;/code&gt;&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;Each entry then contains a hash of domains as keys and authentication details as values; the authentication detail structure is specific to each of the sources above and described in the documentation.&lt;/p&gt; &lt;div class="note"&gt; &lt;p&gt;When using GitHub Enterprise or the Self-Managed version of GitLab, remember to also set the &lt;a href="https://getcomposer.org/doc/06-config.md#github-domains"&gt;&lt;code&gt;github-domains&lt;/code&gt;&lt;/a&gt; or &lt;a href="https://getcomposer.org/doc/06-config.md#gitlab-domains"&gt;&lt;code&gt;gitlab-domains&lt;/code&gt;&lt;/a&gt; config option inside your project’s &lt;code&gt;composer.json&lt;/code&gt;.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;For example, to store authentication details for a &lt;a href="https://packagist.com/"&gt;Private Packagist&lt;/a&gt;, account, set the &lt;code&gt;COMPOSER_AUTH&lt;/code&gt; variable using &lt;code&gt;heroku config:set&lt;/code&gt; with &lt;code&gt;http-basic&lt;/code&gt; details (replacing “YOURTOKEN” with the actual token Private Packagist generated):&lt;/p&gt; &lt;pre&gt;&lt;code&gt;$ heroku config:set COMPOSER_AUTH='{"http-basic":{"repo.packagist.com":{"username":"token","password":"YOURTOKEN"}}}' &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;To give another example, when using &lt;a href="https://getcomposer.org/doc/05-repositories.md#using-private-repositories"&gt;code from private GitHub repositories as Composer dependencies&lt;/a&gt;, a &lt;a href="https://github.com/blog/1509-personal-api-tokens"&gt;personal OAuth token&lt;/a&gt; can be set for authentication. After &lt;a href="https://github.com/settings/tokens/new"&gt;creating a new Token&lt;/a&gt;, you can set it on Heroku (replacing “YOURTOKEN” with the actual token GitHub generated):&lt;/p&gt; &lt;pre&gt;&lt;code&gt;$ heroku config:set COMPOSER_AUTH='{"github-oauth":{"github.com":"YOURTOKEN"}}' &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;The private repository URL in your &lt;code&gt;composer.json&lt;/code&gt; must use the &lt;code&gt;https://&lt;/code&gt; and not the &lt;code&gt;git://&lt;/code&gt; protocol for Composer to be able to use the OAuth token for authentication.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Several sets of authentication details can also be combined into a single document; for example, to use both private GitHub and private BitBucket repositories:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;$ heroku config:set COMPOSER_AUTH='{ "github-oauth": {"github.com": "YOURTOKEN"}, "bitbucket-oauth": {"bitbucket.org": { "consumer-key": "YOURKEY", "consumer-secret": "YOURSECRET"} } }' &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;You may use line breaks within quotes when setting environment variables on Heroku as shown in the example above, but you must ensure that the quoting is correct when running the &lt;code&gt;heroku config:set&lt;/code&gt; command.&lt;/p&gt; &lt;/div&gt; &lt;h2 id="customer-support"&gt;Customer Support&lt;/h2&gt; &lt;p&gt;You can submit issues via one of the &lt;a href="https://devcenter.heroku.com/articles/support-channels"&gt;Heroku Support channels&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="additional-reading"&gt;Additional Reading&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://devcenter.heroku.com/articles/php-support"&gt;Heroku PHP Support Reference&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://devcenter.heroku.com/articles/specifying-a-php-runtime"&gt;Specifying a PHP Runtime&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8786</id> <published>2025-01-03T20:53:25Z</published> <updated>2025-01-03T20:53:25Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/specifying-a-php-runtime"/> <title>Specifying a PHP Runtime</title> <content type="html">&lt;p&gt;You can specify which runtime(s) to use in your &lt;code&gt;composer.json&lt;/code&gt; file. Upon a push, Heroku reads the necessary information from &lt;code&gt;composer.lock&lt;/code&gt;, if present, and falls back to &lt;code&gt;composer.json&lt;/code&gt; otherwise.&lt;/p&gt; &lt;h2 id="specifying-a-runtime"&gt;Specifying a Runtime&lt;/h2&gt; &lt;p&gt;For example, here &lt;code&gt;composer.json&lt;/code&gt; instructs Heroku to use the latest version of PHP 8 greater or equal to 8.2.0, but not PHP 9:&lt;/p&gt; &lt;pre class="language-json"&gt;&lt;code class="language-json"&gt;{ "require": { "php": "^8.2.0" } } &lt;/code&gt;&lt;/pre&gt; &lt;div class="warning"&gt; &lt;p&gt;Never specify an exact version like “&lt;code&gt;8.2.13&lt;/code&gt;” for PHP, or any other package.&lt;/p&gt; &lt;p&gt;Instead, use &lt;a href="https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators"&gt;the “&lt;code&gt;^&lt;/code&gt;” or “&lt;code&gt;~&lt;/code&gt;” &lt;em&gt;next significant release&lt;/em&gt; operators&lt;/a&gt; to ensure that you get appropriate updates upon push as they become available.&lt;/p&gt; &lt;p&gt;For example, specifying “&lt;code&gt;~8.2.0&lt;/code&gt;” provides the latest 8.2.x release. This specification is fully compatible with other releases from the 8.2 series, but may contain security or performance updates. It is not compatible with PHP 8.3 or later.&lt;/p&gt; &lt;p&gt;To get the latest PHP 8.2 or later (including PHP 8.3, 8.4, and so on) but not PHP 9, specify “&lt;code&gt;^8.2.0&lt;/code&gt;”.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Heroku prints the versions that are resolved and installs:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;-----&amp;gt; Installing platform packages... - php (8.2.13) &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Specifying an unknown or unsupported version results in an error listing potential alternative versions.&lt;/p&gt; &lt;h3 id="php"&gt;PHP&lt;/h3&gt; &lt;p&gt;Specify “&lt;code&gt;php&lt;/code&gt;” as a dependency in the &lt;code&gt;require&lt;/code&gt; section of your &lt;code&gt;composer.json&lt;/code&gt; to use PHP as the runtime. For example, for PHP 8.1 or later:&lt;/p&gt; &lt;pre class="language-json"&gt;&lt;code class="language-json"&gt;{ "require": { "php": "^8.1.0" } } &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;It’s recommended you always prefix the minimum version you’d like to use with the &lt;code&gt;^&lt;/code&gt; selector. This ensures that you receive updated versions as they become available. In the example above, you get PHP 8.1.0 or later, including newer versions in the 8.x series. You won’t get PHP 9 (when it’s released) until you change your specification.&lt;/p&gt; &lt;/div&gt; &lt;p&gt;Next, ensure that your new requirements are “frozen” to &lt;code&gt;composer.lock&lt;/code&gt; by running:&lt;/p&gt; &lt;pre class="language-term"&gt;&lt;code class="language-term"&gt;$ composer update &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;Finally, don’t forget to &lt;code&gt;git add&lt;/code&gt; and &lt;code&gt;git commit&lt;/code&gt; both files!&lt;/p&gt; &lt;h2 id="additional-reading"&gt;Additional Reading&lt;/h2&gt; &lt;ul&gt; &lt;li&gt;&lt;a href="https://devcenter.heroku.com/articles/php-support#php-runtimes"&gt;Heroku PHP Support Reference&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href="https://devcenter.heroku.com/articles/php-behavior-in-heroku"&gt;PHP Behavior in Heroku&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt;</content> </entry> <entry> <id>tag:devcenter.heroku.com,2005:Article/8781</id> <published>2025-01-03T20:52:54Z</published> <updated>2025-01-03T20:52:54Z</updated> <link rel="alternate" type="text/html" href="https://devcenter.heroku.com/articles/managing-php-web-servers"/> <title>Managing PHP Web Servers</title> <content type="html">&lt;p&gt;Heroku supports &lt;strong&gt;&lt;a href="http://httpd.apache.org"&gt;Apache HTTPD&lt;/a&gt; 2.4&lt;/strong&gt; and &lt;strong&gt;&lt;a href="http://nginx.org"&gt;Nginx&lt;/a&gt;&lt;/strong&gt; as dedicated web servers. For testing purposes, users can also use PHP’s built-in web server, although it’s not recommended. To see available web server versions, see &lt;a href="https://devcenter.heroku.com/articles/php-support#available-web-servers"&gt;Heroku PHP Support Reference&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;In the absence of a &lt;code&gt;Procfile&lt;/code&gt; entry for the “web” dyno type, the Apache Web server will be used together with the PHP runtime.&lt;/p&gt; &lt;h2 id="apache"&gt;Apache&lt;/h2&gt; &lt;p&gt;Apache interfaces with PHP-FPM via FastCGI using &lt;code&gt;mod_proxy_fcgi&lt;/code&gt;.&lt;/p&gt; &lt;p&gt;To start Apache together with PHP-FPM and correct settings, use the &lt;code&gt;heroku-php-apache2&lt;/code&gt; script:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;web: heroku-php-apache2 &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;By default, the root folder of your project will be used as the &lt;a href="https://devcenter.heroku.com/articles/custom-php-settings#setting-the-document-root"&gt;document root&lt;/a&gt;. To use a subdirectory, you can pass the name of a subfolder as the argument to the boot script, for example “public_html”:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;web: heroku-php-apache2 public_html &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;You can use regular &lt;code&gt;.htaccess&lt;/code&gt; files to customize Apache’s behavior, for example for &lt;a href="http://httpd.apache.org/docs/2.4/rewrite/"&gt;URL rewriting&lt;/a&gt;. For additional details on this and other options to customize settings for Apache, refer to the &lt;a href="https://devcenter.heroku.com/articles/custom-php-settings"&gt;corresponding Dev Center article&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="nginx"&gt;Nginx&lt;/h2&gt; &lt;p&gt;Nginx interfaces with PHP-FPM via FastCGI.&lt;/p&gt; &lt;p&gt;To start Nginx together with PHP-FPM and correct settings, use the &lt;code&gt;heroku-php-nginx&lt;/code&gt; script:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;web: heroku-php-nginx &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;By default, the root folder of your project will be used as the &lt;a href="https://devcenter.heroku.com/articles/custom-php-settings#setting-the-document-root"&gt;document root&lt;/a&gt;. To use a subdirectory, you can pass the name of a subfolder as the argument to the boot script, for example “public_html”:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;web: heroku-php-nginx public_html &lt;/code&gt;&lt;/pre&gt; &lt;p&gt;For additional details on different ways of customizing settings for Nginx, refer to the &lt;a href="https://devcenter.heroku.com/articles/custom-php-settings"&gt;corresponding Dev Center article&lt;/a&gt;.&lt;/p&gt; &lt;h2 id="php-built-in-web-server"&gt;PHP Built-in Web server&lt;/h2&gt; &lt;p&gt;For testing purposes, you can start &lt;a href="http://php.net/manual/en/features.commandline.webserver.php"&gt;PHP’s built-in Web server&lt;/a&gt; by using &lt;code&gt;php -S 0.0.0.0:$PORT&lt;/code&gt; as the entry for “web” in your &lt;code&gt;Procfile&lt;/code&gt;:&lt;/p&gt; &lt;pre&gt;&lt;code&gt;web: php -S ‘0.0.0.0:$PORT &lt;/code&gt;&lt;/pre&gt; &lt;div class="note"&gt; &lt;p&gt;The &lt;code&gt;Procfile&lt;/code&gt; must contain &lt;code&gt;$PORT&lt;/code&gt; in the line shown above. It’s used by Heroku at runtime to dynamically bind the web server instance to the correct port for the dyno.&lt;/p&gt; &lt;/div&gt; &lt;p class="devcenter-parser-special-block-separator" style="display:none"&gt;&amp;nbsp;&lt;/p&gt; &lt;div class="note"&gt; &lt;p&gt;It’s important to bind to all interfaces using &lt;code&gt;0.0.0.0&lt;/code&gt;, otherwise Heroku’s &lt;a href="https://devcenter.heroku.com/articles/http-routing"&gt;routing&lt;/a&gt; won’t be able to forward requests to the web server!&lt;/p&gt; &lt;/div&gt; &lt;p&gt;You can also pass an alternative document root, or use a router script to process requests. For details, refer to the PHP project’s &lt;a href="https://www.php.net/manual/en/features.commandline.webserver.php"&gt;documentation for the built-in Web server&lt;/a&gt;.&lt;/p&gt;</content> </entry> </feed>