chore(storybook): switch to static Clever App #1287
Merged
+37
−114
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.
Fixes #1280
What does this PR do?
node-staticdependency,startnpm script,.htaccessto be used by the static Clever App (Apache server).How to review?
npm run storybook:buildlocally and check that thestorybook-staticdirectory contains a.htaccess.Things to discuss
To make Apache handle the SPA correctly & specify cache rules, we need a
.htaccessfile.This
.htaccessfile needs to be placed at the root of the directory served by the server (CC_WEBROOT) which isstorybook-static.We cannot simply put the
.htaccessinstorybook-staticourselves because this directory is removed & created by the storybook build command (+ it's git ignored anyway).We have two options:
.htaccessfile instorybook-static(the option I chose in this PR),CC_POST_BUILD_HOOKto move the.htaccessfile in thestorybook-staticdirectory only when building on Clever Cloud.The option I've chosen has 1 advantage: you cannot forget to add this step, it's part of the build process.
It also has 1 disadvantage: we send
.htaccessfiles even for previews which is useless because they are served by Cellar.