Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We have done this by setting up an ASPX on our daily build and QA websites that triggers a publish. The build then has a Powershell call to trigger this. We've done this with CruiseControl, TeamCity, and Team Build.</p> <h2>TeamCity Configuration</h2> <p>The configuration for TeamCity uses an additional build step after you've deployed files and TDS:</p> <ol> <li><strong>Runner Type:</strong> Powershell</li> <li><strong>Step name:</strong> Trigger Publish to Web DB</li> <li><strong>Powershell run mode:</strong> x64</li> <li><strong>Working Directory:</strong> [no value]</li> <li><strong>Script:</strong> Source code</li> <li><p><strong>Script Source:</strong> </p> <p>$r = [System.Net.WebRequest]::Create('http://myqasite/SomePath/Publish.aspx'); $resp = $r.GetResponse();</p></li> <li><strong>Script execution mode:</strong> Put script into Powershell stdin with "-Command -" arguments</li> </ol> <h2>Publish.aspx</h2> <p>The code for our Publish page is something like this:</p> <pre><code> string full = Request.QueryString["full"]; // Set up the publish mode PublishMode publishMode = PublishMode.Smart; if (!string.IsNullOrWhiteSpace(full) &amp;&amp; (full == "1" || full.Equals("true", StringComparison.InvariantCultureIgnoreCase)) ) { publishMode = PublishMode.Full; } using (new Sitecore.SecurityModel.SecurityDisabler()) { //We need the target database var webDb = Sitecore.Configuration.Factory.GetDatabase("web"); //source db var masterDb = Sitecore.Configuration.Factory.GetDatabase("master"); try { foreach (Language language in masterDb.Languages) { //loops on the languages and do a full republish on the whole sitecore content tree var options = new PublishOptions(masterDb, webDb, publishMode, language, DateTime.Now) {RootItem = masterDb.Items["/sitecore"], RepublishAll = true, Deep = true}; var myPublisher = new Publisher(options); myPublisher.Publish(); } } catch (Exception ex) { Sitecore.Diagnostics.Log.Error("Could not publish the master database to the web", ex); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAutomatic publish of Sitecore content at end of TDS CI deploy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJay S
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAutomatic publish of Sitecore content at end of TDS CI deploy
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt's probably unnecessary to do a full publish of the entire content tree. TDS edits items and places them into the Publish Queue, so you should be able to trigger an incremental publish which will do the same job but a lot more efficiently. NOTE: either way, you'll need workflows properly set up across all content and media items, in case an editor has made a change that they don't want published yet.
      singulars
      1. PO
      1. USSean Holmesby
    2. COSean: this is only going to happen in QA and it will be a full db reset :)
      singulars
      1. PO
      1. USandycwk
    3. CONote that the code above defaults to doing a Smart publish and only does a full publish if the user requests it in the URL to the page.
      singulars
      1. PO
      1. USJay S
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload