|
MononcQc posted:There would be all kinds of scaling complications like sharding [...] which would make it impractical for anything but a small personal blog or for a similar concept. I hate that everyone is so obsessed with scaling. If you make it as big as Google then you can afford to worry about scaling. Killing novel ideas because they might not scale to thousands of concurrent users is ridiculous.
|
#
¿
Apr 16, 2009 22:13
|
|
|
|
| # ¿ Apr 27, 2024 20:12 |
|
|
That this is the first mention of darcs makes me sad.
|
|
#
¿
Apr 17, 2009 02:34
|
|
|
Sebbe posted:Any recommendations for something I can easily set up, preferably on a HostGator shared account (not likely, it seems) or some sort of free hosting site (Like GitHub and Google Code, for instance, only allowing for private projects without paying a subscription)? http://patch-tag.com offers github for darcs. Dunno about private projects. supster posted:Yep, using SVN. You could use svk or git-svn, both of which have interactive commit functionality. svk ci -i and git add -p. There would be a lot of other benefits, like every operation not being slow as gently caress.
|
|
#
¿
Apr 30, 2009 01:45
|
|
|
Otto Skorzeny posted:I want to have a release branch with a bunch of dummy config files, and a regular working branch with fleshed-out versions of those same config files We solve that one by having two config files: config.yml which is versioned and site_config.yml which is not. site_config trumps config. If you're using Perl then Hash::Merge is perfect for combining the configs.
|
|
#
¿
May 1, 2009 23:06
|
|
|
I just converted nearly all of my repositories to git. 
|
|
#
¿
Jun 4, 2009 20:45
|
|
|
You can also use git svn fetch -r3950 to treat everything before the first 3950 commits as one huge commit, which is fast.
|
|
#
¿
Jun 8, 2009 21:11
|
|
|
|
| # ¿ Apr 27, 2024 20:12 |
|
|
Pesch posted:Are you supposed to create one SVN repository to put all your projects in, or are you supposed to create a seperate SVN repository for each of your projects? Either works just fine. If you want to give someone a commit bit to just one project, Subversion supports that. Keeping everything in one repository makes certain operations like testing and debugging multiple projects easier. You can checkout a specific revision of each project, rather than fooling around with correlating revision numbers with timestamps. I don't recall any specific benefits of a separate svn repository for each project.
|
|
#
¿
Aug 22, 2009 02:42
|
|