Jump to content

Kode

Community Developer
  • Posts

    456
  • Joined

  • Last visited

Everything posted by Kode

  1. Needo sets the files permissions incorrectly, use the linuxserver one and it will automatically set the correct permissions
  2. Well if you want an auto upgrading one and the limetech one isn't working, I'd suggest the linuxserver one
  3. Most of the plex dockers auto upgrade when you stop/start them, not 100% about the limetech one, worth a try though
  4. don't forget to scroll down on the docker page as well, it gets lost for me under the running dockers
  5. I think previous issues with the feed have all been resolved now. For some reason, some of the curl requests fail occasionally (6 times in the last 24 hours out of approx 2000 requests as I now get emailed on a curl failure), which previously would have resulted in a small part of the feed dissapearing or not displaying correctly, it now retries the curl request up to a further 5 times with a 1 second sleep between failed attempts, however I have only received an email once at a time suggesting that the request succeeds on the second attempt.
  6. Why don't you do something like substr( $overview, 0, 200 ); And let authors know there is a limit of 200 chars (or whatever you decide), anything over that will be strpped out, might make them take more care of their overview.
  7. The url is on ssl now, so it's https://tools.linuxserver.io/unraid-docker-templates.json
  8. Did you notice how long ago the request was made? Not to mention that link no longer resolves to a thread after the forum hack. A non-issue "soon" might be optimistic
  9. The customisations are stored outside the docker, so you shouldn't lose them should you change the docker you use.
  10. All the application should be back in now, there was a typo, sorry about that.
  11. @Squid: I've added instructions on http://lime-technology.com/forum/index.php?topic=41413.msg392752#msg392752 of how docker authors can get updates to show up straight away, might be worth adding something similar to the first page of this thread.
  12. Can you change the webhooks to match Squids list exactly? Namely: https://github.com/sparklyballs/docker-repo/tree/templates and https://github.com/sparklyballs/beta-repo/tree/master/Sparkly-Beta The other way I tried to do it ended up losing 22 apps, lol
  13. Hold on, found the issue: https://github.com/sparklyballs/beta-repo/tree/master that's what is being sent in the webhook https://github.com/sparklyballs/beta-repo/tree/master/Sparkly-Beta is what is in Squids list, whch will produce different hash values, it should hopefully be fixed now.
  14. yep, 25 extra apps, I've just changed something and have rebuilt the list again, if you can push another change when you get a chance hopefully that will fix it.
  15. Can you make another change and see if it adds 25 new apps in there again?
  16. Just ran the full update again and it dropped it back down to 202 apps, so that's very strange
  17. There is an "Updated" tag with a UNIX timestamp Ok I was confused because 25 apps were just added to the list not sure why, for some reason ones like SynaMan are showing up twice, will need to investigate
  18. Ahh, Ok, I see what you are saying now. Your beta repositories are showing now showing in the list as well, don't put the webhook on the repository if you don't want them to show in the list. *edit* Also, when the hourly scan runs it will remove those repositories if they aren't in Squids list
  19. So you are saying it's working? The ... is confusing me, lol
  20. Should be working now, if you want to test it, make a change to a template, push the change then refresh http://tools.linuxserver.io/unraid-docker-templates.json the time should update, and if you copy the time stamp and do a search on the page for that tmestamp it should show up next to your application.
  21. Shouldn't affect me. The updated timestamp is a good idea, but I can't use it to determine new / updated applications simply because the change may simply have been a spelling mistake in the description. also with timestamps , it should be made clear which format is being used.... mm/dd/yyyy is confusing for us non-american types, but if we know it's what's being used, then it's workable. if someone doesn't know and puts the date in sensible format then 11th july becomes november 7th.. etc.... It's a UNIX epoch timestamp
  22. @kode i've never used one of those and am a little confused with the settings page.... this from github... payload url is http://tools.linuxserver.io/template-update/https://github.com/sparklyballs/docker-repo/tree/templates remove the secret key and the rest is fine, just save it. The secret is if I want to verify you are allowed to send stuff to me, but then I'd have to add a key for everyone. It's not quite working yet, but it should be shortly
  23. @Squid: I've changed the feed again, sorry, it shouldn't have any effects but just in case letting you know. It now has a timestamp of the last time the feed changed "last_updated_timestamp" and a human readable version"last_updated" which is set to Europe/London. Every entry also has an Updated timestamp. @sparklyballs: I'm trying to get someone to test this for me, but if you add a webhook that goes to http://tools.linuxserver.io/template-update/your-repo-address-on-squids-list i.e. http://tools.linuxserver.io/template-update/https://github.com/sparklyballs/docker-repo/tree/templates whenever you push a change to your template on github it will trigger an update for your repo and because only 1 has changed the time for it to show up should be a few seconds.
×
×
  • Create New...