I plan on having a development website, a staging website and a production website.
Each website will have it's own database.
I pointed one of my websites to a domain, but if I debug this website in localhost, it brings up the page in from the domain, not localhost. For example, I am pointing to www.websiteA.com, but debugging in http://localhost. If I go to the backoffice, and click the url link, Umbraco will nagivate to www.websiteA.com instead of http://localhost.
So given all this, is there a best practice to syncing websites and databases Umbraco so I don't have to make a change 3 times?
Is it common to have a structure like:
website.local -> no domain (defaults to local)
website.stage -> stage.websiteA.com
website.prod -> websiteA.com
If this is the case and I make a change in website.local, how can I sync the db and the the content between all 3
Hi Saied,
Do you have the domains configured on specific nodes (typically a home node but any node can have a domain configured)? That would explain why the url for a node has the domain instead of localhost.
You best bet is to always assume Live is master for content.
To keep staging in sync then after a release or three take a backup of live and use that for staging (binning off the old staging db).
Locally you can run your own copy of the db.
When ever you make doctype changes on local you repeat the process on staging/live (adding doctypes or properties to doctypes can't break anything and doing it there and then means you don't have to remember about it later come deployment time).
Not ideal but it work. Trying to do it via a tool is a bit of a nightmare and one of the reason Umbraco as a Service has taken 3 years to build. The other option you have is of course to use Umbraco as a Service.
Keeping Umbraco sites and databses in sync?
Ok, so here is my scenario.
I plan on having a development website, a staging website and a production website.
Each website will have it's own database.
I pointed one of my websites to a domain, but if I debug this website in localhost, it brings up the page in from the domain, not localhost. For example, I am pointing to www.websiteA.com, but debugging in http://localhost. If I go to the backoffice, and click the url link, Umbraco will nagivate to www.websiteA.com instead of http://localhost.
So given all this, is there a best practice to syncing websites and databases Umbraco so I don't have to make a change 3 times?
Is it common to have a structure like:
website.local -> no domain (defaults to local) website.stage -> stage.websiteA.com website.prod -> websiteA.com
If this is the case and I make a change in website.local, how can I sync the db and the the content between all 3
Hi Saied, Do you have the domains configured on specific nodes (typically a home node but any node can have a domain configured)? That would explain why the url for a node has the domain instead of localhost.
There is a plugin developed by Umbraco HQ called Courier that is designed to do what you want - http://umbraco.com/products-and-support/courier/
You best bet is to always assume Live is master for content.
To keep staging in sync then after a release or three take a backup of live and use that for staging (binning off the old staging db).
Locally you can run your own copy of the db.
When ever you make doctype changes on local you repeat the process on staging/live (adding doctypes or properties to doctypes can't break anything and doing it there and then means you don't have to remember about it later come deployment time).
Not ideal but it work. Trying to do it via a tool is a bit of a nightmare and one of the reason Umbraco as a Service has taken 3 years to build. The other option you have is of course to use Umbraco as a Service.
Cheers
Pete
Thanks,
As far as keep the umbraco nodes and content in sync, is courier a viable option?
is working on a reply...