View Full Version : The app doesnīt change with a new deploy

2021-10-20, 12:28
When I deploy again the new changes do not appear in my server, even if I delete the app and deploy it again, also if we erase the cache with ctrl+F5. Can someone tell me if Im missing an extra step from the deploy? or what do I have to do to have the new version of my app with the new changes?

2021-10-20, 13:28
Hi Karla,

How are you running the app in the browser? Is it from the app center or are you just specifying a url?

The version number in the app attributes should be updated before you deploy. In the app center this is added onto the url to force load a new version.

2021-10-20, 14:28
Thank you for your reply, we run the app by specifying a URL, when we deploy the app again itīs still the same version in the app attributes, so we try by deleting the app at all, and its the same, the new changes do not appear

2021-10-20, 20:51
If you are specifying the url in the browser address bar then the browser will be caching the previous version.

You need to make the url unique during testing by postfixing something like ?_version=xxx.yyy

Thats what app center tiles do.

2021-10-21, 01:51
Hi Karla,

See this article.

2021-10-21, 21:40
Good evening, the issue is not in the local host, is in the app center of my server, we visualice our apps by introducing the IP of our server in the browser, then it directs us to the app center and the changes do not appear, even if we delete it from the admin console in the lianja cloud admin

2021-10-21, 22:25
Hi Karla,

That sounds like a permissions problem on the server.

Can you upload one of the examples and access it?

Is that cloud server accessible to me? If it is submit a ticket with the information and I will investigate for you.

2021-10-21, 23:27
Sure, Iīll be honored, thank you so much, Iīll submit the ticket right away.

2021-10-22, 00:11
Hi Karla,

Check the version number in the App attributes "App Center Tile".

When you click the tile to load the app you should see the version number in the URL in the browser address bar.



That 1.0 corresponds to the version of your App.

Make sure you "Preview live in browser" also.

One other thing...

It may be that the package you are uploading is cached. Make sure you add a version number to that also.

2021-10-25, 13:20
Iīm sorry for the delay, I was having problems with my server, I fixed them so that you can access as you asked me, thank you so much for your help, Iīve already submit the ticket with the information of the server. By the way, I didnīt understand the version of the apps, Iīm confused because is not a local deployment.

2021-10-26, 00:11
Hi Carla,

When you create a package to upload using the Lianja Admin Console you should update the version of the package in the deploy workspace. This will create a new package and not overwrite the previous one you created. You can then rollback to earlier versions of you need to.


I always update my app version also if i'm going to update a remote server.


After the package is uploaded, it will be placed in the cloudserver/tenants/public/wwwroot/packages directory on your linux server.

If you look in that directory you will see all the packages that you have uploaded and an associated installation log.

Here is mine on windows.


The log file for a package contains installation info.


2021-10-27, 12:38
Iīm confused, according to the documentation
there are two ways to deploy an app, we do it by creating a proyect and including the apps, database and the files or scripts we created. Then we introduce the server information on the sftp protocol, and itīs working, but we are curious to learn this method. This is uploaded as packages directly on the Lianja Admin Console?

2021-10-27, 22:20
Yes you can create a package and upload it directly from the Lianja Admin Console. This uses http/https so no sftp is required on the server.

The package will automatically install if the environment variable DB_WWWAUTOUPDATE=ON is set.

Alternatively you can "Install" from the Lianja Admin Console.

When a package is installed the cloud server prevents any requests being served until the package installation has completed.

If the package contains upgrade.prg or setup.prg then database schema updates can be donw inside that file.

The installation of the package is done without affecting the system operation.