-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Progressive build for static site #113
Comments
Note: WOOT! I finally survived a whole run!! yay! 🎈 🍰 🎉 😃 Progress! 20m 18s elapsed. |
The difficulty with this is that generating each page will still reference other information (for example to determine who someone may be living with or close to), each page generation is not stateless. Having said that, any suggestions for speed improvements will be greatly appreciated. |
Nod. That's a very valid concern under normal conditions. I was just thinking about some quick |
I understand - I use a similar hack when testing a specific person |
Feature request: Add switch to skip processing of already-existing
static-site/
individuals.With 4,176 people in my GEDCOM, an attempted build of the static site takes 20 minutes. I'm having to iterate lots of data errors in my GEDCOM that are crashing
ged2site
. Fair enough, but it sure would be nice if I didn't have to wait 20 minutes for it to re-process thousands of individuals that processed fine last time.It would be great if I modify a specific individual in my GEDCOM, I could just delete that one
static-site/
file, runged2site
, and re-generate that one individual in seconds instead of 20 minutes.With dozens of errors in my GEDCOM I need to fix, it's currently taking hours to iterate through them, one at a time.
The text was updated successfully, but these errors were encountered: