I have an Umbraco (16) Cloud site running at https://opensourcecloud.lotte.dev. Or least I do for now, I won't keep this site running for ever!
I'm using this public GitHub repository as the "working" directory for that project: all development on the site should be done here, not committed directly to the Cloud git repo. There's a GitHub Action that, fingers crossed, gets everything it needs from GitHub Secrets to push to Cloud and update the live site!
BTW I've written this blog post explaining how I set all this up in case you want to give it a go yourself.
But first we'd love people to try running the site locally and contributing back - see the steps below. Would a workflow like this enable the community to contribute to the new Umbraco Community site that we're currently building on Cloud?
- Fork this repository
- Clone locally
- Open
OpenSourceTest.slnin Rider|Visual Studio and start the website project - In the browser click the
Open Umbraco without restorelink - Log in using
community@umbraco.comandcommunity! - Settings section > Deploy dashboard > press the
Update Umbraco schema from data filesbutton - Content section > Click ... top-left > select the
Importoption - Click to upload and navigate to the
content-importfolder off root - Import each file separately working in alphabetical (i.e. date) order:
- Leave all options ticked and press
Import - If it complains about signatures, try clearing the signatures in Settings section > Deploy dashboard > press the
Clear Signaturesbutton
- Leave all options ticked and press
- Confirm that now have a working home page at
https://localhost:44390
I've raised issues for specific things I'd like people to test. But you're welcome to try whatever you like to have a go at the workflow contribution yourself.
In your fork, please work in a branch and a raise a pull request targetting the default branch of develop.
If you're creating new Document Types, Templates or Data Types you should see a corresponding .uda file for each item in your list of changes to commit. Make sure you commit those!
If you have new/updated content in the content tree that would be useful to share with others to review/test your changes, then find the content node in the Content section and:
- Click the three dots ...
- Select
Export - Tick
Include all items below,Include content dependencies, andInclude content file dependencies. Do not tick the schema-related options as these you should have already committed. - Download the resulting zip file and save in the
content-importfolder using the naming convention ofYYYYMMDD-nodename.zip - Commit this zip file and create your pull request!
If you have issues, or any thoughts in general on this set up, please let me know!
SuperTak 😀