Applications

An Application is a digital service or product hosted and distributed via WakaStart. It is attached to a Partner and can be deployed for several Networks and Customers.

When do you use this section?

• You want to register a new application on the platform
• You want to check the deployment status of an application
• You need to configure the settings of an existing application
• You want to manage the legal documents associated with a commercial application

Accessing the application list

From the main menu on the left, click Applications.

The list shows, for each application: its name, its type (Application, Module, or Service), the owning partner, and its deployment status (Not deployed, In progress, Deployed, In error, Stopped). The View URLs button gives access to the application's actual front-end address for each environment (see below).

Creating an application

1. Click + New application at the top right.
2. Fill in the information:
   • Owning partner: the partner to whom this application belongs
   • Name: the application's name (required)
   • Description: short presentation (250 characters max)
   • API address: the URL of the back-end services
   • HDS certification: check if the application handles health data
   • ISO 27001 certification: check if the application meets ISO 27001 requirements
   • Commercial application: check if the application is subject to terms of use — this will trigger the automatic creation of legal documents
3. Click Create.

Deleting an application

Click the trash icon. To confirm, you'll need to enter the application's exact name. This operation is irreversible.

Managing legal documents

When an application is marked as commercial, you can write and manage its legal documents (terms of use, privacy policy, etc.) through the built-in document editor.

The editor offers rich formatting (headings, lists, links, tables). You can import an existing Word or Markdown file, and export your document as Word, Markdown, or PDF.

Managing an application's infrastructure

Click the rocket icon next to an application to access its infrastructure view. There you'll find:

• Architecture: the associated services, repositories, dependencies, and addresses
• Builds: the build history and the option to trigger a new build. You'll also find:
  • the Registre (registry) card: the space used by the application's images, and its quota if there is one. When the quota is reached, new builds are refused;
  • the Purge automatique des builds (automatic build purge) card: the purge of old builds is disabled by default. Once enabled, it deletes the images of the oldest builds every night, and always keeps the ones still in use. See Build — from code to Docker image
• Environments: configuration variables, databases, storage, scheduled tasks, and deployments

Viewing URLs by environment

Click the View URLs icon (external link) next to an application to open the URLs by environment window. It lists, for each environment (dev, staging, prod): its name, its type, and the application's actual front-end address.

• A clickable address means the application is deployed and accessible in that environment.
• An address with the Pending badge means the architecture is declared but not yet synchronized in that environment — try again later or check the deployment.
• The message "No official front-end URL is declared" means no address has yet been designated as official for this application. This designation is done in the Architecture → URLs screen (rocket icon → Architecture → URLs → star next to the desired front-end route, or checkbox when creating/editing it). Only a route to a FRONT type service can be designated this way.

Going further

• Create profiles and rights for an application
• Manage programmatic access keys
• View an application's audit logs