Docker-compose services build & deployment workflow












0















Recently I started making a REST API.
My plan was to use React.js, Flask and Postgres all being created with docker-compose during development and then in production use React and Flask services with docker-compose but make the database run on VPS (outside of docker container). I should also add that I am currently doing my migrations via Flask-Migrate module.



I was thinking of a way how to easily deploy the project to a VPS by git and build the docker-compose using git post-receive hook, since I want to have full control of the process, but...




  1. How would I make database migrations this way?

  2. Is this a good way to build & deploy a project?


Sorry for any inconvenience and feel free to ask me for further info if you can't understand my questions.










share|improve this question





























    0















    Recently I started making a REST API.
    My plan was to use React.js, Flask and Postgres all being created with docker-compose during development and then in production use React and Flask services with docker-compose but make the database run on VPS (outside of docker container). I should also add that I am currently doing my migrations via Flask-Migrate module.



    I was thinking of a way how to easily deploy the project to a VPS by git and build the docker-compose using git post-receive hook, since I want to have full control of the process, but...




    1. How would I make database migrations this way?

    2. Is this a good way to build & deploy a project?


    Sorry for any inconvenience and feel free to ask me for further info if you can't understand my questions.










    share|improve this question



























      0












      0








      0








      Recently I started making a REST API.
      My plan was to use React.js, Flask and Postgres all being created with docker-compose during development and then in production use React and Flask services with docker-compose but make the database run on VPS (outside of docker container). I should also add that I am currently doing my migrations via Flask-Migrate module.



      I was thinking of a way how to easily deploy the project to a VPS by git and build the docker-compose using git post-receive hook, since I want to have full control of the process, but...




      1. How would I make database migrations this way?

      2. Is this a good way to build & deploy a project?


      Sorry for any inconvenience and feel free to ask me for further info if you can't understand my questions.










      share|improve this question
















      Recently I started making a REST API.
      My plan was to use React.js, Flask and Postgres all being created with docker-compose during development and then in production use React and Flask services with docker-compose but make the database run on VPS (outside of docker container). I should also add that I am currently doing my migrations via Flask-Migrate module.



      I was thinking of a way how to easily deploy the project to a VPS by git and build the docker-compose using git post-receive hook, since I want to have full control of the process, but...




      1. How would I make database migrations this way?

      2. Is this a good way to build & deploy a project?


      Sorry for any inconvenience and feel free to ask me for further info if you can't understand my questions.







      docker docker-compose database-migration githooks






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 3 at 8:46







      Davkk

















      asked Jan 2 at 18:04









      DavkkDavkk

      84




      84
























          1 Answer
          1






          active

          oldest

          votes


















          0














          There are a few options in this field, but I personally prefer to use Liquibase to manage my schema and migrations. I use Knex for my data access inside node who also provides some of the same capabilities, but I prefer Liquibase. I'm currently generating a docker image and publishing that which gets auto-run, but once my current project is nearing release I'll probably move to a manual step to run DB migrations via spinnaker.






          share|improve this answer























            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',
            autoActivateHeartbeat: false,
            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%2f54011083%2fdocker-compose-services-build-deployment-workflow%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            There are a few options in this field, but I personally prefer to use Liquibase to manage my schema and migrations. I use Knex for my data access inside node who also provides some of the same capabilities, but I prefer Liquibase. I'm currently generating a docker image and publishing that which gets auto-run, but once my current project is nearing release I'll probably move to a manual step to run DB migrations via spinnaker.






            share|improve this answer




























              0














              There are a few options in this field, but I personally prefer to use Liquibase to manage my schema and migrations. I use Knex for my data access inside node who also provides some of the same capabilities, but I prefer Liquibase. I'm currently generating a docker image and publishing that which gets auto-run, but once my current project is nearing release I'll probably move to a manual step to run DB migrations via spinnaker.






              share|improve this answer


























                0












                0








                0







                There are a few options in this field, but I personally prefer to use Liquibase to manage my schema and migrations. I use Knex for my data access inside node who also provides some of the same capabilities, but I prefer Liquibase. I'm currently generating a docker image and publishing that which gets auto-run, but once my current project is nearing release I'll probably move to a manual step to run DB migrations via spinnaker.






                share|improve this answer













                There are a few options in this field, but I personally prefer to use Liquibase to manage my schema and migrations. I use Knex for my data access inside node who also provides some of the same capabilities, but I prefer Liquibase. I'm currently generating a docker image and publishing that which gets auto-run, but once my current project is nearing release I'll probably move to a manual step to run DB migrations via spinnaker.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 2 at 18:54









                Russ BrownRuss Brown

                415




                415
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011083%2fdocker-compose-services-build-deployment-workflow%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

                    Monofisismo

                    Angular Downloading a file using contenturl with Basic Authentication

                    Olmecas