IMHO the sooner the better, for Sage's trac is basically not working now...
Dima
--
---
You received this message because you are subscribed to the Google Groups "sagemath-admins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sagemath-admi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Trac detected an internal error:There was an internal error in Trac. It is recommended that you notify your local Trac administrator with the information needed to reproduce the issue.
The action that triggered the error was:
GET: /ticket/20769
On Sat, Jun 18, 2016 at 10:34:03AM -0700, William Stein wrote:
> Hi,
>
> (1) It is now newly possible for either me or Harald Schilly to do
> anything related to the *.sagemath.org DNS setup.
>
> (2) Mike Hansen is currently looking into migrating wiki.sagemath.org
> to the same Google compute engine project...
I guess it is needless to recall from a previous email that:
- all the archeological work is already done,
- config files are cleaned up,
- sysadmin choices (webserver, firewall,...) are compatible with asksage ones
for better cooperation with the collective which is daily working in
maintainig it,
- everythging is documented, so that any kind of migration or upgrade should
take less than 5 minutes (+ download time).
On Sun, Jun 19, 2016 at 4:09 AM, mmarco <mma...@unizar.es> wrote:
> Did you recently enable cloudflare cache services?
>
> I am using Tor to circunvent some pesky firewall, and when trying to push
> some changes, I get some git_trac.trac_error.TracConnectionError: Forbidden
> error.
>
> Would it be possible to disable cloudflare? Or at least, to use the option
> to not blacklist Tor exit nodes, please?
As far as I can tell I have now disabled cloudflare for everything
trac related. Does this help? Cloudflare is doing nothing but DNS.
trac.sagemath.org is currently 128.208.160.253
-- William
On Jun 18, 2016 10:37 PM, "William Stein" <wst...@gmail.com> wrote:
>
>
>
> On Saturday, June 18, 2016, Thierry <sage-goo...@lma.metelu.net> wrote:
>>
>> On Sat, Jun 18, 2016 at 10:34:03AM -0700, William Stein wrote:
>> > Hi,
>> >
>> > (1) It is now newly possible for either me or Harald Schilly to do
>> > anything related to the *.sagemath.org DNS setup.
>> >
>> > (2) Mike Hansen is currently looking into migrating wiki.sagemath.org
>> > to the same Google compute engine project...
>>
>> I guess it is needless to recall from a previous email that:
>>
>> - all the archeological work is already done,
>> - config files are cleaned up,
>> - sysadmin choices (webserver, firewall,...) are compatible with asksage ones
>> for better cooperation with the collective which is daily working in
>> maintainig it,
>> - everythging is documented, so that any kind of migration or upgrade should
>> take less than 5 minutes (+ download time).
>
>
>
> I didn't realize all of the above was posted publicly somewhere. Can you please repost the link and save us some time. Thanks!
I second that. Where us all of this documented?
I would like to also reiterate my suggestion for an "infrastructure" repository to track configuration files and documentation concerning Sage infrastructure. Currently there are several such repositories for bits and pieces of it spread around random places, with none of it at all comprehensive or documented.
In the process of rebuilding the trac/git server I started such a repository privately, but need some place to put it online where others can access it. That said I still think it should be private. This would be a necessary first step, IMO, to making better use of CM tools (chef/ansible/salt/etc.) to make this more sane in the future.
Would GitHub be a good place to put such a repository? Bitbucket? Anywhere as long as it's private and not actually on any of Sage's infrastructure itself. It would be great to get Thierry's documentation of ask and wiki integrated as well.
Best,
Erik
P.s. Let's please keep the person barbs out of this discussion or literally nothing will be accomplished.
Mostly the latter.
I would like to understand what is currently the problem with trac/git in case it impacts the new server. But I suspect it's something in between the client and our apache server, such as a misconfigured proxy.