gwtproject.org site

[Manuel Carrasco Moñino]

Hello all.

Due to changes in the GAE java Remote API, the uploader tool that we have to update the gwtproject.org site is not working anymore.

Julien has updated last changes by hand (thanks Julien), but this is a tough task and we should fix the issue.

Although I can take the time to fix the tool, I think it's time to propose different options that make the deploy process simpler.

The system we have right now comes from the ages when GAE was almost the only option in google infra to deploy web sites. We are storing static data in the DataStore, and it is served by a dedicated servlet, using custom code to index the site using  key values.

Since all the data we serve from gwtproject.org are static files, I would propose to use either Google Cloud Storage or Compute Engine services. 

- Cloud Storage makes easy and fast deploy and serve static content.

- Compute Engine needs more setup, but it's more versatile in the sense that we can deploy demo web apps running anything in server side. Also we already have an instance where we run the CI.

More options? thoughts?

- Manolo

[Jens]

Why don't we use Github pages with custom domain? Never looked into the code, does the servlet anything special?

-- J.

[Manuel Carrasco Moñino]

Nothing special, it gets the resource based in the pathinfo, decode it to utf-8, computes the content-type based on the extension, and writes the answer to the client.

It is not storing any info in database, because we use google analytics for counting visits. The GA script is statically included in any page the servlet does not rewrite anything.

El vie., 29 jul. 2016 a las 13:21, Jens (<jens.ne...@gmail.com>) escribió:

Why don't we use Github pages with custom domain? Never looked into the code, does the servlet anything special?

-- J.

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/ba7d3311-fb22-4729-a704-251dd49e4702%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Manuel Carrasco Moñino]

About github pages with custom domains, the only minor I see is that it does not supports https, but currently our site is not https enabled, so not a big deal in the short time.

[Jens]

About github pages with custom domains, the only minor I see is that it does not supports https, but currently our site is not https enabled, so not a big deal in the short time.

Yes but its possible to put cloudflare.com in front of it to get free SSL on the domain. I have done that for my domain. You would use a CNAME from domain.tld  -> account.github.io and choose full SSL in cloudflare. Then you have SSL between browser <-> cloudflare using the cloudflare cert and SSL between cloudflare <-> github using the github cert. Its not fully end-to-end encrypted but IMHO good enough.

But Github has some limits:

• GitHub Pages source repositories have a recommended limit of 1GB .
  
• Published GitHub Pages sites have a 1GB recommended limit.
  
• GitHub Pages sites have a recommended bandwidth limit of 100GB or 100,000 requests per month.
  
• GitHub Pages sites have a recommended limit of 10 builds per hour.
  

-- J.

[Andreas Ofner]

Hi Manuel,

Am Freitag, 29. Juli 2016 13:47:43 UTC+2 schrieb Manuel Carrasco Moñino:

About github pages with custom domains, the only minor I see is that it does not supports https, but currently our site is not https enabled, so not a big deal in the short time.

GitHub recently announced official https support. See https://github.com/blog/2186-https-for-github-pages

[Thomas Broyer]

Only for *.github.io, not with custom domains.

[JonL]

If everything is static pages, what about firebase?