-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appreciate any guidance on a subdirectory deployment #370
Comments
See #221 (comment) and #133 (comment). When you create your |
Thanks @tianon for your prompt response, much appreciated. Indeed i have came across those threads #221 and #133 I made sure I have a WORKDIR in my
This is what i get
No modifications made to the docker-entrypoint.sh. |
Not sure why you're duplicating so much of this repo's source, can you elaborate? I was able to get this to work with the following simplified FROM wordpress:php7.1-apache
WORKDIR /var/www/html/blog |
(Closing, since this is answered the best we can. 👍) |
My attempt to change the WORKDIR results in the homepage being served but article pages causing error |
can confirm that it's very easy: pkg_tar(
name = "wp_content",
srcs = glob(["wp-content/**"]),
package_dir = "/usr/src/wordpress",
strip_prefix = ".",
visibility = ["//visibility:public"],
)
container_image(
name = "wordpress_image",
base = "@wordpress_6_1_apache//image",
tars = [
":wp_content",
],
workdir = "/var/www/html/blog",
visibility = ["//visibility:public"],
)
btw: crazy how many trash solutions are out there for this problem |
Hello folks,
I'm having a hard time getting my WP deployment to properly work without any broken links trying to have it served under a subdirectory /blog.
I have used info from Codex to have those changes incorporated in the image. but no success so far.
Also in my k8s ingress i have this configuration snippet which handles the rewriting rules as follows,
I still have those 404 when trying to publish new posts.
Any guidance is extremely appreciated.
The text was updated successfully, but these errors were encountered: