Automate project in laravel

Question

I have an app in Laravel with .env.local file (a and I made the next docker-compose file:

api:
container_name: nadal_api
build:
  context: .
  dockerfile: Dockerfile
volumes:
  - .:/var/www/html/app
ports:
  - ${APP_PORT}:80
links:
  - db
  - redis

And my Dockerfile:

FROM composer:latest AS composer

WORKDIR /var/www/html/app/



FROM php:7.2-fpm-stretch

RUN apt-get update && apt-get install -y \
    supervisor \
    nginx \
    zip

ADD docker/nginx.conf /etc/nginx/nginx.conf ADD
docker/virtualhost.conf /etc/nginx/conf.d/default.conf ADD
docker/supervisord.conf /etc/supervisor/conf.d/supervisord.conf

ARG enviroment

COPY --from=composer /usr/bin/composer /usr/bin/composer

COPY .env.local .env RUN chmod -R g+w /var/www/html/app/bootstrap

RUN composer install RUN php artisan key:generate

EXPOSE 80

CMD ["/usr/bin/supervisord"]

I want to clone the repository and when doing a docker-compose build that does the following in the dockerfile:

rename .env.local to .env
give permissions to the storage folder. I have an error in this line

RUN chmod -R g+w /var/www/html/app/bootstrap

chmod: cannot access '/var/www/html/app/bootstrap': No such file or
directory

docker-compose.yaml: ${APP_PORT} take values from .env.local (I tried with env_file but it does not work

WebMan · Accepted Answer · 2019-04-26 13:30:05Z

3

In your Dockerfile there is no COPY action to copy all your current project code into created image. Therefore bootstrap folder is not exist in your image. So chmod tells you exactly that.

Volumes (this line - .:/var/www/html/app) will sync your current directory with container later when it will be created depending on image structure. So if you want to give permissions to bootstrap folder then copy project code into image before giving permissions to it. Add this line before permission operations to make folders accessible.

COPY . /var/www/html/app

answered Apr 26, 2019 at 13:30

WebMan

3944 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Juan Pablo B Over a year ago

Thanks, it worked. Do you know abour ${APP_PORT} ? I need .env.local instead of .env

WebMan Over a year ago

Why you need copy and rename? When you copy the entire project then .env also copied into the container. So before begin building just edit your environment based values in .env file all will be fine :)

WebMan Over a year ago

.env is ignored file because of your all secret informations will be inside of this file. You can find that it added inside .gitignore file. So if you want your config to work for your app just copy .env.example file as .env and add your configurations. Then start image building prosess. Then there will be .env file there) and you can use all env variables inside your containers.

WebMan Over a year ago

If you add the line in my answer then all. Files in your app will be inside your image. So that composer.json file also will be there. And because of you set WORKDIR correctly running composer install must add all vendor files into image. Also I can not try now copying but I guess your copy will create correct .env file inside image. If no then after adding the line in my answer just use linux move command to rename file. RUN mv .env.local .env then there will be renamed .env file:)

WebMan Over a year ago

Let us continue this discussion in chat.

|

Collectives™ on Stack Overflow

Automate project in laravel

1 Answer 1

7 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

7 Comments

Your Answer

Sign up or log in

Post as a guest

Related