Project Settings
Last updated
Last updated
When working with an Umbraco Cloud project, you can handle a lot of the project configuration directly in the Umbraco Cloud Portal. You can manage the following configurations from the left-side menu:
See an overview of your environments for your project as well as access the frontend, backend, or clone down the environment.
See who is added to your project, add new Team members, backoffice users and technical contacts, and pending invites.
You can view the Summary of your Umbraco Cloud project in the overview menu under Summary.
Manage the team members and user permissions on your project. You can also view the backoffice user groups for each team member, view pending project invites, and manage Technical contacts for your project.
On the project history page, you can see a history of activities that have happened on your projects.
You can see metrics related to the overall health and performance of the Azure app service hosting the live environment of your solution.
On your Umbraco Cloud project, it is possible to see the usage of Custom Domains, Media Storage, Content Nodes, and Bandwidth for the project. You can also check if it is using above or below the allowed amount for the plan that your project is on.
Find connection details to your Umbraco Cloud databases. You need to allow your IP to connect to the databases with your local machine.
We handle minor and patch upgrades for the Umbraco components used by Umbraco Cloud, so you don't have to. From the Automatic Upgrades page, you can control if you want to opt in or out of automatic minor upgrades.
New projects are opt-in by default.
Manage CDN Cache settings for your project. You can modify default settings, which apply to all hostnames added to the current Project. Alternatively, you can set up specific settings per hostname, if you want to have different settings for certain hostnames.
Binding hostnames to your Umbraco Cloud project is done from the Hostnames section in the Settings menu on the Umbraco Cloud Portal.
If you have your own custom certificate, you can upload and bind it to your custom hostnames. This can be done instead of using the TLS: Transport Layer Security (HTTPS) certificates provided by the Umbraco Cloud service.
It is possible to configure a deployment webhook on your environments on Umbraco Cloud projects. This will be triggered upon successful deployments, you can configure where you would like information about the deployment to be posted.
Manage Advanced settings for your project from the Settings menu:
Enable static outbound IP addresses for projects on a Standard, Professional, or Enterprise plan.
Enable IIS logging for each of your environments. The log files can be accessed through kudu in C:\home\LogFiles\http. There is a rolling size limit on the log files of 100 MB. Once the limit is reached, the oldest log files will be overwritten by new ones.
Change .NET framework runtime for your Umbraco installation for each environment of your cloud project.
When enabling IIS logging, the site will have to restart. For more information about IIS logging, look at the Official Microsoft Documentation.
With this setting, it is possible to create a database backup of one or more of your cloud environments.
Public access is by default available for projects created after the 10th of January 2023.
The Umbraco.Cloud.Cms.PublicAccess package can be installed to enable Public access for projects created before the 10th of January 2023.
You can deny access to your project with the Public access setting.
Users who are not part of the project or whose IP has not been allowed will not be able to access the project.
You can disable/enable it with one click on the Public access page.
Access to manage Public access requires your project to be on the Standard plan or higher.
Manage transport security settings for your project. You can configure certain transport security options for all hostnames or specific hostnames within your project.
If your Umbraco Cloud project uses sensitive information such as API keys, encryption keys, and connection strings, it is recommended to store these as secrets.
You can upgrade your project to a Standard or a Professional plan, from the Settings menu, depending on your needs. The option is not available if you are already on the specific plan or if you are running in Trial mode.
You can rename your Umbraco Cloud project from the Management tab in the menu.
If you are working locally, you need to update the origin of your local git repository to point to the new clone URL. Alternatively, you can make a fresh local clone of the project, once you’ve changed your project name.
You can rename your project from the Rename Project section in the Settings menu on the Umbraco Cloud Portal. When you rename a project, the default hostnames and clone URLs assigned to the project are updated to match the new project name. You can also rename your project files and folders locally.
You can change your Umbraco Cloud project to run in a dedicated setup with additional computational resources compared to the shared setup. You can choose between the different dedicated options depending on the number of resources you will need for your project.
You can delete your Umbraco Cloud project from the Settings menu. Deleting your Umbraco Cloud project is permanent - all data, media, databases, configuration, setup, and domain bindings are removed in the process.
Deleting your Umbraco Cloud project will also cancel any subscriptions you have set up for the project.
