I've been playing with Matomo recently and opted to use a premade container [1] for it and that was working pretty well.

[1] https://github.com/crazy-max/docker-matomo

I don't know if starting a rice farm is a feasible way to pay off student loans or mortgages for most people.

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.

Thanks Idonley. I have heard that flask is easier. At this point I feel too deep into Django to give up. However, picking up some flask stuff on the side could be worthwhile. Would certainly broaden my understanding of it all.

I would second this advice. Flask is structured much more intuitively than Django. The first time I tried Flask after Django everything just clicked into place immediately.

I would agree too. Flask will help you understand the basic web framework and will give you confidence. In the past I often used django but once I worked with flask I never looked back.

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.

Tape is cheap.

Not buying is even cheaper.

Tell that to the half-dozen microphones you probably have within earshot.

Tampering with devices you own is already a crime in some circumstances. I'm sure they can extend it to these.

It looks like this is the GitHub for the project: https://github.com/oxalorg/stagit

Actually http://git.2f30.org/stagit/ is the real host, what you linked was just a mirror. If you go up one level on the site, you can find a list of projects hosted by the 2f30 team, including stagit, which was made by Hiltjo Posthuma (one of the Suckless guys, iirk)

I'd just go on Amazon and find some cheapo phone like the BLU R1 HD. Just find one that is compatible with your provider.

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.

Check out books of Tony Buzan, use your head etc. as well look for some books on mind mapping. As for that mnemonic system I cannot find it :/ but similar thing is GMS from 'Phenomenal memory', look it up on google & you shall find it... :)

I'll check them out, thanks!