Simon

Results 215 comments of Simon

The capture view is now updated with Tachyons, see https://github.com/dwyl/elm-pwa-example/commit/e6c1dba06df1f29b4e2e55e2855dfa2de1c94b1f

We might need to update the buildback config: https://github.com/dwyl/dwylbot/blob/master/elixir_buildpack.config see: - https://hexdocs.pm/phoenix/heroku.html - https://github.com/HashNuke/heroku-buildpack-elixir

Looking at how to setup Github pages for PWA https://gist.github.com/kosamari/7c5d1e8449b2fbc97d372675f16b566e

Better now! ![image](https://user-images.githubusercontent.com/6057298/71010904-71142780-20e4-11ea-83ee-98ff3fc6cb8a.png) The main issue was the trailing "/" in the start_url. The link above was useful @nelsonic yes I think the next step might be to try with...

The app is now reloading offline: ![image](https://user-images.githubusercontent.com/6057298/71011186-e3850780-20e4-11ea-8d81-dee9e0cba31b.png) https://dwyl.github.io/elm-pwa-example/

Now that the application is hosted on Heroku it is simpler to debug and add changes (see #3) Running an audit on the heroku application returned the following error for...

The only PWA remaining warning from the audit is the redirect to https: ![image](https://user-images.githubusercontent.com/6057298/71907322-b071e900-3163-11ea-9459-547b29320ace.png=500x800) We might need a more customisable backend server, however for testing the pwa app http-server is...

Using Nginx instead of the npm http-server allow us to configure the server, see https://github.com/dwyl/elm-pwa-example/issues/3#issuecomment-571941816 It is really quick to deploy on Heroku and we have now all the PWA...

@iteles yes sorry. It took me a while to try to find a good way to describe with test the rule, and just seeing that Github provide an easy way...

This has also happened on [LDMW]( https://github.com/LDMW/cms/pull/47#issuecomment-310384792)