-
Notifications
You must be signed in to change notification settings - Fork 112
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
Build site in another folder? #1055
Comments
A bit cheeky but you could just do More to the point though, no there isn't. I think it should be easy to support though because everything is done via this Is this just a preference thing or do you have a more specific use case in mind? |
Well, what happened was that git/Github/GithubPages eventually got fed up with my site's repo (when it got over 3Gb - I can't blame them), and all my attempts to fix it also failed (and might even have made it worse), with things taking hours to fail rather than minutes, so eventually I just nuked the entire thing. and started again. And my current idea is to maintain two separate repos, one with the site, the other with the source. It is probably just a preference - an easier set-up to think about - but I wondered if it might be useful as a general feature... 🤔 |
is it 3Gb because the whole git history is kept on the in the first case there may be a setting of the github-pages-deploy-action to avoid that, in the latter, maybe it'd make sense to store assets on a cloud bucket somewhere. Anyway, can you test |
It works great! If you think it would be useful to others as well, please add it to one of your forthcoming *ranklin releases...
Haha, well if it was important stuff I might do that, but this is just idle amusement, so I'll stop when it starts to get out of hand again... :) Thanks so much for your work! |
I know this might be a silly question, but is there a way to build the site in a different folder, rather than the same folder that contains all the source files? Something like a
serve(target="/path/to/somewhere/")
?The text was updated successfully, but these errors were encountered: