On Sun, Aug 10, 2008 at 5:51 PM, Juan Pablo Califano <[EMAIL PROTECTED]> wrote: > Well, I can say that I've experienced some problems regarding speed when > browsing code. The items in the left menu sometimes just keep showing a > "loading..." mesagge, but they never completely load, making it hard to > access some file in the browse code view. Usually, trying again solves > it. I'm not sure it's my connection, because I've seen that behaviour in a > number of different machines. It doesn't happen all the time, but it's not > too rare.
oh ok I thought you were saying that the use of the SVN with HTTPS was slow.. so 2 different things I experienced the "loading..." too but honestly it look more an AJAX probleme than slow servers but I find it ok, you want the speed on the SVN access as a priority the rest is kind of secondary > > Appart from that, the two main problems I see are the quota limit and that > you're unable to export your repository (for moving to another hosting > service, if you find that appropriate at some future point). About the > quota, I think it's reasonable anyway to put some limit, and the faq's say > that if you hit the limit (which admitedly is fine for most projects), you > can ask for more space, so it's not that terrible, probably. I saw more than once people asking for quota increase and got it pretty fast, note that you have differeant quotas: SVN quota, download quota, number of projects quota by default you got: - 10 projects and per project - 100 MB per SVN - 100 MB per download to fill up 100MB on the SVN is not that easy ideally you would want to have only source code, no zip, or binaries etc. just saying don't think it is a good way to archive your FLAs but if you stick on code all should be ok. > As > for eventually migrating from google code, I remember reading that for now, > you just can do a check out of a revision, but not getting your > whole repo (I might be wrong, I've just taken a glance at the faqs and can't > find info about this). > you have svnsync and you get your whole revisions, it is not exactly a dump of the repository but it is almost the same. from the top of my head $svnadmin create /backup/myproject $svnsync http://myproject.googlecodecom/svn /backup/myproject just be carefull if you want your backup as mirror and keep using the google repos as your main repos for commit (look the svn redbook doc) > Anyway, I've been using google code to host some 4 or 5 projects, and I have > to say that I'm mostly happy with it. It's a good service, it's free > and some of those limitations may get worked out with the time. The only > real problem I see is that you can't export your repository (which I > remember reading somewhere, but I'm not sure now if it still true...) > http://svnbook.red-bean.com/en/1.4/svn.reposadmin.maint.html#svn.reposadmin.maint.backup "The svnsync program (see the section called "Repository Replication") actually provides a rather handy middle-ground approach. If you are regularly synchronizing a read-only mirror with your main repository, then in a pinch, your read-only mirror is probably a good candidate for replacing that main repository if it falls over. The primary disadvantage of this method is that only the versioned repository data gets synchronized—repository configuration files, user-specified repository path locks, and other items which might live in the physical repository directory but not inside the repository's virtual versioned filesystem are not handled by svnsync." amd al is explained here http://svnbook.red-bean.com/en/1.4/svn.reposadmin.maint.html#svn.reposadmin.maint.replication they say "Do not modify the mirror" etc. but this is only for people that want to mirror their repo, if you want to do a direct copy, ditch the old repo and use the new one, it work perfectly. cheers, zwetan _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
