correction accès aux archives #26
Open
Conversation
This file contains hidden or 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
ON fait un `find -type f -exec sed -i 's/archives\/lyon/archives/g' {} \;`
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.
Avec un
on enlève lyon dans les chemin des archives de la ville.
Et :
dans le htaccess root, si le fichier existe on redirige (pour le moment en 302) vers la même url préfixée par root
dans le htaccess d'archives, on sert le contenu du dossier archives_content, sans archives_content dans l'url et en utilisant le sous domaine de l'url
et dans le htaccess d'archives_content on rends impossible l'accès au contenu redirect tout en permettant d'y accéder en rewrite depuis archives.