<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Answers to: Docker, applications folder, deployment</title><link>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment</link><description>&lt;p&gt;Dear Ivy team&lt;/p&gt;
&lt;p&gt;When we are building the KLARA image in windows, we get an issue with long file names. We have decided to keep the deployed IARs inside the image. Therefore the deployed apps are part of it. The folder structure looks like this :&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;jam:~/.../applications/luz$ ls -ltr
total 80
drwxr-xr-x 3 jam jam 4096 Mai  1  2019 luz_components
drwxr-xr-x 3 jam jam 4096 Mai  1  2019 luz_docs_process
drwxr-xr-x 3 jam jam 4096 Mai  1  2019 luz_finance
drwxr-xr-x 3 jam jam 4096 Mai  1  2019 luz_xhrm_processes
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and each folder contains all the Ivy stuff. So no wonder build under Windows is an issue due to long file names.&lt;/p&gt;
&lt;p&gt;Question : What is needed in these folders ? can we skip some folders/files ?&lt;/p&gt;
&lt;p&gt;Request for 7.3.2 : Can you provide a "applications"-less Ivy version which does not require 7.4 ? &lt;/p&gt;
&lt;p&gt;Best regards
John Moser&lt;/p&gt;</description><atom:link href="https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 08 Nov 2019 05:34:16 -0500</lastBuildDate><item><title>Answer by andreas_balsiger</title><link>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment/4159</link><description>&lt;p&gt;Hello John&lt;/p&gt;
&lt;p&gt;Thank you for being so active in our community support channel. We appreciate that very much and are always there happy to help you. As Head of Product Management, I am very much interested in meeting all customer needs. &lt;/p&gt;
&lt;p&gt;Our core developers have already been able to help and support you with your technical concerns. Therefore I would like to take the opportunity to explain our support strategy in detail. This strategy was introduced about 3 years ago at the request of a large number of customers. So it is known to all customers and has proven itself accordingly.&lt;/p&gt;
&lt;p&gt;We distinguish between so-called "Long Term Support / LTS" versions, which appear every 18-24 months. During this period there are smaller updates for the LTS version, so called service releases (bugfixes). Our existing customers mostly use this version in order to be able to work on the system in the long term without major changes. Our support covers the latest LTS and one older. (October 2019: 6.0.x, 7.0.x ==&amp;gt; Version 8.0 will be released in mid November!. The naming is as follows: 6.0.x, 7.0.x, 8.0.x etc.&lt;/p&gt;
&lt;p&gt;At the same time there is the possibility to use so-called "Leading Edge / LE" versions. These are released every 3-6 months and already contain new features in contrast to LTS versions. In case of support only the latest LE version is covered (November 2019: Version 7.4). The naming is as follows: 7.3, 7.4, 8.1 etc,&lt;/p&gt;
&lt;p&gt;In order to satisfy all customers, we are not able to support the outdated LE version 7.3. I hope you understand this from the explanations and don't feel like we're forgetting our customers.&lt;/p&gt;
&lt;p&gt;I hope I was able to show you what our proven support and release strategy looks like.&lt;/p&gt;
&lt;p&gt;As a long-time and very close customer we also recommend to place inquiries in our support channel support@axonivy.com .&lt;/p&gt;
&lt;p&gt;Best regards,
Andreas&lt;/p&gt;
&lt;p&gt;btw, the release strategy is public here: &lt;a href="http://developer.axonivy.com/download#product-editions"&gt;http://developer.axonivy.com/download#product-editions&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">andreas_balsiger</dc:creator><pubDate>Fri, 08 Nov 2019 05:34:16 -0500</pubDate><guid>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment/4159</guid></item><item><title>Comment by Alex Suter on John Moser's answer</title><link>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment#4157</link><description>&lt;p&gt;There is a suitable workaround for the 7.3 line by mounting the application directory to a persistent storage.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Suter</dc:creator><pubDate>Fri, 08 Nov 2019 04:11:15 -0500</pubDate><guid>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment#4157</guid></item><item><title>Answer by Alex Suter</title><link>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment/4155</link><description>&lt;p&gt;I assume you are talking about the &lt;code&gt;applications&lt;/code&gt; directory of ivy and &lt;code&gt;luz_components&lt;/code&gt;, &lt;code&gt;luz_docs_process&lt;/code&gt;, &lt;code&gt;luz_finance&lt;/code&gt; and &lt;code&gt;luz_xhrm_processes&lt;/code&gt; are process models. Everything is needed in those folders.&lt;/p&gt;
&lt;p&gt;We won't provide a 7.3.2. On our leading edge train there is in fact no further support for older LEs, especially no new features. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Suter</dc:creator><pubDate>Fri, 08 Nov 2019 02:58:02 -0500</pubDate><guid>https://answers.axonivy.com/questions/4154/docker-applications-folder-deployment/4155</guid></item></channel></rss>