Otherwise, if you're starting a fresh project with a separate front-end, this is a good template: https://github.com/gtalarico/django-vue-template/
I came across a few other examples, but they didn't do a good job of displaying the initial value or handling choices with integer values.
Updating specific requirements is something I need to do pretty often, and it's not fun to explain all the Pipenv quirks to the team.
Pip-tools looks like it does everything I need and has fewer quirks, so I ended up making the switch.
Pipenv uses pip-tools under the hood, so the migration to pip-tools was very smooth. The migration process was:
- Copy the dev-packages and packages sections of the Pipfile to their own requirements.in files.
- Run pip-compile
- Copy over the specific versions and hashes from the Pipfile.lock to the generated requirements.txt.
I learned about the "playsinline" fix from here: https://webkit.org/blog/6784/new-video-policies-for-ios/
Adding "playsinline" to my video tag fixed it.
I set up a ESP32 houseplant soil water + temperature + humidity + light sensor that sends me a daily status update message.
Here’s the code for it: https://gist.github.com/pawl/6a408afde1411c6b1f58980e3d1dff83
Here's what I did:
- Purchase the domain using Route53.
- Create two public s3 buckets (www.heckingoodboys.com and heckingoodboys.com)
- Enable "Static website hosting" on www.heckingoodboys.com and redirect to heckingoodboys.com.
- Enable "Static website hosting" on heckingoodboys.com, select "use this bucket to host this website", and use routing rules similar to this:
- Back to Route53 - Create an A record for both www.heckingoodboys.com and heckingoodboys.com using the alias to their respective buckets. (this will be the first option in autocomplete)
Why not just use a CNAME from www.heckingoodboys.com to heckingoodboys.com? AWS says they don't charge for aliases, but they do charge for CNAMEs. So, I used an alias to a bucket instead.