Skip to content
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

[Wordpress] Change the default deployment path from / to /blog #1333

Closed
battbot-snappy opened this issue Jan 2, 2024 · 6 comments
Closed
Assignees
Labels
how-to How to issues reported by users solved stale 15 days without activity triage Triage is needed wordpress

Comments

@battbot-snappy
Copy link

Describe your issue as much as you can

We deployed a bitnami wordpress AMI on an instance on AWS. We want to map the /blog path to this wordpress instance via the application loadbalancer for our domain via the path mapping /blog/*. However, access to our domain /blog path will result in page not found error as the wordpress application is hosted directly under the / path on the instance. How can we change the deployment so it's served under the /blog path? Tried googling the issue and couldn't find a relevant result. Under the /opt/bitnamic/apache/conf folder there's too many conf files. We are not sure which one really governs the behaviour. So far we tried changing the /opt/bitnami/apache/conf/vhosts/wordpress-vhost.conf file by modifying the RewriteBalse from '/' to '/blog/' and it didn't do anything

@battbot-snappy battbot-snappy added the how-to How to issues reported by users label Jan 2, 2024
@github-actions github-actions bot added the triage Triage is needed label Jan 2, 2024
@jotamartos
Copy link
Collaborator

You have a similar request here, could you please take a look at it?

#100 (comment)

@jotamartos jotamartos changed the title Bitnami Wordpress Change the default deployment path from / to /blog [Wordpress] Change the default deployment path from / to /blog Jan 4, 2024
@battbot-snappy
Copy link
Author

battbot-snappy commented Jan 4, 2024

working now. Thank you!

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jan 24, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
@andersonbosa
Copy link

Has anyone managed to accomplish this in the bitnami/wordpress-nginx image?

@jotamartos
Copy link
Collaborator

Hi @andersonbosa,

We do not have any guide regarding how to make this change in NGINX but you should be able to do so by following similar steps than the ones I shared for Apache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
how-to How to issues reported by users solved stale 15 days without activity triage Triage is needed wordpress
Projects
None yet
Development

No branches or pull requests

4 participants