A static site repo viewer
Tucker McKnight <[email protected]> Thu, 27 Mar 2025 01:14:03 -0600
| Newsgroups | gmane.comp.version-control.darcs.user |
|---|---|
| Message-ID | <CAE1hpOiarK6_-oEQWF9kC8WhMB0zsG2Zj4kxzUFawyLVkiLqtQ@mail.gmail.com> |
--===============4370290926480567763== Content-Type: multipart/alternative; boundary="000000000000817a5806314db32e" --000000000000817a5806314db32e Content-Type: text/plain; charset="UTF-8" Hi! Darcs newbie here. I've been enjoying learning about it. I spent some time over the weekend working on a static site generator for displaying a darcs repository. It's very basic at the moment, but it does work, allowing you to browse files, view patches, clone, and pull a specific patch. It's here: https://repos.tuckerm.us/repos/eleventy-darcs Since I only learned about darcs recently, I have a question about how a typical darcs user would "push" their work to a static website. If you were working on multiple changes locally and only wanted one of those changes to show up on your website, how would you want to do that? I know that with "darcs push" you can specify which patch(es) you want to push. But in this case, with a static website, you aren't actually pushing to a remote repository. The idea here is that the plain HTML pages are generated locally on your computer, and then you copy those HTML pages to your web server. Would it make sense to have a config file where you list specific tags and patches that should show up on the site, with a default option of showing all available patches? That doesn't seem all that different from typing "darcs push" to either send all patches or send some specific ones. But maybe there is a more darcs-y way of doing this that I'm not familiar with. Some other notes: - It works on the darcs.net repository. - It takes about a minute (on my computer, at least) to generate the site for darcs.net. - The full output of "darcs log --verbose" alone is 87 megabytes. - The resulting HTML pages are 300+ megabytes. I plan to add features to this over the next few weekends. Would love to hear any suggestions people have! -Tucker --000000000000817a5806314db32e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi! Darcs newbie here. I've been enjoying learnin= g about it.</div><div><br></div><div>I spent some time over the weekend wor= king on a static site generator for displaying a darcs repository. It's= very basic at the moment, but it does work, allowing you to browse files, = view patches, clone, and pull a specific patch.</div><div><br></div><div>It= 's here: <a href=3D"https://repos.tuckerm.us/repos/eleventy-darcs">http= s://repos.tuckerm.us/repos/eleventy-darcs</a></div><div><br></div><div>Sinc= e I only learned about darcs recently, I have a question about how a typica= l darcs user would "push" their work to a static website.</div><d= iv><br></div><div>If you were working on multiple changes locally and only = wanted one of those changes to show up on your website, how would you want = to do that? I know that with "darcs push" you can specify which p= atch(es) you want to push. But in this case, with a static website, you are= n't actually pushing to a remote repository. The idea here is that the = plain HTML pages are generated locally on your computer, and then you copy = those HTML pages to your web server. Would it make sense to have a config f= ile where you list specific tags and patches that should show up on the sit= e, with a default option of showing all available patches? That doesn't= seem all that different from typing "darcs push" to either send = all patches or send some specific ones. But maybe there is a more darcs-y w= ay of doing this that I'm not familiar with.</div><div><br></div><div>S= ome other notes:</div><div><br></div><div>- It works on the <a href=3D"http= ://darcs.net">darcs.net</a> repository.</div><div>- It takes about a minute= (on my computer, at least) to generate the site for <a href=3D"http://darc= s.net">darcs.net</a>.</div><div>- The full output of "darcs log --verb= ose" alone is 87 megabytes.</div><div>- The resulting HTML pages are 3= 00+ megabytes. <br></div><div><br></div><div><div> I plan to add features t= o this over the next few weekends. Would love to hear any suggestions peopl= e have!<br></div></div><div><br></div><div>-Tucker<br></div></div> --000000000000817a5806314db32e-- --===============4370290926480567763== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ darcs-users mailing list [email protected] https://lists.darcs.net/mailman/listinfo/darcs-users --===============4370290926480567763==--