Reverse proxy with path, site-url, wordpress-address url, container

[rdkgit]

Hi!

I've been fighting this for about a week and was wondering if this config is possible with this docker wordpress container.

For a variety of reasons, here is what I want to do:

apache/ssl/reverse proxy <---> port 8100 docker/wordpress container

I want the external URL to be something like https://www.example.com/lab to reverse proxy to/from docker container running on port 8100. The main apache will handle the ssl termination.

So, the content in docker/wp container will be /lab/wp-admin/blahblah and /lab/helloworld/blahblah

What I've struggled with is getting the right settings for site-url, wordpress address, and container .htaccess rewrite rules. What I find is that some of the pages generated will correctly refer to www.example.com/lab but many of the admin pages will not. Plus, some of the test content that would be www.example.com/lab/hello-world can't be found.

Any suggestions on how to configure this? Via logs, I believe I have the main apache/reverse-proxy files set up correctly and the ssl termination.

Thanks,

Bobby

[wglambert]

I would ask over at an Apache/WordPress resource, and supplying your config files. Or the Docker Community Forums, Docker Community Slack, or Stack Overflow.
Since these repos aren't really a user-help forum

[rdkgit]

Thanks! I've tried the wordpress forums and havent received any real help. I've been googling for week and have not found any real solution. I'm struggling to believe that my desired config is all that uncommon. It seems that most WP deployments are for domains and subdomains where / is redirected or reverse proxied for rather than a specific path.

I'll give the docker community forums a whirl. If I solve this, I'll update here too. Hopefully, someone might chime in with an answer.

Thanks,

Bobby

[tianon]

What you'll want to do is run your WordPress container with WORKDIR set to /var/www/html/lab so it knows it is in a subdirectory and acts accordingly.

See #370, #221 (comment), #133 (comment).

[rdkgit]

Hi!

Thanks for your reply. One of the issues is that the base install is in /var/www/html for this docker image. I don't have a sub-dir lab; I merely want /lab to be the proxy/reverseproxy under which my WP is referenced. If I create a lab subdir inside my image and then move everything into it, the WP container seems to re-copy all the WP files to the base /var/www/html directory. Is that the desired behavior?

Thanks,

Bobby

[tianon]

You need to change the workdir of the container as well -- just moving the files is not enough.

[rdkgit]

Do you mean container WORKDIR variable? I didnt see one for wordpress. Set this in docker compose file?

Thanks,

Bobby

[tianon]

Yes, this would be in your compose file, docker run flags, etc.

[tianon]

working_dir:

[rdkgit]

I will give this a whirl. What I really want is /lab as a reverseproxy path without gumming up the install directory or working directory. I would have assumed that setting the site-url would have been sufficient.

Thanks,

Bobby

[tianon]

If you're doing a bind-mount or a volume, just let the container itself abstract the subdirectory away for you, ala:

...
    wordpress:
        image: wordpress
        working_dir: /var/www/html/lab
        volumes:
            - /path/to/my/wordpress/dir:/var/www/html/lab
...

[rdkgit]

Hi!

I managed to get everything working through combo of edit to wp-config.php, setting site-url and address-url, plus placing a link in the install directory pointing the subdir to install dir.

Bobby

[wglambert]

Cool, closing since this is resolved

[rdkgit]

Thank you for closing. I should have done so.