Dkron VS Django REST framework

My SaaS is not that big and doesn't need very complicated CRON management. I tried different options like dkron but it doesn't hold any job data after for example removing the container, according to a discusion issue I created. Source: about 1 year ago

Well, you can either use this as an example or use it cause the work is done: dkron. Source: over 1 year ago

I'am also familiar to hangfire, used in the past as distributed job scheduler for Owin microservices in C# too. Btw when we moved towards Golang stack realized that hangfire wasnt really necessary. It was enough standard and idiomatic Go code, learning using Go Routine adding any Cron library and maybe a Redis dependency if persistence is needed. But if you really prefer something hangfire-like, give a try to... Source: about 2 years ago

Perhaps https://dkron.io/ can solve your problem? Source at https://github.com/distribworks/dkron. Source: over 2 years ago

Oops, my bad. I was trying to refer to dkron https://dkron.io/. Source: over 2 years ago

Django Rest Framework seems like the most mature and works great with Django. But its strength, if I understand correctly, is for auto-creating all the necessary endpoints for manipulating models, which might be useful for data entry applications. I know that it's super flexible and probably my use case will be covered, but it seems that this it might get complicated. Source: almost 2 years ago

There is one last thing I'm a little confused on with Django Rest Framework and that's the different between permission classes and authentication classes. Source: about 2 years ago

I am using django-rest-framework. It provides an awesome Django admin style browsable self-documenting API. But anyone can visit those pages and use the interface to add data (POST). How can I disable it? Source: over 2 years ago