From: David G. <go...@py...> - 2008-11-25 20:06:45
|
It looks like SourceForge has re-enabled their shell service, details below. Should we use it, or stick to the local-build plan for website updates? -- David On Tue, Nov 25, 2008 at 23:00, SourceForge.net Team <no...@so...> wrote: > 5. INTERACTIVE SHELL SERVICE > > shell.sourceforge.net -- most SourceForge.net developers have used our old > shell service at one time or another. The old shell service was prone to > failure and abuse; it was part of the original SourceForge.net service > offering and really had not evolved much over the years. With our > datacenter migration wrapping-up at the end of the September, we set our > sights on replacing the old shell service with a much more sustainable, > open, and useful service. > > We launched our new interactive shell service at the end of last month, and > have launched a series of improvements earlier this month. Our new shell > service is built for improved resilience and performance, permits a much > broader range of access, and applies a more reasonable set of restrictions > than our past shell offering (namely, we limit your data access to the data > for your own projects). > > This also marks the first time that we have implemented a "built to suit" > feature -- we included the functionality that the majority of our users > requested in a survey we ran. Feedback since launch has been very > positive, and we (like our end-users) are pleased with the reliability and > new options that our new shell service provides. > > For more information: > * Interactive shell service: > https://sourceforge.net/community/forum/topic.php?id=3953&page&replies=1 |
From: Guenter M. <mi...@us...> - 2008-11-26 08:54:20
|
David Goodger <go...@py...> schrieb: > It looks like SourceForge has re-enabled their shell service, details > below. Should we use it, or stick to the local-build plan for website > updates? Would this allow to safely rsync between berlios.de and SF? I have no preference as there are pros and cons for either approach. My problem is that currently files that are (re)moved in the SVN are not (re)moved in the web space. The "local-build and rsync" could complicate things further: after a boring and tedious cleaning of docutils.sf.net, rsync from a local mirror might bring back all the obsolete files. Günter |
From: David G. <go...@py...> - 2008-11-26 14:51:26
|
On Wed, Nov 26, 2008 at 03:54, Guenter Milde <mi...@us...> wrote: > David Goodger <go...@py...> schrieb: >> It looks like SourceForge has re-enabled their shell service, details >> below. Should we use it, or stick to the local-build plan for website >> updates? > > Would this allow to safely rsync between berlios.de and SF? Maybe, I haven't checked. I'm inclined to abandon that approach though. > I have no preference as there are pros and cons for either approach. > > My problem is that > > currently files that are (re)moved in the SVN are not (re)moved in the > web space. > > The "local-build and rsync" could complicate things further: > > after a boring and tedious cleaning of docutils.sf.net, rsync from a > local mirror might bring back all the obsolete files. I don't see how that would be any worse on a local build than on a remote server. It's not that big of a problem IMO. Can you explain further? -- David Goodger <http://python.net/~goodger> |
From: Guenter M. <mi...@us...> - 2008-11-27 08:33:30
|
David Goodger <go...@py...> schrieb: > On Wed, Nov 26, 2008 at 03:54, Guenter Milde <mi...@us...> wrote: >> currently files that are (re)moved in the SVN are not (re)moved in the >> web space. >> The "local-build and rsync" could complicate things further: >> after a boring and tedious cleaning of docutils.sf.net, rsync from a >> local mirror might bring back all the obsolete files. > I don't see how that would be any worse on a local build than on a > remote server. > It's not that big of a problem IMO. Can you explain > further? With the remote server, I had to do the cleaning 3 times (locally|SVN, berlios/aux and SF). With local updates, files I remove from SF remain on the local contributors machines and will be restored with the next rsync (if no special care is taken). Günter |