On Wed, Aug 8, 2012 at 12:14 PM, Nicholas Kwiatkowski <nicho...@spoon.as>wrote:

> Om,
>
> I was working on this early last week (sorry I haven't touched it in the
> last week -- I've had a few personal things I had to take care of this
> week), and I was getting the same thing.  It has something to do with the
> way the CMS is transferring the content to the production server.
>

Yes, I see that the html file I added with just " [preferred] " in it has
been padded with the standard template html around it.

>
> I do know that the CGI has to be in the CGI folder, and given run
> permissions.


If you look at the page:
http://incubator.apache.org/flex/single-mirror-url.cgi, we do get the
single preferred mirror url in the content section.  It looks like the cgi
is running fine inside of /flex/content/ itself.

When I put the single-mirror-url.cgi and single-mirror-url.html files
inside of the cgi-bin folder, it caused build errors. I might have done
something wrong as well.


> I'm assuming infra does this for us (the permissions part),
> but I'm not sure.  I hopefully will be able to dive into it again tomorrow.
>

I would like to shadow you when you do these things.  It will be good for
me to learn how these things work.

Thanks,
Om


> -Nick
>
> On Wed, Aug 8, 2012 at 3:00 PM, Om <bigosma...@gmail.com> wrote:
>
> > That url should be up now.
> >
> > Om
> >
> > On Tue, Aug 7, 2012 at 11:48 PM, Erik de Bruin <e...@ixsoftware.nl>
> wrote:
> >
> > > Om,
> > >
> > > > http://incubator.apache.org/flex/single-mirror-url.html is there as
> > > well,
> > > > but is showing only the word [preferred].  What am I doing wrong?
> > >
> > > I don't see anything at that URL... I get a 404 (Not Found) message.
> > >
> > > EdB
> > >
> > >
> > >
> > > --
> > > Ix Multimedia Software
> > >
> > > Jan Luykenstraat 27
> > > 3521 VB Utrecht
> > >
> > > T. 06-51952295
> > > I. www.ixsoftware.nl
> > >
> > >
> > >
> > > P.S. I would like everybody to know that as of this morning I broke my
> > > personal record for days lived.
> > >
> >
>

Reply via email to