docker4drupal | Docker-based Drupal stack | Continuous Deployment library

 by   wodby Shell Version: 6.0.3 License: MIT

kandi X-RAY | docker4drupal Summary

kandi X-RAY | docker4drupal Summary

docker4drupal is a Shell library typically used in Devops, Continuous Deployment, Docker, Drupal applications. docker4drupal has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Docker4Drupal is a set of docker images optimized for Drupal. Use docker-compose.yml file from the latest stable release to spin up local environment on Linux, Mac OS X and Windows.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              docker4drupal has a medium active ecosystem.
              It has 1171 star(s) with 524 fork(s). There are 59 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 114 open issues and 349 have been closed. On average issues are closed in 134 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of docker4drupal is 6.0.3

            kandi-Quality Quality

              docker4drupal has 0 bugs and 2 code smells.

            kandi-Security Security

              docker4drupal has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              docker4drupal code analysis shows 0 unresolved vulnerabilities.
              There are 1 security hotspots that need review.

            kandi-License License

              docker4drupal is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              docker4drupal releases are available to install and integrate.
              It has 71 lines of code, 1 functions and 3 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docker4drupal
            Get all kandi verified functions for this library.

            docker4drupal Key Features

            No Key Features are available at this moment for docker4drupal.

            docker4drupal Examples and Code Snippets

            No Code Snippets are available at this moment for docker4drupal.

            Community Discussions

            QUESTION

            How to make changes to docker-compose.yml and Drupal 9 project files correctly if containers are already running?
            Asked 2021-Aug-08 at 05:53
            1. I installed Docker and Docker Compose
            2. I downloaded the latest release Docker-based Drupal stack (there are php, mariadb, apache images etc.) and put it in the my project folder /var/www/html/mydrupaldocker
            3. Next, I made the settings in the .env and docker-compose.yml files and running the containers with the command:
              docker-compose up -d
            4. After running images from this folder, as well as adding the unzip drupal 9 folder to the my project folder, I will start installing drupal 9 in the browser.

            And I have questions on two possible situations:

            Situation №1:

            I made mistakes in the file docker-compose.yml I have the commented code which is responsible for the few images. Accordingly, the containers were not started. And I want to place the project in another place of the computer (not critical, but it is desirable)

            I can do:
            docker-compose stop
            docker-compose rm

            Fix everything that I need. And run again:

            docker-compose up -d

            Is it right to do so? Or do I need something otherwise?

            Situation №2:

            Everything is set up well, running all the necessary containers, installed the Drupal 9 site in the container. And then I created a sub theme, added content, wrote code in php, js, css files, etc.

            How do I commit the changes now? What commands do you need to write in the terminal? For example, in technology such as git, this is done with the commands:
            git add.
            git commit -m "first"

            How is it done in Docker? Perhaps there will be a situation when I need to roll back the container to the version below.

            ...

            ANSWER

            Answered 2021-Aug-08 at 05:53

            Okay, let's go by each case.

            Situation No.1

            Whenever you make changes to docker-compose.yml, it's fine to restart the service/images so they reflect the new changes. It could be as minor as a simple port switch from 80 to 8080. Hence, you could just do docker-compose stop && docker-compose up -d and docker-cli will restart the containers with the new changes.

            You don't really need to remove the containers/services unless you have used custom Dockerfile and have made changes to it. Although, your below assumption would still give the same result, it's just has an extra step of removing the containers without any changes being done to the actual docker images.

            I can do: docker-compose stop docker-compose rm

            Fix everything that I need. And run again:

            docker-compose up -d

            Situation No.2

            In this you would be committing your entire project to git along with your Dockerfile and docker-compose.yml file from your host machine and not the container. There's no rocket science here.

            You won't be committing your code to git via the containers. The containers are only for deploying and testing your code. You would be committing just the configuration files i.e Dockerfile (if custom is used offcourse) and docker-compose.yml file along with your source code to git. The result would be that, any developer who is collaborating with you in a team, can just take a pull of the project and run docker-compose up -d and the same containers/services running on your machine will be up and running on the host machine of the other dev.

            Regarding how to roll back to old version of docker services, you can just rollback to a previous commit and the docker-compose.yml will be reverted. Then you can just do:

            docker-compose down && docker-compose up -d

            Source https://stackoverflow.com/questions/68696590

            QUESTION

            Install npm and gulp in docker4drupal
            Asked 2020-Nov-01 at 19:09

            I am working on an existing project that was built by Droopler distribution and docker4drupal. As per Droopler distribution documentation, it requires npm and gulp to compiled sass easily and docker4drupal don't have it by default.

            I tried to install in the container by sudo apt-get install npm and it says:

            sudo: apt-get: command not found

            Is there any way to install npm and gulp in docker4drupal for my existing project?

            ...

            ANSWER

            Answered 2020-Nov-01 at 19:09

            I am able to install npm & gulp, access php container and install those.

            access php container docker-compose exec php bash install npm sudo apk update && sudo apk add npm install gulp globally sudo npm install -g gulp

            This is how I do it, maybe there is a better way.

            Reference: Install npm and gulp

            Source https://stackoverflow.com/questions/64635199

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install docker4drupal

            You can download it from GitHub.

            Support

            Full documentation is available at https://wodby.com/docs/stacks/drupal/local.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/wodby/docker4drupal.git

          • CLI

            gh repo clone wodby/docker4drupal

          • sshUrl

            git@github.com:wodby/docker4drupal.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link