Managed deployments are uploaded to the server. In case of unmanaged deployments there is only a 'link' to the original file.
But I would handle that with care in production.
See the helptext of the cli command deploy
--unmanaged if this argument is not specified, the deployment content
will be copied (i.e. uploaded) to the server's deployment
repository before it is deployed. If the argument is
present, the deployment content will remain at and be
deployed directly from its original location specified with
NOTE: exploded deployments are supported only as unmanaged.
Hi Wolf-Dieter Fink ,
Just for curious, If I have deployed with unmanaged argument. Can I able to check the deployed application ? If yes, How long I could check the deployed application ? ( Is there any constraints ?)
I don't understand what you are asking for, could you elaborate on this?
I would like to ask about the update process for unmanaged deployments. If we explode the new archive in the path indicated for the unmanaged deployment and, then, restart de Server Group, it would automatically gets the new version? Or we need to remove the old deployment and make a new one?
I don't understand your question
If you have a server-group, that mean you use the domain mode, here you don't have unmanaged deployments or exploded deployment.
Also as this is an old thread you should open a new discussion as your question is not related to the original issue.