The name of the Project. This is used to identify the Project and is also used in the URL to invoke the Project.
The description of the Project. This is used to provide additional information about the Project.
Labels are used to categorize Projects. They are used to filter out and group Projects together for easier management.
The visibility of a Project determines who can access it. There are two options:
- Public: do not require an API key to invoke the Project (public URL)
- Private: require an API key to invoke the Project
A Project can be deployed to a specific environment. This will create a new deployment and boot it. The
deploymentId is used to identify the deployment and in the URL to invoke the Project.
The entrypoint file is the file that will be executed when a Project is invoked. This file will be executed as-is, without the need for a build step.
You can check if the current file is the entrypoint file by checking the
i boolean variable.
Environment variables are key-value pairs that are available to your Project at runtime. They can be used to store secrets, configuration values and more. Environment variables are scoped to the Project and are not shared with other Projects. All Projects have two environments:
Transfer the Project to another Workspace or delete the Project permanently.