Re: [ML] Re: Hosting of gnustep.org

[Ivan Vučica]

On Tue, Jan 19, 2021 at 7:18 AM H. Nikolaus Schaller <hns@goldelico.com> wrote:
>
>
> > Am 19.01.2021 um 00:36 schrieb Ivan Vučica <ivan@vucica.net>:
> >
> > Some options:
> >
> > - Should we turn the index into a set of static pages generated from
> > MySQL data, which we then check in?
> > - If we turn each entry into a single .md file, we can perhaps
> > leverage https://github.com/allejo/jekyll-toc
>
> Hm.
>
> The page is highly interactive (searching/filtering/jumping) and accepts
> proposing updates. It is even counting access and building a TOP10 list.
>
> How should that work with static content?

Hypothetically speaking, as I don't want to put that much effort and
I'd rather let it run as-is:

As we stand, there aren't so many items. The list of them can be
fetched all at once, and filtered/searched client-side, if we need
that.

Top 10 is, obviously, not doable. However, I missed that it's based on
an access metric; I thought it was simply the 'last 10'.

Interestingly, we have plenty of pages that are making outgoing
requests and failing; for instance, the number 1 on top 10:
http://www.gnustep.org/softwareindex/showdetail.php?app=61

Should we rethink the index?

>
> > - We could have a tiny nginx host which does nothing but route
> > requests to serving backends based on the path:
> >  - either proxy the request to gnustep.github.io,
> >  - or proxy it to a host with the software index (or even return a
> > 301 to something like index.gnustep.org)
>
> Keep it simple...
>
> Why not just redirect the entry point www.gnustep.org/index.html to
> the new page and leave the remainder like the softwareindex on the
> existing infrastructure (apache, php, mysql)?
>
> This should suffice
>
> www.gnustep.org/index.html;
>
> <meta http-equiv = "refresh" content = "0 ; url = 
> https://gnustep.github.io/index.html"/>

Because this situation relegates the "main site" to a secondary URL,
permanently. I've done that before and I regret it. And it prevents us
from even attempting to preserve location of other URLs which would be
completely fine as static pages. (Search engines will eventually index
gnustep.github.io as the sole main site. But right now it's not even
on the first page of results on three major search engines I tested
on.)

>
>
> >
> > I can play with moving things around over some weekend, if I get
> > sufficient access to current host.
> >
> >
> > On Mon, Jan 18, 2021 at 6:03 PM H. Nikolaus Schaller <hns@goldelico.com> 
> > wrote:
> >>
> >> Hi,
> >> I just recognized that making gnustep.org point somewhere else will break
> >>
> >> http://www.gnustep.org/softwareindex/
> >>
> >> unless this is moved as well.
> >> It is long ago that someone did set this up and it still works...
> >>
> >> The Software Index needs php, a httpd and a mysql database to be hosted 
> >> somewhere. I am not sure if gnustep.github.io can provide this.
> >>
> >> BR,
> >> Nikolaus
> >>
> >>> Am 18.01.2021 um 18:26 schrieb Patryk Laurent <plaurent@me.com>:
> >>>
> >>> Hi Greg,
> >>>
> >>> Could we make a plan to implement pointing the domain to the Gitub-hosted 
> >>> site and/or delegate someone to do it?
> >>>
> >>> Aside from the navigation menu improvements already committed on the 
> >>> GitHub version of the site, we could also incorporate or link to sites to 
> >>> increase visibility e.g., https://teespring.com/stores/gnustep
> >>>
> >>> Best regards,
> >>> Patryk
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>> On Dec 18, 2019, at 13:01, Ivan Vučica <ivan@vucica.net> wrote:
> >>>>
> >>>> On Wed, Dec 18, 2019 at 1:17 PM Manuel Guesdon <ml@sbuilders.com> wrote:
> >>>>>
> >>>>> - make a CNAME www.gnustep.org => gnustep.github.io (but server hosting
> >>>>>  gnustep.github.io should accept requests for www.gnustep.org)
> >>>>
> >>>> This merely requires creating a file named 'CNAME' in the github repo
> >>>> for gnustep.github.io (i.e.
> >>>> https://github.com/gnustep/gnustep.github.io).
> >>>>
> >>>> See 
> >>>> https://help.github.com/en/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site
> >>>>
> >>>>> I can't make a CNAME gnustep.org => gnustep.github.io (due to the way 
> >>>>> DNS
> >>>>> works) but I can make a 301 redirect http://gnustep.org
> >>>>> => http://www.gnustep.org
> >>>>
> >>>> Looks like Github documents the exact IPs that can be used:
> >>>> https://help.github.com/en/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain
> >>>>
> >>>> Then again, 301 + CNAME for www are probably more maintainable.
> >>
> >>
>