Skip to content

App details

App details page

On the left, you can choose which section you want to display.

Details

The Details section will show more information from the currently selected version of the app.

  • The description;
  • The author of the app;
  • The owner who uploaded the app first;
  • If the user seeing the page have permission to edit the app:
  • The internal ID of the app;
  • The type of the app (PGM / Shiny / Dash);
  • The R and/or Python versions used for the app;
  • If a virtual environment has been detected and its status;
  • The currently running instances of the app. If any, a button will open a section showing more details on the instances.

After the details, some buttons will show:

  • Start will start a personal instance;
  • Permissions will open the permission form;
  • Download will download the .pgm or .zip file of the app;
  • Install/update environment will install or update the app environment;
  • Update allow to select a file for creating a new version of the app;
  • Delete will delete the app and all its versions, links, cron jobs and files.

Read-only users will only see the Start button.

Changelog

The changelog section will show the changelog table as written in the ppro of the app for PGM apps.

Versions

Note

This section is only visible to developers with full access to the app.

Each app can have multiple versions. This allow developers to upload and test a new update of an app they made before setting it to "live". More precisely, everytime a user clicks on the Update button in the details page, this will create a new version of the app that will be listed in the Versions section.

App versions list

For each version you can see if it's the current selected version (green checkmark), the languages versions, the status of the virtual environment, the upload date and the user that uploaded this version.

The Actions button offer several options:

  • Set as default to set this version as the selected one for users;
  • Run app to run this specific version;
  • Settings for this version settings;
  • Download files to download the .pgm or .zip file of the version;
  • Delete to delete the version and all its related files.

Version settings

An app version have several settings:

App versions settings

Here you can override:

  • The app name;
  • The app version;
  • The app author;
  • The app description.

You can also add/update the app icon, select the R and Python version that will be use for tha app, and the persistent mode.

The links sections will list all the links for the app. See the Links guide page.

App links

Cron jobs

This section will list all the cron jobs for the app. See the Cron jobs page.

Cron jobs

Settings

In this section you can edit various settings about the app. Currently, it's mainly resources-oriented parameters.

App settings

The first settings control if an app can start by limiting its total possible instances, instances per IP and instances per user. For these settings, the global limits set in the administration panel still apply. Leaving a setting empty or setting it to 0 will be set to unlimited, but global settings still applies. If a single limit is excedeed, the instance will not start.

Example

Here is an example:

  • Global max total instances set to 10.
  • Global max total instances per IP set to 5.
  • App total instances set to 7.
  • App total instances per IP set to 10.

Every IP will be limited to 5 instances, with a maximum of 7 instances of this app across all users and IPs. Moreover, the server will never run more than 10 total instances. The App total instances per IP set to 10 has no effect because it is higher than the global setting set to 5.

The other ressources options are for aborting the app if it exceed some limit of RAM, CPU, CPU time or total execution time. This settings completely override the global settings.

Example

Here is an example:

  • Global Max total RAM for each app set to 200 Mo.
  • App Max RAM per instance set to 500 Mo.

This app will have a limit set to 500 Mo.

If Close on Disconnect is activated, it will abort the instances of this app as soon as the user quits the page of the instance. This is useful for dashboard-like apps.

Finally, Allow personal instances allow user to launch personal instances. This is useful when creating app that will be only executed through links. This setting should then be disable to prevent the user to create personal instance and hide it from the launchable apps in the listing.