Skip to content

Update environment references where needed in the FAQ article #7008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 7, 2025
Merged

Update environment references where needed in the FAQ article #7008

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions umbraco-cloud/frequently-asked-questions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1003,7 +1003,7 @@ Other reasons for missing the upgrade:

For more details, see the [Upgrades](product-upgrades/README.md#the-process-of-auto-upgrading-a-umbraco-cloud-project) article.

### Do pending commits (dev to live environment) derail the upgrade process?
### Do pending commits between environments derail the upgrade process?

Pending commits do not stop the auto-upgrade.

Expand Down Expand Up @@ -1085,7 +1085,7 @@ Yes, TDE is enabled by default for sites created after May 2, 2017. For older si

### Can a shared SQL Server be used for a development team instead of the SQL/LocalDb database created by Umbraco Cloud?

No, a shared database should not be used. Umbraco Cloud is designed so each team member can safely make changes and push them to the development environment. Other developers can do the same, allowing changes to be tested in a structured way. Once changes are confirmed, developers can pull updates and continue working on new features.
No, a shared database should not be used. Umbraco Cloud is designed so each team member can safely make changes locally and push them to the Cloud environment. Other developers can do the same, allowing changes to be tested in a structured way. Once changes are confirmed, developers can pull updates and continue working on new features.

Using a shared database can cause two major issues:

Expand Down