-
Notifications
You must be signed in to change notification settings - Fork 44
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
Comments
You have a similar request here, could you please take a look at it? |
working now. Thank you! |
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. |
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. |
Has anyone managed to accomplish this in the |
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. |
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
The text was updated successfully, but these errors were encountered: