discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Umberto Cerrato
Subject: Re: [ML] Re: Hosting of gnustep.org
Date: Tue, 19 Jan 2021 11:30:29 +0000

(Hi there, I am quite new here, I am sorry for interfering here, I wanted to.)

Is that really necessary?

I do not know how much GNUstep is “libre”.
But usually, I would tend to stay out of big company platforms (f.e. Amazon)
Making an exception only on some (like GitHub).

Theoretically (but that is a very personal opinion), to me the best platform
would be a self hosted one. Relying on other(s) services the least possible.

PS:
To me, these are tough choices.
Eventually, I think the only thing GNUstep may need is just an aesthetic 
restyling.

I have something more to say, But I think I am just going to copy-paste that to 
the IRC channel
If you want to hear them.

> Il giorno 19 gen 2021, alle ore 11:35, Gregory Casamento 
> <greg.casamento@gmail.com> ha scritto:
> 
> Nikolaus,
> 
> On Tue, Jan 19, 2021 at 2: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?
> 
> > - 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)?
> 
> The idea is to get off of the existing server.  I really would like to move 
> to something hosted on github or on some other server that we push changes to 
> more easily.
> 
> This should suffice
> 
> www.gnustep.org/index.html;
> 
> <meta http-equiv = "refresh" content = "0 ; url = 
> https://gnustep.github.io/index.html"/>
> 
> 
> > 
> > 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.
> >> 
> >> 
> 
> 
> 
> 
> -- 
> Gregory Casamento
> GNUstep Lead Developer / OLC, Principal Consultant
> http://www.gnustep.org - http://heronsperch.blogspot.com
> https://www.patreon.com/bePatron?u=352392 - Become a Patron
> https://gf.me/u/x8m3sx - My GNUstep GoFundMe
> https://teespring.com/stores/gnustep - Store


reply via email to

[Prev in Thread] Current Thread [Next in Thread]