Hi! I think this issue might be a common source of confusion for people using Getdown for the first time.
Currently, java -classpath getdown-core-X.Y.jar com.threerings.getdown.tools.Digester myapp generates two files:
Regarding this, the Quick Start documentation states:
If your app has never shipped with the old digest.txt file, you can omit it from your app distribution and only use a digest2.txt file [...].
However, this is not true. The Getdown Launcher actually does require both digest.txt and digest2.txt on the host. See this issue where another user ran into the same confusing error due to the misleading documentation. In that thread, @samskivert confirms this:
So yes, [even] if this is a completely new app that has never had users, you do have to keep this vestigial digest.txt file around, which is annoying, but I didn't have time to do the extra work to make Getdown cope with not having a digest.txt file.
If it's too much work to make the Getdown Launcher work with just the digest2.txt file, at least, the documentation should be changed to correctly state that both digest.txt and digest2.txt are currently required on the host, i.e. that you can not omit digest.txt.
Kind regards
Tom
Hi! I think this issue might be a common source of confusion for people using Getdown for the first time.
Currently,
java -classpath getdown-core-X.Y.jar com.threerings.getdown.tools.Digester myappgenerates two files:digest.txtdigest2.txtRegarding this, the Quick Start documentation states:
However, this is not true. The Getdown Launcher actually does require both
digest.txtanddigest2.txton the host. See this issue where another user ran into the same confusing error due to the misleading documentation. In that thread, @samskivert confirms this:If it's too much work to make the Getdown Launcher work with just the
digest2.txtfile, at least, the documentation should be changed to correctly state that bothdigest.txtanddigest2.txtare currently required on the host, i.e. that you can not omitdigest.txt.Kind regards
Tom