You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a project file, the default value for project/@output-dir is output. And the default value for project/@stage is output/stage. If you override the first default, with say project/@output-dir="myoutput" and then you deploy, it creates an output/stage/ folder (creating the intermediate output/ folder) and now your file tree has both output/ and myoutput/.
Thoughts on making stage just not be a subfolder of output?
The text was updated successfully, but these errors were encountered:
Hot take, I forget why we put the default stage in output (maybe just to be lazy with gitignores), but I think having stage as a sibling of output makes sense.
I don't love having another root-level folder for this, as for most users currently, stage will be identical to output/web. I think having both will be confusing.
No reason we can't get the location of stage to be relative to the value of project/@stage with default being the stage subdirectory of the actual project/@output directory.
In a project file, the default value for
project/@output-dir
isoutput
. And the default value forproject/@stage
isoutput/stage
. If you override the first default, with sayproject/@output-dir="myoutput"
and then you deploy, it creates anoutput/stage/
folder (creating the intermediateoutput/
folder) and now your file tree has bothoutput/
andmyoutput/
.Thoughts on making
stage
just not be a subfolder ofoutput
?The text was updated successfully, but these errors were encountered: