<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket #742: Stg site to play with</title>
    <link>http://localhost:8080/trac/ticket/742</link>
    <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
I'm trying to set up a stage site, just to test rearranging the homepage blocks.
&lt;/p&gt;
&lt;p&gt;
I created a site on the "Transition Network D6 S012 Booker" Platform, but I just get an empty pressflow site: &lt;a class="ext-link" href="http://stgsam.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://stgsam.transitionnetwork.org/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Can I use your stg site to test the block arrangement instead: &lt;a class="ext-link" href="https://booker-stage-20140501.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://booker-stage-20140501.transitionnetwork.org/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Or could you let me know what might be going wrong?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/ticket/742</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Thu, 12 Jun 2014 15:27:32 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:1</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.125&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.125&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Hi Sam,
&lt;/p&gt;
&lt;p&gt;
Feel free to use my stage site.
&lt;/p&gt;
&lt;p&gt;
I am cloning this site now, to see If  I get a empty pressflow site ..
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Thu, 12 Jun 2014 16:11:50 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:2</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:2</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.125&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.125&lt;/em&gt; to &lt;em&gt;0.25&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
I managed to cloned the site successfully again. I know, sorry ..
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://booker-stage-20140501-2.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://booker-stage-20140501-2.transitionnetwork.org/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Here's what I did:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Go the stage platform.   (Transition Network D6 S012 Booker / &lt;a class="ext-link" href="https://tn.puffin.webarch.net/hosting/c/platform_TransitionNetworkD6S012"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://tn.puffin.webarch.net/hosting/c/platform_TransitionNetworkD6S012&lt;/a&gt;)
&lt;/li&gt;&lt;li&gt;Click on the site I want to clone.  (&lt;a class="ext-link" href="https://tn.puffin.webarch.net/hosting/c/booker-stage-20140501.transitionnetwork.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://tn.puffin.webarch.net/hosting/c/booker-stage-20140501.transitionnetwork.org&lt;/a&gt;)
&lt;/li&gt;&lt;li&gt;Sacrifice 3 kittens - to the God of your choice.
&lt;/li&gt;&lt;li&gt;Click on the "run" button against the clone action: a modal dialogue window present itself; leave the plaform as the - current plaform - and click on the clone button
&lt;/li&gt;&lt;li&gt;Wait ..
&lt;/li&gt;&lt;li&gt; Voila
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
I guess you must have done something different?
&lt;/p&gt;
&lt;p&gt;
Paul
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Thu, 12 Jun 2014 18:02:45 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/742#comment:3</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:3</guid>
      <description>
        &lt;p&gt;
Paul can you point us to the documentation about this (and double check it's all there)? We'll cover this next week, but it's good to see it now - and for you to double check the documentation before the meet too ..
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Fri, 13 Jun 2014 12:27:32 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:4</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:4</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.25&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.25&lt;/em&gt; to &lt;em&gt;0.5&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Ed,
&lt;/p&gt;
&lt;p&gt;
The documentation for cloning a site on Aegir can be be found in the documentation on Aeigir:
&lt;/p&gt;
&lt;p&gt;
Cloning a site
&lt;a class="ext-link" href="http://community.aegirproject.org/node/24"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://community.aegirproject.org/node/24&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I found reading the documentation on Aeigir, and listening to the audio tutorial (on Aegir) from Jim  -taking notes- helpful in getting oriented.
&lt;/p&gt;
&lt;p&gt;
I have gone through all of our wiki documentation and found the documentation to be vey helpful. It's probably also complete - with the exception of those areas that are already highlighted by Jim.
&lt;/p&gt;
&lt;p&gt;
Just thinking about the call. I'm still new to Aeigir so there is very good chance I could suck in any questions and answers session :) I think I could probably best help others by taking questions on the mailing list, I'll then have an opportunity to reflect and consult the documentation / wiki as required. Actually, maybe be Jim would be better on the call than me? If he could be available .
&lt;/p&gt;
&lt;p&gt;
Best, Paul
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Fri, 13 Jun 2014 14:08:11 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:5</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:5</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.25&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.5&lt;/em&gt; to &lt;em&gt;0.75&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
It'll be interesting to hear what Sam did different, because that may indicate something ..
&lt;/p&gt;
&lt;p&gt;
Some thoughts:
&lt;/p&gt;
&lt;p&gt;
With anything that looks difficult - I always like to zoom out, and then zoom back in slowly. There is nothing that can't be understood in layman terms. There's a lot of voodoo language with Aegir - so you just have be clear that you understand the lingo.
&lt;/p&gt;
&lt;p&gt;
In terms that we can all agree on, we know we have website that has code and a database, and that we often have to bring in new code (e.g new features, security updates) and update the database - so that it works with the new code. So the idea is, we could maintain a document which keeps a list all the modules / themes we have installed, any patches that are applied , .. so that if we wanted to make an exact copy of the website, all we would need is the document (also call a makefile) and a copy of the database, and some kind of administrative interface  (platform) that can put these together with some input from you. Aegir gives you these administrative interfaces.
&lt;/p&gt;
&lt;p&gt;
So when in Aegir speak someone says, they have "cloned" the website on the "platform", this means, they have made a copy of the website using the *same* administrative interface; which means the website was built from the same document (makefile) as the original.
&lt;/p&gt;
&lt;p&gt;
And if after an update someone says, they have have built a new platform and "migrated" the site to the new platform, this means that they have updated the document (makefile) and built a *new administrative interface* and then using this administrative interface have built a website with an updated version of the document (makefile) and the database from the site that we being updated.
&lt;/p&gt;
&lt;p&gt;
Keywords: clone, migrate, platform , makefile
&lt;/p&gt;
&lt;p&gt;
Hope this help. (Damn, that took longer than 15 minutes :) )
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Fri, 13 Jun 2014 14:33:18 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:6</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:6</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.125&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.75&lt;/em&gt; to &lt;em&gt;0.875&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Notes that I took for Jim's talk ...
&lt;/p&gt;
&lt;p&gt;
Directory structure:
/data/disk/tn/static/&lt;a class="missing wiki"&gt;PLATFORM?&lt;/a&gt;/sites  (platform sites)
&lt;/p&gt;
&lt;p&gt;
Site level
&lt;/p&gt;
&lt;p&gt;
Clone: Make a copy of a site on a platform.
Migrate: pick up a site and move it to another platform,  …   …  switch the nginx config.  (e.g core updates)
&lt;/p&gt;
&lt;p&gt;
Create a domain alias with dev - allows you to view the site without caching enabled, and shows errors to the screen.
&lt;/p&gt;
&lt;p&gt;
if *Redirect domain aliases to main domain* is turned on this will need to be disabled to see the dev sites. Turned on for SEO.
&lt;/p&gt;
&lt;p&gt;
*.transitionnnetwork.org
*.*.transitionnnetwork.org .. pointing at Puffin server.
&lt;/p&gt;
&lt;p&gt;
Doing a core update …
Update makefile,
Build platform ,
Clone stage site on the same platform
Migrate site to the new platform
&lt;/p&gt;
&lt;p&gt;
Updating custom module / theme on the stage site you can delete the static copy and do a git clone to get a working copy
&lt;/p&gt;
&lt;p&gt;
Currently working on master branch. Not currently branching?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Mon, 16 Jun 2014 09:13:58 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/742#comment:7</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:7</guid>
      <description>
        &lt;p&gt;
Thanks Paul,
&lt;/p&gt;
&lt;p&gt;
I'd say that the skype would not be a 'Q&amp;amp;A' and 'howto', but a check-in on how it is working, how we will work from now on, and the other BOA ticket that Chris wants to talk about.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Mon, 16 Jun 2014 10:11:08 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:8</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:8</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.125&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.875&lt;/em&gt; to &lt;em&gt;1.0&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Thanks Ed
&lt;/p&gt;
&lt;p&gt;
Aeigir is working. I have been able to do everything that I have needed to do, so far.
&lt;/p&gt;
&lt;p&gt;
It's an interesting question how things should work going forward. I think the main problem with Aeigir seems to be managing the software?  and secondly some inertia in using it? I would be happy to consider any developer setup. Maybe a setup that revolves around terminal access to a developers home directory on the server, could work for everyone?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Mon, 16 Jun 2014 10:16:39 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/742#comment:9</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:9</guid>
      <description>
        &lt;p&gt;
Hi Paul, yes it is - and why we need to be together as a group to discuss it.
&lt;/p&gt;
&lt;p&gt;
It's also important to establish what TN needs and the likely architecture for TNv3 as part of that conversation, which Annesley will be working on.
&lt;/p&gt;
&lt;p&gt;
I don't think we'll sort something out this week, but it's important we see the need to work on it as a group, and how we'll do that.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Mon, 16 Jun 2014 10:22:27 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/742#comment:10</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:10</guid>
      <description>
        &lt;p&gt;
Sounds like a good plan. Thanks Ed.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Thu, 03 Jul 2014 12:56:34 GMT</pubDate>
      <title>component changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:11</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:11</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;component&lt;/strong&gt;
                changed from &lt;em&gt;Dev server&lt;/em&gt; to &lt;em&gt;Live server&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>paul</dc:creator>

      <pubDate>Fri, 10 Oct 2014 12:49:08 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/742#comment:12</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/742#comment:12</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.125&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;1.0&lt;/em&gt; to &lt;em&gt;1.125&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
@Sam
&lt;/p&gt;
&lt;p&gt;
This can  probably be closed.   Are you having any current problems creating a stage site?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>