HACS works in a container, or is there specific functionality of it that doesn't work? I've been using it inside a Docker HA container on a Pi without issue.
92 karma · joined October 12, 2010
> Of course I'd like a static website for deploying, but I'd love a web gui which acts as a frontend for such generators.
If you want such a gui on your local machine you're not much more than a few commands away
npm i -g ghost-cli
ghost install localhttps://ghost.org/docs/api/v2/gatsby/
In the meantime, Discourse[1] and Talk[2] are great options that can be self-hosted if needed and integrate well. If you look at them you can see the level of effort that is required to do commenting, moderation, and spam protection well at scale.
[0] https://forum.ghost.org/t/memberships-subscriptions/377 [1] https://www.discourse.org [2] https://coralproject.net/talk/
Upgrades are painless, typically requiring around an hour at most. If there are bigger framework changes we can usually upgrade immediately then clean up deprecations later as necessary but even then the work is normally minimal. When there are more stylistic changes that touch many files it's usually very quick work thanks to the codemods that are released alongside. All of this despite huge and continuous under-the-hood improvements in Ember since we've been using it.
Compared to what I've seen in other frameworks I think we've benefitted a lot in being able to spend pretty much zero time bike shedding which libraries will make up our core framework. We also save a lot of time not needing to upgrade disparate parts of a custom framework built of 3rd party libraries that aren't necessarily in sync with each other. The Ember addon ecosystem has also been stellar, with common solutions rallied around by the community such that they are usually as stable as core and kept up-to-date with the latest idioms without breaking backwards compatibility.
In conclusion Ember has allowed us to focus almost entirely on product rather than framework. It stays out of the way and provides very clear happy paths for typical workflows whilst allowing us to break out of those where needed without sacrificing any tooling or upgradability.
As for the downsides I think the biggest has been the limited pool of contributors. A lot of react bandwagon jumping has happened since we started with Ember and it's interesting when talking to other developers outside of the Ember ecosystem because there's a lot of historical and outdated views about what Ember is and isn't. The Ember core team and community is working hard to improve Ember's marketing message to counter that but it's tough to break through when the framework's core selling point is consistency through hype cycles.
> Our plans are limited by how many readers you have, and how often they visit your publication. We only enforce these limits on a 3 month rolling average, so we'll never make you upgrade plans if you happen to have one big traffic spike or particularly successful month.
> This means people will rather publish their blogs on sites like medium.com rather than running their own wordpress server, or even a ghost blog.
I think we'll just see an evolution of the tools available. For example, Ghost's CLI install already sets up letsencrypt for you along with auto-renew of certificates, anyone using that or the 1-click DigitalOcean droplet will get HTTPS with no extra setup difficulty compared to a non-HTTPS version.
Have you seen the Sony Digital Paper System[0]? It seems to fit the bill perfectly but the price point high.
[0]: http://pro.sony.com/bbsc/ssr/product-DPTS1/?PID=I:digitalpap...
I'd have to say the Discourse project (http://discourse.org) provides a fantastic counter example to this. It shows what can be achieved when SPAs embrace the URL and a lot of thought is put into how the modern browser features can be used to improve the user experience rather than just jumping on the bandwagon.
Example forums:
http://meta.discourse.org http://discuss.atom.io http://discuss.emberjs.org
[0]: http://emberjs.com/api/data/classes/DS.EmbeddedRecordsMixin....
On the iPad you also get more control over viewing angles, I was surprised that you lose that on the desktop.
- inventory is limited? which amazon website are you visiting?
Running on a retina MBP, both Safari and Chrome render the text pin-sharp with no noticeable aliasing.
That's what happens by default when using the asset pipeline when in the "development" environment, it's supposed to ease debugging and works well when only including a few JS files. In "production" all the files would be merged into 1.
There is a flag "config.assets.debug = true" in the "development.rb" file, switching that to "false" will output just one file.
Akamai's stats show a very different story - http://blog.cloudfour.com/explaining-the-ios-and-android-mob...
Mobile browser share
Safari: 66.2%
Android: 19.4%
iOS: 65.7%
Android: 20.2%A huge swathe of the south east has no aerial photography whatsoever beyond a satellite level where contrails are clearly visible.
I tried requesting a route from my current location to a nearby train station and it gave me a route to a random pub in the next town over - this was for a search term that worked reliably in the old maps app.
Maps themselves show much less information than the equivalent google maps view. There's a fraction of the POI's available and those that are available are often 100m+ off from their actual location.