Say I have a production site and a development site (say, hosted at TxD). Using SVN for version control. I want to be able to keep the client updated on the development site (that would track the trunk branch), and then be able to create release branches for each release (which switchtower would then push out to the production site). It would be great if the development site was at http://dev.thesite.com and the production site was at all other urls for thesite.com. Anyone using switchtower for anything like that? Any pointers? Thanks, Joe
On Aug 26, 2005, at 9:44 PM, Joe Van Dyk wrote:> Say I have a production site and a development site (say, hosted at > TxD). Using SVN for version control. > > I want to be able to keep the client updated on the development site > (that would track the trunk branch), and then be able to create > release branches for each release (which switchtower would then push > out to the production site). > > It would be great if the development site was at > http://dev.thesite.com and the production site was at all other urls > for thesite.com. > > Anyone using switchtower for anything like that? Any pointers?You''ll want to create two separate recipe files, one for your dev configuration and one for prod. However, the problem is that switchtower does not (currently) support specific releases, but I hope to rectify that in the next few days. One way to work around the lack is to tag the releases you want, and then modify your recipe for every release so that the repository named is the path to the tag you want to release. An awful hack, I know, but like I said, specific releases will be supported soon (today, if I can find the time to work on it). - Jamis
On 8/27/05, Jamis Buck <jamis-uHoyYlH2B+GakBO8gow8eQ@public.gmane.org> wrote:> On Aug 26, 2005, at 9:44 PM, Joe Van Dyk wrote: > > > Say I have a production site and a development site (say, hosted at > > TxD). Using SVN for version control. > > > > I want to be able to keep the client updated on the development site > > (that would track the trunk branch), and then be able to create > > release branches for each release (which switchtower would then push > > out to the production site). > > > > It would be great if the development site was at > > http://dev.thesite.com and the production site was at all other urls > > for thesite.com. > > > > Anyone using switchtower for anything like that? Any pointers? > > > You''ll want to create two separate recipe files, one for your dev > configuration and one for prod. However, the problem is that > switchtower does not (currently) support specific releases, but I > hope to rectify that in the next few days. > > One way to work around the lack is to tag the releases you want, and > then modify your recipe for every release so that the repository > named is the path to the tag you want to release. An awful hack, I > know, but like I said, specific releases will be supported soon > (today, if I can find the time to work on it).So switchtower only works with the trunk branch (by default)?
> So switchtower only works with the trunk branch (by default)?No, by default it just works with one. But you can even inject some dynamics into that by using ENV variables. Ala: set :repository, "svn+ssh://www.example.com/var/repos/app/#{ENV[''SVN_PATH''] || ''trunk''}" Then you can deploy a tag with: rake deploy SVN_PATH=''tags/rel_12'' -- David Heinemeier Hansson http://www.loudthinking.com -- Broadcasting Brain http://www.basecamphq.com -- Online project management http://www.backpackit.com -- Personal information manager http://www.rubyonrails.com -- Web-application framework
On Aug 27, 2005, at 5:31 PM, Joe Van Dyk wrote:> On 8/27/05, Jamis Buck <jamis-uHoyYlH2B+GakBO8gow8eQ@public.gmane.org> wrote: > >> On Aug 26, 2005, at 9:44 PM, Joe Van Dyk wrote: >> >> You''ll want to create two separate recipe files, one for your dev >> configuration and one for prod. However, the problem is that >> switchtower does not (currently) support specific releases, but I >> hope to rectify that in the next few days. >> >> One way to work around the lack is to tag the releases you want, and >> then modify your recipe for every release so that the repository >> named is the path to the tag you want to release. An awful hack, I >> know, but like I said, specific releases will be supported soon >> (today, if I can find the time to work on it). >> > > So switchtower only works with the trunk branch (by default)? > _By default, yes. However. you can now specify the revision you want to check out by setting the :revision variable. And you can do it from the command line: switchtower -vvvv -r deploy -a update_code -s revision=1234 I''m still working on specifying revisions via tags, so if that''s what you need, you''ll need to wait a bit longer (or submit a patch). - Jamis
On 8/28/05, Jamis Buck <jamis-uHoyYlH2B+GakBO8gow8eQ@public.gmane.org> wrote:> On Aug 27, 2005, at 5:31 PM, Joe Van Dyk wrote: > > > On 8/27/05, Jamis Buck <jamis-uHoyYlH2B+GakBO8gow8eQ@public.gmane.org> wrote: > > > >> On Aug 26, 2005, at 9:44 PM, Joe Van Dyk wrote: > >> > >> You''ll want to create two separate recipe files, one for your dev > >> configuration and one for prod. However, the problem is that > >> switchtower does not (currently) support specific releases, but I > >> hope to rectify that in the next few days. > >> > >> One way to work around the lack is to tag the releases you want, and > >> then modify your recipe for every release so that the repository > >> named is the path to the tag you want to release. An awful hack, I > >> know, but like I said, specific releases will be supported soon > >> (today, if I can find the time to work on it). > >> > > > > So switchtower only works with the trunk branch (by default)? > > _ > > By default, yes. However. you can now specify the revision you want > to check out by setting the :revision variable. And you can do it > from the command line: > > switchtower -vvvv -r deploy -a update_code -s revision=1234 > > I''m still working on specifying revisions via tags, so if that''s what > you need, you''ll need to wait a bit longer (or submit a patch).Thanks. Do you guys do all the releases from one branch? You don''t make a release branches?
Howdy. Is it possible in Rails to make www.mysite.com/anyname<http://www.mysite.com/anyname>result in a page displayed that is essentially a custom "about me" portal page for a user? For example, user bob exists in the database, so I want www.mysite.com/bob <http://www.mysite.com/bob> to show a bob-specific page (without authentication, or rather allowing anyone to see). I''ve done this in JSP using a custom 404 page that redirects to www.mysite.com/main.jsp?portal=bob<http://www.mysite.com/main.jsp?portal=bob>. While not elegant, it works well. Is there a way (and better yet, an elegant way) to do this in Rails? Thanks! Michael _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 8/29/05, Michael Teter <michael.teter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Howdy. > > Is it possible in Rails to make www.mysite.com/anyname<http://www.mysite.com/anyname>result in a > page displayed that is essentially a custom "about me" portal page for > a user? >Hi Michael, I haven''t tried it and admittedly I''m a newbie at rails, but this should be possible with routes.rb. Something like.. map.connect '':user'', :controller => ''portal'' And then you can just call params[:user] in the ''index'' action of your portal controller. I guess you can redirect either to the correct user page from there or the main application index if you don''t find a match. -Pawel _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails