selloween / docker-multi-wordpress

Run multiple WordPress Docker containers with NGINX Proxy, LetsEncrypt and PHP Composer
GNU General Public License v3.0
75 stars 18 forks source link

Step by Step #10

Closed compulon closed 5 years ago

compulon commented 5 years ago

Step by Step:

1.- Clone docker-multi-wordpress 2.- Delete wordpress_02 and rename wordpress_01 3.- Rename it to .env 4.- Change the name of the container and the credentials of the database and wp 5.- Run docker-compose up -d in the nginx 6.- Run docker-compose up --build

Result: problem wp without design, imagine problem with css... Note: I'm not touching the files: composer.json, Dockerfile, wp-config.php.

What am I doing wrong?

selloween commented 5 years ago

I can't reproduce your problem. The steps you describe are correct and work for me.

Result: problem wp without design, imagine problem with css... <

Do you mean the frontend or the admin dashboard ? If you activated the custom theme - that's entirely barebone - just a index.php outputting "hello world" and a style.css without any styles.

selloween commented 5 years ago

Are you working locally? If so did you follow the step by adding a dummy domain to your hosts file ? If not you will get an 503 status code from the NGINX proxy.

compulon commented 5 years ago

I'm with digital ocean

El lun., 22 jul. 2019 9:00 a. m., Selwyn Rogers notifications@github.com escribió:

Are you working locally? If so did you follow the step by adding a dummy domain to your hosts file ? If not you will get an 503 status code from the NGINX proxy.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/selloween/docker-multi-wordpress/issues/10?email_source=notifications&email_token=AL5HP7WTYWBKZTQZYGWYLXTQAWVNHA5CNFSM4ID3QPZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2P2ZRI#issuecomment-513780933, or mute the thread https://github.com/notifications/unsubscribe-auth/AL5HP7TLFJ6AQ4WEOOXZXFDQAWVNHANCNFSM4ID3QPZA .

compulon commented 5 years ago

in both cases...

El lun., 22 jul. 2019 8:48 a. m., Selwyn Rogers notifications@github.com escribió:

I can't reproduce your problem. The steps you describe are correct and work for me.

Result: problem wp without design, imagine problem with css... Do you mean the frontend or the admin dashboard ? If you activated the custom theme - that's entirely barebone - just a index.php outputting "hello world" and a style.css without any styles.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/selloween/docker-multi-wordpress/issues/10?email_source=notifications&email_token=AL5HP7QY2NNZTSONYC3OYOLQAWUB7A5CNFSM4ID3QPZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PZ2TQ#issuecomment-513776974, or mute the thread https://github.com/notifications/unsubscribe-auth/AL5HP7VSLC23Q2A6VEVXUBLQAWUB7ANCNFSM4ID3QPZA .

selloween commented 5 years ago

This sounds like a problem with your server and not the docker setup. I would suggest checking if the containers are running with docker ps. Then check if the ports 80 and 443 are open on your host. Then check if the site is running using the IP address instead of the domain. Have you added a DNS entry pointing to host IP? Have you looked in the http response what status code comes back using the inspector tools of your browser ? There are too many factors - so i am afraid I can't really help you as this is not a bug or issue in the docker setup files.

compulon commented 5 years ago

will be a limitation of digital ocean to force create a drop for each wordpress ...

El lun., 22 jul. 2019 9:20 a. m., Selwyn Rogers notifications@github.com escribió:

This sounds like a problem with your server and not the docker setup. I would suggest checking if the containers are running with docker ps. Then check if the ports 80 and 443 are open on your host. Then check if the site is running using the IP address instead of the domain. Have you added a DNS entry pointing to host IP? Have you looked in the http response what status code comes back using the inspector tools of your browser ? There are too many factors - so i am afraid I can't really help you as this is not a bug or issue in the docker setup files.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/selloween/docker-multi-wordpress/issues/10?email_source=notifications&email_token=AL5HP7WJL5GSWPEWSI32P3DQAWX3PA5CNFSM4ID3QPZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2P4S2Y#issuecomment-513788267, or mute the thread https://github.com/notifications/unsubscribe-auth/AL5HP7VHIOCB3RATEYQI42DQAWX3PANCNFSM4ID3QPZA .

selloween commented 5 years ago

Afaik DigitalOcean Droplets are Docker containers - In general you can run Docker in Docker - but I would not suggest running multiple WP containers in a droplet/container - it would not surprise me if DigitalOcean prevents this.

compulon commented 5 years ago

I did something similar with a multi odoo docker without problems ... Let me keep checking and trying to see what happens...

El lun., 22 jul. 2019 9:30 a. m., Selwyn Rogers notifications@github.com escribió:

Afaik DigitalOcean Droplets are Docker containers - you can run Docker in Docker - but I would not suggest running multiple containers in a droplet - it would not surprise me if DigitalOcean prevents this.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/selloween/docker-multi-wordpress/issues/10?email_source=notifications&email_token=AL5HP7TYL2FESG6NGUHSRY3QAWZA7A5CNFSM4ID3QPZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2P5Q5Y#issuecomment-513792119, or mute the thread https://github.com/notifications/unsubscribe-auth/AL5HP7TYYDSBPF556MLNUJDQAWZA7ANCNFSM4ID3QPZA .