bauhouse

<data>
  <hello>
    <entry id="1" type="statement">
      <phrase>Hello</phrase>
      <name>World</name>
    </entry>
    <entry id="2" type="question">
      <phrase>How are you</phrase>
    </entry>
  </hello>

bauhouse

<data>
  <hello>paste your xml here</hello>
</data>

bauhouse

<data>
  <hello>paste your xml here</hello>
</data>

bauhouse

<data>
  <hello>paste your xml here</hello>
</data>

bauhouse

<data>
	<hello>paste your xml here</hello>
</data>

bauhouse

<data>
	<hello>paste your xml here</hello>
</data>

bauhouse

<data>
  <hello>
    <entry id="2">
      <phrase>Hello</phrase>
      <name>World</name>
    </entry>
  </hello>
</data>

bauhouse

<data>
  <hello>
    <entry id="2">
      <phrase>Hello</phrase>
      <name>World</name>
    </entry>
  </hello>
</data>

bauhouse

A Symphony Workflow

I'm describing my workflow in these articles, before I start my next Symphony project. Mostly for myself, to iron out my recurring problems, it is based on solid git techniques, taking heed of advice learned from Symphony community members, many many tips on the web, and flicking through the pages of O'Reilly's Version Control with git.

The core aim of this article, is to get a good Symphony development and deployment environment using git as the basis for the organisation, and have it written down for reference.

This workflow can be applied to any project, in theory, that has a starting point being a private remote git repo.

Disclaimer

bauhouse

<?xml version="1.0" encoding="utf-8" ?>
<data>
	<params>
		<today>2011-10-27</today>
		<current-time>16:00</current-time>
		<this-year>2011</this-year>
		<this-month>10</this-month>
		<this-day>27</this-day>
		<timezone>-07:00</timezone>
		<website-name>Symphony CMS</website-name>