Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
What should be included in source control and in what structure?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Garth  
View profile  
 More options Jul 9 2008, 2:03 pm
From: Garth <ga...@wi.llia.ms>
Date: Wed, 9 Jul 2008 11:03:24 -0700 (PDT)
Local: Wed, Jul 9 2008 2:03 pm
Subject: What should be included in source control and in what structure?
## newbie_faq_question ##

When staring a new project based on sproutcore, what is the
recommended source control setup?

For example, is it recommended that /public be excluded from checkins?

Also, sproutcore, unlike most web dev frameworks, requires an
additional framework for the backend.  When working working with
multiple frameworks (eg, sproutcore + rails) what is the recommended
trunk/main layout? Is something like the following advisable, could
you mix both frameworks in the same tree, or is there a preferred
alternative?

<trunk>/sproutcore/<sproutcore tree>
<trunk>/rails/<rails tree>


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
gskluzacek  
View profile  
 More options Jul 10 2008, 2:28 pm
From: gskluzacek <gskluza...@gmail.com>
Date: Thu, 10 Jul 2008 11:28:55 -0700 (PDT)
Local: Thurs, Jul 10 2008 2:28 pm
Subject: Re: What should be included in source control and in what structure?
Garth,

I will add your question to the Newbie FAQ.

I'm no source control expert, so I don't have a very official answer
for you other than pick a best practice and stick with it.

I would think that you would want everything in the clients directory
to be under source control as well as any other files that you add to
the directory structure created by SproutCore, such as additional
JavaScript files for additional/custom frameworks & libraries.

The SproutCore application when deployed to your production server
will reside in the <web root>/static directory (unless you change your
application build root in the sc-config file -- see
http://github.com/sproutit/sproutcore/wikis/changing-your-application...
) so your back end script files to connect to the db server etc can
reside any where really.

Additionally, durring development, the httpd server servering up your
SproutCore application and the httpd server serving up your scripts
for you back end db access will be different, so you will either want
to
1) set up reverse proxy so SproutCore can call your back end scripts
see here for details on this - Mixing the Build Tools with Your
Backend Server http://github.com/sproutit/sproutcore/wikis/about-the-sproutcore-buil...
2) or use the proxy setting in the the sc-config file

So with regards to source control, it probably doesn't matter where
they get placed relative to the sproutcore files.

Hope that helps a little.
-- Greg Skluzacek

On Jul 9, 1:03 pm, Garth <ga...@wi.llia.ms> wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google