Although you can log in to your CMS directly on Umbraco Cloud and install a package this is not recommended. The reason for this is that your uSkinned Site Builder package will make many changes to your environment. If you install directly on Umbraco Cloud several of these changes might not be registered resulting in these changes being lost if you then decide to work locally or deploy your site to different environments on Umbraco Cloud.
Login to the Umbraco Cloud portal (https://umbraco.io).
Go to your project.
Hit to 'How to connect to your machine'. Copy this URL.
On your computer, paste the URL into your git client or terminal and your site will be downloaded to your local machine. We would recommend GitKraken or Source Tree.
Open your site in Visual Studio Code. Assuming you have IIS Express for VS Code installed, you can run the website in a browser by hitting CTRL+F5 then choosing which browser in the prompt window.
Login to Umbraco CMS.
Go to the Packages section.
Select Install Local from the top right-hand side.
Browse to the location of the package on your computer. This should be a Zip folder of the Site Builder package.
Please wait while the package uploads.
Read and accept the terms and conditions on the screen. Click install to begin.
Please wait while the Site Builder package installs. This may take several minutes, please be patient and do not navigate away from the screen. :-)
Please wait while Umbraco CMS restarts. Please do not navigate away from the screen.
Please wait while the browser window refreshes. Please do not navigate away from the screen.
Now you can click to 'Finish' the installation. Please do not navigate away from the screen until you have clicked 'Finish'.
Your uSkinned Site Builder Package has successfully installed. Now navigate to the Content section to start building your new Umbraco website.
On your computer, open your git client or terminal from earlier. Now push your updates back to Umbraco Cloud.
It is important to make sure that you push all changes back to Umbraco Cloud. Some files are automatically ignored by your git client so you must make sure that the following files are committed and pushed back to Umbraco Cloud:
/App_Code (All files)
/App_Plugins/ (All files)
/css (All files)
/images (All files)
/Media (All files)
/scripts (All files)
/usn (All files)
/views (All files)
All changes that the Site Builder has made to your website will now be deployed to Umbraco Cloud. Example content will not be present yet. If you login to the Umbraco Cloud CMS and access the Settings section of Umbraco, you will now see new Document Types, Templates, Partial Views etc have been added.
You now want to deploy any content and media items that you have added to your local site. First, go to the Media section of Umbraco. Right-click the Media heading and select 'Queue for transfer'. Click the 'Queue' button.
Return to the Content section of Umbraco. Click the 'Send changes to Live workspace' button. This will start the process of uploading your media items to the live Umbraco Cloud environment.
Next, you want to deploy your content to the live Umbraco Cloud environment. Right-click the 'Content' heading and select 'Queue for transfer. Click the 'Queue' button.
Click the 'Send changes to Live workspace' button. This will start the process of transferring your content changes to the live Umbraco Cloud environment.
Your uSkinned Site Builder will now be completely deployed to your Umbraco Cloud environment. Login to the Umbraco Cloud CMS or browse to your Umbraco Cloud URL to see the website.
Additional steps - if necessary
If you run into any issues with your content not loading on Cloud, or you see errors when you try to edit a page in the CMS on Cloud, please do the following.
- Go to the folder ~/data/
- Open the command prompt as an admin
- cd to the ~/data/ folder
- Run the command echo > deploy-export
- Go to your Git client, there should be around 400(ish) new files
- Push these files to Cloud
Once your push has completed, go to your Umbraco Cloud site.
- Login to the CMS
- Go to Settings
- Click on the Published Status tab
- Memory Cache > Reload
- Database Cache > Rebuild
Once this is complete, go to the front end of your site and hit a hard refresh. Your site should be working as expected. :-)