Answers to: Where does Axon.ivy Engine 8 store deployed files?

Comment by Alex Suter on Alex Suter's answer

Alex Suter — Fri, 19 Jun 2020 02:10:28 -0400

Yes, we may should improve our docs.

Comment by vinh_ on Alex Suter's answer

vinh_ — Fri, 19 Jun 2020 02:09:47 -0400

Thanks Alex, these information is useful, I wonder if it could appear in the Administration > Deployment section, that section didn't mention about deployment on Container Environment.

Comment by Alex Suter on Alex Suter's answer

Alex Suter — Fri, 19 Jun 2020 02:00:59 -0400

There is a really special handling about the deploy directory on Axon.ivy Engine startup. It behaves slightly different when deploying while start up out of the deploy directory. We calculate a hash out of the file to deploy, if its the same as before we won't deploy state into the database, we only copy the file to the right place (applications directory). This is especially designed for container environments. The long-term solution is, that we remove all state out of the database - but a long way to go ...

Comment by vinh_ on Alex Suter's answer

vinh_ — Fri, 19 Jun 2020 01:56:14 -0400

I'm aware of the state in System Database, which already stored. That's why I afraid of the deployed files state mismatch with the System Database.

I'm interested in the deploy directory. Is there any issue when it always deploy on start-up? How about existing Tasks, Cases, PMVs, modified global variables and other configurations?

Answer by Alex Suter

Alex Suter — Fri, 19 Jun 2020 01:48:33 -0400

It depends on how you want to use the Axon.ivy Docker Image.

If your application with the ivy projects are part of your Docker image then you only need to put them in the deploy directoy. They will be deployed on start up even if they are deployed - you don't have to care about anything.

But you are free to mount the application directory (/usr/lib/axonivy-engine-8/applications) into a persistent volume. Then you also could deploy for example over the REST-API without building a new image and starting a new container with your new application version.

Keep in mind that there is also state about deployment in the system database.