How to create a CRUD REST API for all Django models with DRF?











up vote
0
down vote

favorite












How would one go about taking all models from all applications in django and then expose all of them under a systematic CRUD endpoint such as api/models/**** without writing DRF Views for each model individually? In other words, how does one create a generic CRUD API for all models of a django server to quickly modify data in the database via REST?



So if we have this application file structure



application/
/auth
/models
/token.py
/other_model.py
/shop
/profile
/...


It would result in the following CRUD endpoints



domain.com/api/models/auth/token
domain.com/api/models/auth/other_model
domain.com/api/models/shop/card
...


Further, these generic endpoints could allow basic filtering (by id, define return fields with a ?fields=... parameter etc.



I know about Eve but we are committed to django/DRF and we want to cut away a lot of redundant model-serializer-view verticals that offer little value for lots of code.










share|improve this question




























    up vote
    0
    down vote

    favorite












    How would one go about taking all models from all applications in django and then expose all of them under a systematic CRUD endpoint such as api/models/**** without writing DRF Views for each model individually? In other words, how does one create a generic CRUD API for all models of a django server to quickly modify data in the database via REST?



    So if we have this application file structure



    application/
    /auth
    /models
    /token.py
    /other_model.py
    /shop
    /profile
    /...


    It would result in the following CRUD endpoints



    domain.com/api/models/auth/token
    domain.com/api/models/auth/other_model
    domain.com/api/models/shop/card
    ...


    Further, these generic endpoints could allow basic filtering (by id, define return fields with a ?fields=... parameter etc.



    I know about Eve but we are committed to django/DRF and we want to cut away a lot of redundant model-serializer-view verticals that offer little value for lots of code.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      How would one go about taking all models from all applications in django and then expose all of them under a systematic CRUD endpoint such as api/models/**** without writing DRF Views for each model individually? In other words, how does one create a generic CRUD API for all models of a django server to quickly modify data in the database via REST?



      So if we have this application file structure



      application/
      /auth
      /models
      /token.py
      /other_model.py
      /shop
      /profile
      /...


      It would result in the following CRUD endpoints



      domain.com/api/models/auth/token
      domain.com/api/models/auth/other_model
      domain.com/api/models/shop/card
      ...


      Further, these generic endpoints could allow basic filtering (by id, define return fields with a ?fields=... parameter etc.



      I know about Eve but we are committed to django/DRF and we want to cut away a lot of redundant model-serializer-view verticals that offer little value for lots of code.










      share|improve this question















      How would one go about taking all models from all applications in django and then expose all of them under a systematic CRUD endpoint such as api/models/**** without writing DRF Views for each model individually? In other words, how does one create a generic CRUD API for all models of a django server to quickly modify data in the database via REST?



      So if we have this application file structure



      application/
      /auth
      /models
      /token.py
      /other_model.py
      /shop
      /profile
      /...


      It would result in the following CRUD endpoints



      domain.com/api/models/auth/token
      domain.com/api/models/auth/other_model
      domain.com/api/models/shop/card
      ...


      Further, these generic endpoints could allow basic filtering (by id, define return fields with a ?fields=... parameter etc.



      I know about Eve but we are committed to django/DRF and we want to cut away a lot of redundant model-serializer-view verticals that offer little value for lots of code.







      django rest django-rest-framework






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 4 hours ago

























      asked 6 hours ago









      pascalwhoop

      1,26011125




      1,26011125





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371344%2fhow-to-create-a-crud-rest-api-for-all-django-models-with-drf%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371344%2fhow-to-create-a-crud-rest-api-for-all-django-models-with-drf%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          'app-layout' is not a known element: how to share Component with different Modules

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          SQL update select statement