nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwfj5gystuu05y2ssfu7eknl8aes4str77lt24qvyeffufqtw2uksq4m624 (nprofile…m624) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqyphkrmhdqvpxgggaepfunhg2p7tx2u8x5kjkdzwuut624zpaadyqmgsj72 (nprofile…sj72) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq83mzlat6cx6g99w83d34k452z8a07j76nrxsu3ylftt2up3vf6hseexz7j (nprofile…xz7j) The flask work felt like a side quest I should step away from, but it was really helpful to build a tiny working version. It ended up giving me a fresh perspective on this project after so long. How would I approach this project if I had a blank slate?
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqf9uksppl8df9c4d662g8tzku8au9mw9wnjcdylfrx87x909e7pzsau2j5c (nprofile…2j5c) brought up some difficult naming issues. To many people, "deployment" is ongoing. So the name django-simple-deploy doesn't match its behavior. django-initial-deploy might be better, but still not perfect.