Hi,

It might be nice to publish the trunk view of althttpd.c so people can easily fetch it when there are updates:

https://sqlite.org/althttpd/raw?filename=althttpd.c&ci=trunk

Thanks for commenting.

I just created this repository earlier this morning. I wasn't expecting anybody to notice it quite so quickly. Suggestions on how to make the site more accessible are welcome.

I'm not sure what "publish the trunk view of althttpd.c" means, exactly. You can click on the "Files" option in the main menu, and there see the "althttpd.c" in the file list. If you then click on the link, you will see the actual source code to althttpd.c. There is a "Download" button on that page as well. Does that not fulfill most peoples needs?

Hi,

Thanks for creating althttpd and continuing to improve it.

The method you selected does work, but if someone wanted their server to have the latest althttpd, they would need to visit this site, download the file, and transfer it to the server to compile.

By publishing (in effect a sentence on althttpd.md) how to get the latest link for downloading the file, folks would be able to download to the server via curl, wget or tools like that (skipping the download locally part). Perhaps they would make a script to download, compile, and replace their existing althttpd binary with the latest.

Now if you start making releases of althttpd with version numbers or similar, this wouldn't be necessary, as someone would be able to copy the link to the download and copy to the server directly. For example, the fossil download page. However, althttpd has existed since 2004 without the need to have releases, so I don't think this method is necessary.

Just something to consider. As I said in the latter example, you've been maintaining althttpd for 16 years and been fine with how things have been, so no need to feel compelled to change this.

I've just submitted a merge request for the althttpd package I maintain for Alpine Linux updating for the new repo location:

https://sqlite.org/althttpd/zip?in=althttpd.c&r=202012011402

Using the commit timestamp in the url should always get you the same code, effectively making every commit a versioned release. The timestamp also serves as the package version in the Alpine repo.

One thing I haven't quite figured out is how to get an email when althttpd.c is updated. I had my login checked to get a digest when it was under the misc/ files location but I've never had any digests show up in my email. I've just been checking back periodically and getting lucky noticing changes, like today.

Click on the "login" link in the upper right-hand corner. Click on the "Create A New Account" button on that page. Once you have an account, you can request automatic email notification for all changes.

Yes, that would be cool to import all the history of althttpd.c as well as the history for the althttpd.md documentation file. But Fossil does not currently have that capability. I would, as you suggest, need to do a lot of web-scraping to pull this off.

But this seems like a good opportunity (and test case) to enhance Fossil with a new command that will extract the history of some subset of files into a new repository. I'll make a note to work on that. At some point, the current Fossil repository for althttpd.c might be replaced with a new one that includes the complete history of althttpd.c and althttpd.md.

I have attempted to start a discussion of the technical issues involved with this idea over on the Fossil Forum.