On Sat, 2016-12-17 at 16:11 +0000, Ian Clarke wrote: > Weren't we going to host on AWS?
I don't know, that's why I am asking...
I have suggested either hugo or pelican with AWS lambda (for a
completely serverless, trendy infrastructure)
OR
using github-pages (with jekyll) and putting some CDN in front
(cloudflare, cloudfront, whatever)
I have not offered to help maintain something ruby based.
> What is the problem with maintaining a Ruby stack exactly? Isn't it
> just a question of installing whatever is required for Jekyll and
> perhaps upgrading it once in a blue moon? Isn't it just a question
> of:
> $ sudo apt get install rubygems$ gem install jekyll bundler
> And then periodically upgrading?
>
I wish it was that simple. AWS lambda doesn't support ruby as runtime...
so you have to ship/maintain your own... and write the glue code in any
of the languages that are supported (java, c#, node, python). You get
billed when your code runs... so the naive approach of doing what you've
described above can turn out to be bloody expensive (network round-trip
to debian mirrors, then to gem, then to bundler, ...)
At the end of the day, I don't care... I've said it in the past; we are
picking the worst and most convoluted solution possible. I've been
ignored and can live with it; just don't count on me to make it happen.
Florent
>
> On Sat, Dec 17, 2016 5:23 AM, Florent Daigniere nextgens@freenetprojec
> t.org
> wrote:
> So what is the plan for hosting if github pages can't do it?
>
>
>
>
> As I wrote before, expecting release managers to maintain a ruby stack
>
> (on top of the existing java/python one) is a no-go.
>
>
>
>
> Florent
>
>
>
>
> On Sat, 2016-12-17 at 01:27 -0800, Dan Roberts wrote:
>
> > Hi Folks,
> >
> > Status update. The simple jekyll plugin I wrote works, with a
> > couple of known issues. It will allow us to use our existing
> > transifex
> > translations unmodified (something I don't think we were going to
> > get
> > out-of-the-box anywhere). It depends on the ruby gettext gem. The
> > site
> > still needs some massaging to match the transifex strings, but you
> > can
> > see the translation work for parts of /about.de/ which is
> > automatically generated by the plugin. For each locales/${LOCALE}.po
> > there will be a ${PAGE}.${LOCALE} file generated.
> >
> > Tomorrow (saturday 12-17) I'm going to fix the known issues with the
> > plugin, and QA the translation tags to ensure our translation keys
> > match what is already translated (I may consider automating it using
> > the existing site generator, we'll see how obnoxious it gets). I'll
> > also be implementing a language selector UI.
> >
> > The source code is at https://github.com/Ademan-laptop/freenet-websi
> > te
> > -redesign though beware the history is ugly, I will be cleaning it
> > at
> > some point, but I wanted to be sure to update before the weekend.
> > Obviously with the plugin dependency it is no longer viewable on
> > github.
> >
> > Thanks,
> > Dan
> >
> > On Sat, Dec 10, 2016 at 1:32 PM, Dan Roberts <ademan...@gmail.com>
> > wrote:
> > > I gave a few updates on IRC but I apologize for not updating the
> > > ML,
> > > I didn't foresee how long I would be stalled. I've had some
> > > personal
> > > issues going on which ate not only my weekends but several work
> > > days
> > > of both last week and this week. I don't expect to lose any more
> > > time from the aforementioned issues but it's not impossible.
> > >
> > > I intend to finish the Jekyll plugin this afternoon so that we can
> > > use existing translations, the proof of concept from the other
> > > weekend worked well. After that we can stand it up somewhere for
> > > QA.
> > > I do need to add a language selector, that is not present in the
> > > design we bought so I'll use my best judgement and we'll move it
> > > later.
> > >
> > > Thanks,
> > > Dan
> > >
> > > On Sat, Dec 10, 2016 at 11:18 AM, Ian Clarke <ian@freenetproject.o
> > > rg
> > > > wrote:
> > > >
> > > > On Sat, Dec 10, 2016 at 9:51 AM, Florent Daigniere <nextgens@fre
> > > > en
> > > > etproject.org> wrote:
> > > > > On Sat, 2016-12-10 at 13:40 +0000, Ian Clarke wrote:
> > > > > > Hey guys, it's been quite a while at this point, and we're
> > > > > still
> > > > > > stuck with the old website.
> > > > > > What's the current status of getting the new site up?
> > > > >
> > > > > I can't make any progress until there is something to
> > > > > deploy...
> > > > > I
> > > > > haven't heard from Dan.
> > > >
> > > > That's worrying...
> > > >
> > > > > > If necessary we should spend some more of our donation to
> > > > > > make
> > > > > this
> > > > > > happen (we've already invested in getting the original
> > > > > > design
> > > > > done,
> > > > > > and yet we've received no benefit from it yet).
> > > > > >
> > > > >
> > > > > Agreed; a big piece of it is the content re-design (for which
> > > > > I
> > > > > haven't
> > > > > seen any plan).
> > > >
> > > > We start by categorizing our different audiences, I think this
> > > > has
> > > > been discussed. Users, donors, and developers are the major
> > > > categories IIRC. IMHO the website should focus on the first
> > > > two,
> > > > and this will probably require a limited amount of content. For
> > > > developers a companion wiki is probably the best approach.
> > > >
> > > > Ian.
> > > >
> > > > --
> > > > Ian Clarke
> > > > Founder, The Freenet Project
> > > > Email: i...@freenetproject.org
> > > >
> > >
> > >
> >
> > _______________________________________________
>
> Devl mailing list
>
> Devl@freenetproject.org
>
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>
>
> Ian Clarke
> Founder, The Freenet Project
> Email: i...@freenetproject.org
> _______________________________________________
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
