I don't understand why Apple doesn't give Ipad pro users an option similar to Samsung Dex. There seems to be an aversion to enabling MacOS on touch devices.
Anyway enough with my rambling, the author seems pleased with his setup so it is what it is.
3,101 karma · joined April 24, 2013
bits & bobs: https://github.com/johnwilson
I don't understand why Apple doesn't give Ipad pro users an option similar to Samsung Dex. There seems to be an aversion to enabling MacOS on touch devices.
Anyway enough with my rambling, the author seems pleased with his setup so it is what it is.
But funny enough I'm able to put up with these little inconveniences because after all it's a free OS. I find myself to be much more tolerant than when I was using MacOS and my macbook pro. Between the dead keys, apple tax, dongle life and the OS quirks ...
Last I checked, converting Javascript charts to PNG is still a hacky/convoluted process.
Which is a bit ironic considering Musk himself was born in South Africa.
In fact, based on the initial footage from Wuhan, countries should have adopted more stringent protocols when they repatriated their nationals, i.e. quarantine on arrival etc... If in doubt throw everything including the kitchen sink at just to be sure. But it is what it is. I just hope we've learnt from this and are prepared for the next one.
1) find out if the runtime/framework is supported but Heroku or if there are any buildpacks available.
2) spin up a Dokku instance using Vagrant for local development and testing
3) deploy to a live Dokku server
If/when I encounter any issues I add Heroku or Dokku to my search query and 9 times out of 10 I’ll find an answer to my issue. Else I just dig into the Dokku docs and GitHub issues and figure it out.
So for instance googling for deploying a Phoenix app with Dokku results in a few hits such as this one [0].
There's also a lovely UI for Dokku being actively developed: Ledokku [1]
The only drawback currently is when you want to horizontally scale your deployment. You can use their kubernetes or nomad schedulers but I think those are an overkill in terms of complexity. You could also use a load balancer in front of multiple Dokku instances but you then lose the ease of deployment, configuration, etc…
Which is why I think their docker swarm scheduler [2] will be one of the most important feature they could add. It’s currently on the roadmap but I’m sure with a bit of sponsorship and a few pull/merge requests it will become a reality.
[0] https://nithinbekal.com/posts/dokku-phoenix-deploy/
Currently, if you want to scale Dokku horizontally and aren’t ready to take the kubernetes plunge, you have to put a load balancer in front of your multiple VMs running Dokku and that comes with it’s own headaches.
Scott Hanselman has a couple of guides on his blog on how to get it up and running.
[0] https://web.archive.org/web/20210528215643/https://www.unice...
Now as to the question of what success is...
import sys
from django.conf import settings
settings.configure(
DEBUG=True,
SECRET_KEY='thisisthesecretkey',
ROOT_URLCONF=__name__,
MIDDLEWARE_CLASSES=(
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
),
)
from django.conf.urls import url
from django.http import HttpResponse
def index(request):
return HttpResponse('Hello World')
urlpatterns = (
url(r'^$', index),
)
if __name__ == "__main__":
from django.core.management import execute_from_command_line
execute_from_command_line(sys.argv)
Granted, it's not as terse as Flask's hello world example but it's still quite short.[0] https://www.oreilly.com/library/view/lightweight-django/9781...
A nice blog to also include in your django learning resources bookmarks is Simple is Better than Complex [1].