Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I was thinking about this recently, and while the command line will always be faster, it would still be useful to have a user interface for generating static HTML, and perhaps even for installing. Really low priority but this is a target for 1.0.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | interdiff-3006451-7-8.txt | 3.29 KB | samuel.mortenson |
| #8 | 3006451-8.patch | 41.92 KB | samuel.mortenson |
| |||
Comments
Comment #2
samuel.mortensonI think I only want this for Tome Static. We rely on the command line heavily for site installs and config imports, rewriting that for the UI would be a huge undertaking regardless of what Tome is doing.
Comment #3
samuel.mortensonMuch UI, very fast. No tests but there aren't any for the commands either, will have to think if that's a follow up for beta2.
Comment #5
samuel.mortensonTweaking the cache fix here.
Comment #6
samuel.mortensonI didn't think it was fair that the UI is now probably faster than the command line, so I made some tweaks and changed the static command to spawn five processes at a time, with each process generating five paths. I ran into a lot of core problems with this but still think it will work for most sites. Users who find problems can always report them here, and can optionally turn down the --path-count back down to 1.
Comment #7
samuel.mortensonConsolidated code between the command line and form.
Comment #8
samuel.mortensonWhen we were requesting one path at a time per process, exceptions were fine because they didn't interfere with other requests. Now we need to catch all errors when requesting paths and display them to the user without breaking the entire build.
Comment #10
samuel.mortenson