Hi all-- I''m starting a new Rails project and I''m preparing to import it into my local Subversion repository. In the past, I''ve just imported the entire set of files generated by ''rails'', but I''m starting to wonder if that is the best way to approach things. For instance, it makes sense to add the log/ directory, but probably not the actual log files (unless you have some perverse need to keep versioned copies of them around). Does anyone else have any suggestions for what to keep and discard when importing a brand new project? Thanks, Patrick -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Patrick J. Franz patrick-LkoapWg8zFbQT0dZR+AlfA@public.gmane.org
On Thu, 03 Mar 2005 20:42:45 -0800, Patrick Franz -- ML <patrick-LkoapWg8zFbQT0dZR+AlfA@public.gmane.org> wrote:> Does anyone else have any suggestions > for what to keep and discard when importing a brand new project?I generally move the database.yml file to database.yml.orig before importing into subversion, and then I set the config directory to ignore database.yml. This way, you can just make a copy of the file when you check out the source, and you don''t have to worry about accidentally sending your database password to the repository for everyone else to see. This isn''t that big of a deal if you are the only one who will ever access the repository, though. -- Regards, John Wilger ----------- Alice came to a fork in the road. "Which road do I take?" she asked. "Where do you want to go?" responded the Cheshire cat. "I don''t know," Alice answered. "Then," said the cat, "it doesn''t matter." - Lewis Carrol, Alice in Wonderland
Patrick Franz -- ML wrote:> > Hi all-- > > I''m starting a new Rails project and I''m preparing to import it into my > local Subversion repository. In the past, I''ve just imported the entire > set of files generated by ''rails'', but I''m starting to wonder if that is > the best way to approach things. > > For instance, it makes sense to add the log/ directory, but probably not > the actual log files (unless you have some perverse need to keep > versioned copies of them around). Does anyone else have any suggestions > for what to keep and discard when importing a brand new project? > > Thanks, > Patrick >I personally keep everything generated by the ''rails'' command, I ignore the log files, and I ignore the database config file (but that''s up to you). Essentially you should be able to check out a copy of your app and run it (adding a db config file first, if you don''t store those). That''s how I roll with it, anyway. Working well for me. If you have stuff in vendor/ you may or may not want that, or may link that via something like svn:externals, that''s up to your situation. -Scott _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
I keep everything in svn except the logs, and database.yml and environment.rb. Those to i have in svn but as database.yml.backup and environment.rb.backup. I then use xal''s deploy script to pull those out and use them when i do a deployment. When i''m setting up a development box for somebody then i manually copy those over and edit them. It works pretty well for us. -rabble On Thu, 03 Mar 2005 23:56:09 -0500, Scott Barron <scott-HDQKq3lYuGDk1uMJSBkQmQ@public.gmane.org> wrote:> Patrick Franz -- ML wrote: > > > > Hi all-- > > > > I''m starting a new Rails project and I''m preparing to import it into my > > local Subversion repository. In the past, I''ve just imported the entire > > set of files generated by ''rails'', but I''m starting to wonder if that is > > the best way to approach things. > > > > For instance, it makes sense to add the log/ directory, but probably not > > the actual log files (unless you have some perverse need to keep > > versioned copies of them around). Does anyone else have any suggestions > > for what to keep and discard when importing a brand new project? > > > > Thanks, > > Patrick > > > > I personally keep everything generated by the ''rails'' command, I ignore > the log files, and I ignore the database config file (but that''s up to > you). Essentially you should be able to check out a copy of your app > and run it (adding a db config file first, if you don''t store those). > That''s how I roll with it, anyway. Working well for me. If you have > stuff in vendor/ you may or may not want that, or may link that via > something like svn:externals, that''s up to your situation. > > -Scott > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > > >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Wilger wrote: | On Thu, 03 Mar 2005 20:42:45 -0800, Patrick Franz -- ML | <patrick-LkoapWg8zFbQT0dZR+AlfA@public.gmane.org> wrote: | |>Does anyone else have any suggestions |>for what to keep and discard when importing a brand new project? | | | I generally move the database.yml file to database.yml.orig before | importing into subversion, and then I set the config directory to | ignore database.yml. This way, you can just make a copy of the file | when you check out the source, and you don''t have to worry about | accidentally sending your database password to the repository for | everyone else to see. This isn''t that big of a deal if you are the | only one who will ever access the repository, though. Thanks, that sounds like a reasonable idea. Regards, Patrick - -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Patrick J. Franz patrick-LkoapWg8zFbQT0dZR+AlfA@public.gmane.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCJ+8unBL/CxPCaScRAl7QAKCUS7m+ZsVPHf4WqkQD3Vu6ghtv4gCfR2FW mCq5xxALaFBkNhILuC7V+u4=uSoD -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Barron wrote: | Patrick Franz -- ML wrote: | |> |> Hi all-- |> |> I''m starting a new Rails project and I''m preparing to import it into |> my local Subversion repository. In the past, I''ve just imported the |> entire set of files generated by ''rails'', but I''m starting to wonder |> if that is the best way to approach things. |> |> For instance, it makes sense to add the log/ directory, but probably |> not the actual log files (unless you have some perverse need to keep |> versioned copies of them around). Does anyone else have any |> suggestions for what to keep and discard when importing a brand new |> project? |> |> Thanks, |> Patrick |> | | I personally keep everything generated by the ''rails'' command, I ignore | the log files, and I ignore the database config file (but that''s up to | you). Essentially you should be able to check out a copy of your app | and run it (adding a db config file first, if you don''t store those). | That''s how I roll with it, anyway. Working well for me. If you have | stuff in vendor/ you may or may not want that, or may link that via | something like svn:externals, that''s up to your situation. Right. My goal is to be able to do an ''svn export'' and go live. Thanks for the advice. Patrick - -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Patrick J. Franz patrick-LkoapWg8zFbQT0dZR+AlfA@public.gmane.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCJ++lnBL/CxPCaScRAjY2AKC7yK/HzxxQAC0Tw5Yibwo/23tmGwCfdI8q gw2louBGZFxc7hBUCNMXJJY=DFVf -----END PGP SIGNATURE-----