[Website] Copy .htaccess to deploy site #506
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kou
approved these changes
Apr 25, 2024
kou
changed the title
|
Thanks @kou -- the htaccess file is now present on asf-site https://github.com/apache/arrow-site/blob/asf-site/.htaccess 🎉 I also tested a few links like And they seem to have redirected successfully to the new site https://datafusion.apache.org/user-guide/cli/index.html Thank you again @kou for all your help 🙏 |
This was referenced Apr 25, 2024
alamb
added a commit
that referenced
this pull request
Apr 25, 2024
Closes apache/datafusion#10124 # Rationale See apache/datafusion#10124 -- basically we moved a URL that is bookmarked / comes up in google search. We need to redirect to the new location # Changes Use the `.htaccess` process added in #505 #506 with @kou to redirect to the new location
|
Great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow on to #505 to actually copy the .htaccess file to the deployment site. Thanks to @kou for noticing this #505 (comment)