[dead]
Show HN: Django Keel – 10 Years of Django Best Practices in One Template
11–20 of 32 posts
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#1215 years of Django for me personally. I use it now in my SaaS as a data backend with Strawberry GraphQL and lean heavily in on the admin. My frontend is React Router 7 framework mode. I’m going to be checking into Keel for my new toy projects. I wish it would use ty but easy enough to add myself.
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#13Looks great, looking forward to trying it.
Interesting that you included Temporal for background task processing — did you ever use it in production in a Django project instead of Celery?
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#14Looks great, looking forward to trying it. Interesting that you included Temporal for background task processing — did you ever use it in production in a Django project instead of Celery?
Quite honestly, I haven't. I've been playing with temporal, and since it's picking up pace, I thought to have an option to have Temporal in place of celery.
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#1515 years of Django for me personally. I use it now in my SaaS as a data backend with Strawberry GraphQL and lean heavily in on the admin. My frontend is React Router 7 framework mode. I’m going to be checking into Keel for my new toy projects. I wish it would use ty but easy enough to add myself.
Interesting! I've loved Strawberry GraphQL.
If you end up adding anything, you may also choose to give back to the template so that others can use it.
I do not understand what you meant by "ty", though?
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#16encountered this post in reddit maybe an hour ago. the comment sections are very different. i'm gonna stick with HN for sure.
good project though. using copier instead of cookiecutter is a good choice.
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#17encountered this post in reddit maybe an hour ago. the comment sections are very different. i'm gonna stick with HN for sure. good project though. using copier instead of cookiecutter is a good choice.
It was all great on Reddit, though until some folks decided to downvote for no apparent reason and then deleted their accounts.
I've chosen copier because of all the pain I've gone through for years just to keep my template and projects running in parallel updated.
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#1815 years of Django for me personally. I use it now in my SaaS as a data backend with Strawberry GraphQL and lean heavily in on the admin. My frontend is React Router 7 framework mode. I’m going to be checking into Keel for my new toy projects. I wish it would use ty but easy enough to add myself.
Interesting! I've loved Strawberry GraphQL. If you end up adding anything, you may also choose to give back to the template so that others can use it. I do not understand what you meant by "ty", though?
I think it's ty the typechecker :D https://docs.astral.sh/ty/
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#1915 years of Django for me personally. I use it now in my SaaS as a data backend with Strawberry GraphQL and lean heavily in on the admin. My frontend is React Router 7 framework mode. I’m going to be checking into Keel for my new toy projects. I wish it would use ty but easy enough to add myself.
Interesting! I've loved Strawberry GraphQL. If you end up adding anything, you may also choose to give back to the template so that others can use it. I do not understand what you meant by "ty", though?
Ty is the typechecker by Astral. https://docs.astral.sh/ty/.
Reviewing the dependencies in the jinja file -- how difficult is it to keep these up to date? I see Django Debug Toolbar is still ^4.3.0.
Re: Show HN: Django Keel – 10 Years of Django Best Practices in One Template
#20> pytest - Comprehensive test suite (80% coverage minimum)
Why would this ever be less than 100%?