The applications of a Beyond project

Before you start#

• This applies only to a CDN installation that is connected to Beyond Projects. Without the connection, applications work as they always did and none of these screens appear.
• To register, add or release you need the application.manage capability: Owner, Administrator or Developer of the organization. A Viewer sees the project context and the Project panel, without actions.
• The project must exist in Beyond Projects, be active and belong to the same organization as the applications.

One rule to keep in mind#

An application belongs to at most one project. A project may have many applications: a storefront and its back office, a site and its API. An application with no project stays valid: nothing requires a project to register, prepare, release, bind a domain or serve.

The project is a reference on the application and nothing else. Adding an application to a project, or releasing it, changes no identifier, release, domain, address, quota, plan or credit, and published delivery serves the same whether or not Projects answers. The exact contract is in The project of an application.

Arrive from Beyond Projects#

1. In Beyond Projects, open the project and choose Open on Applications in CDN.
2. CDN administration signs you in if needed, finds the organization that owns the project and opens its applications, filtered to the project.

Expected outcome: above the list, a notice titled "Project: {name}" with the name of the project says "Showing only the applications of the project" and shows the project identity. It has the links Open in Projects, when the installation configured the Projects address, and Show all applications.

The address grants nothing. A project that you may not see is the ordinary not-found screen, exactly like a project that does not exist.

Register an application for this project#

1. In the project context, choose Register an application for this project. With no applications yet, the list says "No applications in this project yet" and "Register an application for this project, or add one that already exists. The project itself is never registered again."
2. The dialog is the ordinary Register an application dialog, with the line "The application will belong to the project" and the project identity. Fill it in as in Applications and targets.
3. Choose Register application.

Expected outcome: the application opens with a Project panel. The project itself is never registered again, in CDN or anywhere else.

The project is checked before anything is created, so a refusal creates no application. If Projects confirms late, the application exists and its link reads Pending confirmation: see the Project panel.

Add an existing application#

Use this for an application that was registered before the project existed.

1. In the project context, choose Add an existing application.
2. In Add an existing application to the project, choose the Application. The list holds the applications of the organization that belong to no project. If it says "Every application of this organization already belongs to a project.", there is nothing to add.
3. Read the rule: "Only the reference changes. The application keeps its identifier, releases, domains and addresses."
4. Choose Add to project.

Nothing is matched by name. An application called exactly like the project is not part of it until you add it.

The Project panel of an application#

An application that belongs to a project shows the panel Project. An application with no project shows no panel, and that is not an error.

Under them, Open in Projects and Applications of this project.

Pending confirmation comes with the notice "Projects has not confirmed this link yet": "The application exists and works. CDN recorded the project, but Projects did not confirm the link when it was asked. Trying again is safe: nothing is duplicated." Choose Try again. It either becomes Confirmed by Projects or shows the refusal.

Release an application from its project#

1. In the Project panel, choose Release from project.
2. The dialog asks "Release this application from its project?" and states: "Only the reference is removed. The application, its releases, domains and published addresses stay exactly as they are, and it can be added to a project again."
3. Choose Release from project to confirm, or Cancel.

To move an application to another project, release it first and then add it there. There is no implicit move.

When it is refused, or Projects does not answer#

In every case the applications, their releases and what they serve are untouched.

Limits#

Next action#

Define the targets of the application, or go back to the project in Beyond Projects.