I had this recently happen as well. I always go through namecheap and use their (now free) privacy offering, yet from one of my domains (a .digital) I received lots of spam calls from Indian dev shops offering their services. Thankfully it only lasted a few days.
Hey, I created this simple project/guide for a use case I had. I figured it would be a good opportunity to demonstrate a basic infrastructure-as-code project that others might also find helpful.
My use case was to create a bastion host, or an environment on the edge of my homelab, which is the only ingress point from the outside web.
It might be worthwhile to use a library like Flask which has less batteries included. This will force you to figure out which pieces of the puzzle you are missing and will (hopefully) allow you to learn a lot through exploration.
Once you understand what everything is doing, going back to Django, you should understand what all of the components are doing.
Django & Flask are not exactly one-to-one with the way they handle a lot of things, but I think it would still be a useful exercise.
Maybe I'm just wearing a foil-helmet, but the presence of a front-facing camera on an always-on device is concerning to me when there is no real good reason to have it.
Maybe I am biased, but I agree with the other user on here that Ansible is a good solution for keeping the environments the same.
However, if you're feeling brave, you should definitely check out OpenShift (community version at http://openshift.org). OpenShift is basically Kubernetes with a bunch of cool stuff added, one especially useful feature is source-to-image.
It pulls your code from a scm repo and finds a builder image (or you can choose one) and it will build the docker image for you. You can have it pull whenever there is new code and rebuild the image and deploy if you want.
On top of that you get lots of cool docker orchestration features.
Do you have any book recommendations for these techniques? I tried the "memory palace" or the method of loci and had a small degree of success, but never found it practical. I'd love to give it another go though.
This is tangential to your point about remaining on this planet, but it is much easier to survive on our planet, polluted or not, than it is to setup shop on a different planet.
I am fully in agreement with your view on how messed up things are on our planet due to human action. I just felt compelled to point out that any adjustments to be made on other planets can be done here. Can't breath on mars? Build a dome and generate air into it. The same thing could be done on Earth if the situation was bad enough. Can't survive on the surface of Venus due to hot and thick atmosphere? Live floating in the clouds. We could do the same on Earth.
The process of getting to another planet is so infeasible at this point and probably will be for a long time yet. We can hope, but I like to play devil's advocate. Also, Human's are very good at adapting and I'm sure the will to survive will keep our species alive even if pollution degrades our environment to the point of toxicity.
This is too true. Best is when the opinions on these are formed with no previous experience with it. I have to use Perl at work and whenever someone finds out they say "I'm sorry that you have to use that terrible language!" Sure, I would prefer to use Python, but Perl has some useful features that other languages don't do as well which is why I use it. Conveniently, nobody who comments to me about Perl has ever actually used it. Same with when I have used Java in the past.
If anyone is interested in some more drone chainsaw action, they should check out when Jamie from Mythbusters attempted to make one of these: https://www.youtube.com/watch?v=1fe9IDx3vCs
He was unable to get it to work effectively or safely, though his drone was not as heavy-duty as the one from this thread.
[1] https://github.com/crazy-max/docker-matomo