<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Redis for n8n]]></title><description><![CDATA[<p dir="auto">I installed another application on Cloudron and I saw that the application has Redis. Can I leverage that Redis for the queue in my n8n, or do I need to install Redis elsewhere? Thank you.</p>
]]></description><link>https://forum.cloudron.io/topic/13262/redis-for-n8n</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 14:15:26 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/13262.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 08 Feb 2025 09:37:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Redis for n8n on Tue, 21 Oct 2025 10:17:41 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/james" aria-label="Profile: james">@<bdi>james</bdi></a><br />
safe as in I want to avoid corruption<br />
this is way I pick database number 1 <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f609.png?v=13d69e59554" class="not-responsive emoji emoji-android emoji--wink" style="height:23px;width:auto;vertical-align:middle" title=";)" alt="😉" /></p>
<p dir="auto">because if; Redis is shared between all the container and attribute different database to each of them<br />
then if manually I use a database number (such as 1)<br />
I might shoot data and disrupt one of my services.</p>
<p dir="auto">PS: I don't really know Redis<br />
but I presume, as in any database, data integrity is important.</p>
]]></description><link>https://forum.cloudron.io/post/114171</link><guid isPermaLink="true">https://forum.cloudron.io/post/114171</guid><dc:creator><![CDATA[JOduMonT]]></dc:creator><pubDate>Tue, 21 Oct 2025 10:17:41 GMT</pubDate></item><item><title><![CDATA[Reply to Redis for n8n on Tue, 21 Oct 2025 08:49:16 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/jodumont" aria-label="Profile: JOduMonT">@<bdi>JOduMonT</bdi></a></p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jodumont" aria-label="Profile: JOduMonT">@<bdi>JOduMonT</bdi></a> said in <a href="/post/113973">Redis for n8n</a>:</p>
<blockquote>
<p dir="auto">is it safe the reuse that Redis for my has memory for my AI Agent (inside n8n) ?</p>
</blockquote>
<p dir="auto">Could you please elaborate what you mean by "safe" so I can give a more precise response?<br />
In general, yes you can use the Redis service of your app for your app with no issues.</p>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jodumont" aria-label="Profile: JOduMonT">@<bdi>JOduMonT</bdi></a> said in <a href="/post/113973">Redis for n8n</a>:</p>
<blockquote>
<p dir="auto">is this Redis isolated and dedicated to n8n instance ?</p>
</blockquote>
<p dir="auto">Yes, if an app comes with a Redis service, this Redis service is available to this app.<br />
By default, only the app that creates its own Redis service uses this Redis service.</p>
<p dir="auto">But to be very precise, it is not fully isolated to this app only.<br />
Meaning?<br />
As an example, you have the N8N app and the LAMP app.<br />
Both have a Redis service.<br />
If you get the credentials of the LAMP Redis service, you could connect from the N8N app to the LAMP Redis service.<br />
Same with other services like PostgreSQL, MYSQL and so on.</p>
<p dir="auto">That can be very useful, since you could connect to the other services in N8N.<br />
I have a LAMP app with my custom Webpage and Database and can connect to this Database with the N8N app to do some automation.</p>
<p dir="auto">If you have more questions, feel free to ask away.</p>
]]></description><link>https://forum.cloudron.io/post/114161</link><guid isPermaLink="true">https://forum.cloudron.io/post/114161</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Tue, 21 Oct 2025 08:49:16 GMT</pubDate></item><item><title><![CDATA[Reply to Redis for n8n on Fri, 17 Oct 2025 12:51:56 GMT]]></title><description><![CDATA[<p dir="auto">hi;</p>
<blockquote>
<p dir="auto">I know it's not the same question but the title remain appropriate.</p>
</blockquote>
<p dir="auto">I just deployed the n8n 1.115.3 via the Package Version io.n8n.cloudronapp@3.105.1<br />
and I noticed that Redis is available <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=13d69e59554" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<h4>my questions are;</h4>
<ol>
<li>is it safe the reuse that Redis for my has memory for my AI Agent (inside n8n) ?</li>
<li>is this Redis isolated and dedicated to n8n instance ?</li>
</ol>
<ul>
<li>BTW: I used "Database Number": 1.</li>
</ul>
]]></description><link>https://forum.cloudron.io/post/113973</link><guid isPermaLink="true">https://forum.cloudron.io/post/113973</guid><dc:creator><![CDATA[JOduMonT]]></dc:creator><pubDate>Fri, 17 Oct 2025 12:51:56 GMT</pubDate></item><item><title><![CDATA[Reply to Redis for n8n on Sun, 09 Feb 2025 10:03:39 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/zonzonzon" aria-label="Profile: zonzonzon">@<bdi>zonzonzon</bdi></a> are you rferring to <a href="https://docs.n8n.io/hosting/scaling/queue-mode/#start-redis" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.n8n.io/hosting/scaling/queue-mode/#start-redis</a> ? I have to say such a setup might be an overkill for Cloudron. (as in , having multiple workers + horizontal scaling) . The package is designed for a single node deployment.</p>
]]></description><link>https://forum.cloudron.io/post/101464</link><guid isPermaLink="true">https://forum.cloudron.io/post/101464</guid><dc:creator><![CDATA[joseph]]></dc:creator><pubDate>Sun, 09 Feb 2025 10:03:39 GMT</pubDate></item></channel></rss>