DocFetcher Server 1.2 Release

DocFetcher Server 1.2 is out. This release fixes two indexing-related crashes and a major bug concerning index updates. The bug, as explained in the changelog: If a subfolder within an indexed folder was renamed, moved or removed, the files in that subfolder were not properly updated in the index, causing obsolete files to show up in the search results along the current ones. The obsolete files will disappear once you upgrade to the new release and update all your indexes.

It appears that recently, an unknown number of emails sent to the official support email address (support .. were lost. They were likely blocked on their way through Google’s servers for unknown reasons. If you sent an email to the support address and didn’t get a response, that’s why. Please resend your email to the address currently listed on the support page if your issue still persists. Apologies for the inconvenience!

Subscribe to DocFetcher Pro news

DocFetcher Server 1.1 Release

DocFetcher Server 1.1 is out. This releases is mostly a collection of usability improvements to round out some of the rough edges of the first release. Most items on the changelog are more or less significant, so in this release announcement there isn’t really much to do except copy and paste the entire changelog:

  • The application could not be run on older Linux distributions due to a glibc compatibility issue. It now runs on Linux distributions with glibc 2.17 or newer.
  • Among the indexing settings, there’s now a new setting for skipping content indexing for all files that are bigger than a certain maximum file size. The filenames of these files can still be indexed. With this new setting, it’s now possible to skip large files that may cause the application to run out of memory during indexing.
  • In the Admin Area in the indexes table, there’s a new column “Visible”. By ticking and unticking the checkboxes in that column, you can control which indexes are transmitted to the clients, and which indexes are kept only on the server side. This is useful if you have some very large and rarely used indexes; keeping them on the server side when they’re not needed will make the web interface load faster.
  • In the result table, you can now press the arrow-up and arrow-down keys to navigate to the previous or next result, with the contents of the preview pane updated accordingly. However, for this to work properly, you need to turn off “Automatically scroll to first match in preview pane” in the user preferences.
  • For tablet users, there’s now a button above the result table for downloading the first selected result. Before, downloading results was only possible via the result table’s context menu, which is difficult to open on tablets.
  • For technical reasons, the users that are counted towards the application’s client limit are identified by browser session rather than by IP address. Among other things, this means accessing the web interface from multiple browsers on the same computer counts as multiple clients rather than as a single client. For some users, this can be quite inconvenient. In addition, it was also inconvenient for a single user to switch between different computers. For these use cases, there’s now a workaround called “session stealing”, which means that when the client limit is reached, new users may take over existing sessions, thus kicking their previous owners out of the web interface. The intended use is for users to kick “themselves” out in order to more easily switch between browsers and/or computers. For instances of DocFetcher Server with a client limit greater than 1, session stealing is off by default and must be enabled in the Admin Area on the Access tab.
  • It’s now possible to inject custom CSS and JavaScript into the web interface, on the server side, via the files misc/custom.css and misc/custom.js. Note that no support or HTML stability guarantees for such customizations is provided, as explained in the comments in the custom.css and custom.js files.

Subscribe to DocFetcher Pro news

DocFetcher Server 1.0 Release

After over a year of development, DocFetcher Server 1.0 is now finally out!

For those not in the know, DocFetcher Server is a cousin of DocFetcher and DocFetcher Pro, featuring a proper implementation of the long-requested multi-user and remote-access support that is poorly implemented in DocFetcher and unavailable in DocFetcher Pro.

In essence, DocFetcher Server is a background process that runs on a server computer, indexes files on that computer, and makes those files searchable and downloadable for one or more clients through their web browsers. Typically, you’d want to deploy this kind of software on a server machine in a private or company network, or deploy it on a rented server machine for remote access to your files. Accordingly, DocFetcher Server is geared more towards businesses than individuals, and this combined with the substantially more complex server technology under the hood is why the software is situated at a higher price range than DocFetcher Pro.

During the first 3 weeks after launch, until August 21, 2022, DocFetcher Server will be available at a reduced price (15% off). This will hopefully compensate for any early-release bugs. If you do find any bugs, please help getting them fixed by reporting them to Support.

To be sure, development of DocFetcher Server took much longer than initially expected. Like, how hard can it be to build a web UI on top of the existing DocFetcher Pro core? – Well, turns out, very hard, for two reasons: First, the existing desktop UI turned out to be a lot bigger and deeper than expected, and taking it to the web revealed all kinds of hidden features that took a considerable amount of time to reimplement. And second, designing a web UI turned out to be not only considerably more complex than, but also vastly different from designing a desktop UI, so that in the end very little existing UI code could be reused. – You may not realize this, but a web UI is basically an HTML page pretending to be a user interface. Naturally, all kinds of hacks are involved to make this happen.

Unfortunately, because of these difficulties, DocFetcher Server currently lacks some of the more advanced and/or less frequently used features of DocFetcher Pro, notably the ability to load and save indexing settings, CSV export of search results and indexing errors, and the file size and Custom Types filters. For a complete list of missing features, see this page. – Reimplementing all of these would probably have added three months or more to the development process, and the madness had to stop somewhere.

Speaking of the past, DocFetcher Server was formerly announced as “DocFetcher Pro Server”, but in the end the “Pro” was dropped for the sake of brevity. It’s still “Pro” software though, even more so than DocFetcher Pro!

So, now that DocFetcher Server is out, what about the future of the DocFetcher project? Of course, there are plans for DocFetcher Pro 2.0 and DocFetcher Server 2.0, but no, don’t expect them to come out in the near future. The thing is, the DocFetcher project has been on a development sprint for over two years now (since early 2020), producing as results DocFetcher Pro, a major bugfix release of DocFetcher, and DocFetcher Server. During this sprint, cleanup and maintenance activities were mostly left by the wayside, and this is not sustainable in the long run.

Consequently, the DocFetcher project will now enter a prolonged cleanup and maintenance phase, which will probably produce very little in terms of visible, flashy results, but will produce a lot of internal changes that contribute significantly to the long-term future of the project. To give just two concrete examples:

  1. Since the very beginning, before 2007, DocFetcher has been developed in a development environment known as the Eclipse IDE. Unfortunately, the latter has fallen out of favor with the development community for some time now, and some vital tools needed to develop DocFetcher are no longer being updated. That’s why the DocFetcher project sooner or later needs to get off that sinking ship and migrate to a new development environment. On that occasion, the currently used programming language Scala needs to be upgraded from the aging Scala 2 to the new Scala 3 as well. All this takes a lot of work and will produce exactly zero new features.
  2. DocFetcher Pro and DocFetcher Server will be equipped with so-called “unit tests”, which is programming jargon for automated testing of the software. Among other things, unit tests serve as a safeguard against new major features and changes breaking existing functionality. – That’s just what’s needed when new major features and changes finally get implemented for DocFetcher Pro 2.0 and DocFetcher Server 2.0. Unit tests themselves produce exactly zero new features, unfortunately, but they support the addition of new features down the road.

So, hopefully, DocFetcher Server 1.0 was worth the long wait, for those who were waiting, and hopefully whatever big thing comes next will be worth the wait too. Until then, you can expect to see some more bugfixing in DocFetcher, DocFetcher Pro and DocFetcher Server.

On a final note, until now everyone who bought DocFetcher Pro was automatically subscribed to the DocFetcher Pro newsletter. With the arrival of DocFetcher Server, this has to change a little: The DocFetcher Pro newsletter will cover both DocFetcher Pro and DocFetcher Server news, but if you bought only one of them, you will only receive the subset of the newsletter that pertains to the product you bought. If you want the full newsletter instead, you have to subscribe manually on the Subscribe page. This news article right here will be the first and last article about a DocFetcher Server release that DocFetcher Pro users will receive, unless they subscribe to the full newsletter.

Subscribe to DocFetcher Pro news