jfa-go

Author	SHA1	Message	Date
Harvey Tindall	f083d6b53f	updater: include build date, check against updates build time is included in the binary, so the buildrone release date is compared to it when deciding if something is an update or not.	1 year ago
Harvey Tindall	77c05a4d4f	prefix css with version to avoid cache conflict	3 years ago
Harvey Tindall	d7ab01063a	apt: Use commit count to fix version comparisons previous fix only worked because the numerical portion of the commit hash happened to be greater. This should do properly fix it.	3 years ago
Harvey Tindall	5892899114	thread compile_mjml	4 years ago
Harvey Tindall	eb8f2777ae	fix naming conflict with goreleaser, add buildrone key to other steps	4 years ago
Harvey Tindall	92332206f0	add basic update functionality If enabled, jfa-go pings buildrone (hosted at builds.hrfee.pw) every 30 min for new updates. If there is one, it gets information (and if applicable, a binary) from the appropriate source (buildrone, github, or dockerhub) and displays it on the admin page. You can switch update channels between stable and unstable. For binary releases, updates are downloaded automatically and installed when the user presses update. Since this obviously introduces some "phone-home" functionality into jfa-go, I just want to say IPs are not and will not be logged by buildrone, although I may later introduce functionality to give a rough idea of the number of users (again, no IPs stored). The whole thing can also be turned off in settings.	4 years ago