The app doesn´t change with a new deploy

[barrymavin]

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.

https://watch.screencastify.com/v/DQrFmZ7LrPlzYynpmUYr

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.

[karlaesponda01]

I´m confused, according to the documentation
https://www.lianja.com/doc/index.php...nt_with_Lianja
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?

[barrymavin]

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.