sparklyballs

how am i suddenly the villain ?

I get all nervy when you start talking about new tags, adding them to 50+ xml's is a pain, lol

i hate icon mode... lol.

call it squid's fault, lol...

done....

i'll push a change in my main repo see if that's set correctly too... i'll move daapd-server from beta to main... kill 2 birds with one stone and test both.

pushed another change to the same xml , wine-box... currently working on it anyways...

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 Its sparkly's fault I'm sure. [emoji12] you've never quite gotten over that ballerina comment, have you ? lol.

edit, seeing the timestamp now..... squid's always berating me for not indenting/tabbing my code, but i'm probably the only person that finds that sh*t unreadable....

i have 3 repos in all.... main repo, beta repo are avaialble to people and are in my signature.. private repo is for stuff that is either broken or breaks other stuff, or for things i'm working on that are not even beta stage yet... that one doesn't get published publicly, a few people have it

misread the reply, put glasses on and reread. not seeing the timestamp code in the json for my app but it did pick up the changes i made, (in the changes section, lol) for wine-box.

time at the top changed when i edited a template in my beta repo....

@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 added for my beta and main repos.

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....

@kode i've never used one of those and am a little confused with the settings page.... this from github...

damn it, that's me pretty much stuck in legacy mode then, can't wait two hours (or until next cycle) to test new builds and how they load from CA. Already started the revamp to address much of this. Should be ready sometime this weekend. Or, you could do the gentlemanly thing and share. [emoji6] also i run builds on my beta repo too, sometimes needing template updates too. I know.. I know.. You are a special case.. i can't tell if you're insulting me.... lol.

damn it, that's me pretty much stuck in legacy mode then, can't wait two hours (or until next cycle) to test new builds and how they load from CA. Already started the revamp to address much of this. Should be ready sometime this weekend. Or, you could do the gentlemanly thing and share. [emoji6] also i run builds on my beta repo too, sometimes needing template updates too.

damn it, that's me pretty much stuck in legacy mode then, can't wait two hours (or until next cycle) to test new builds and how they load from CA. Already started the revamp to address much of this. Should be ready sometime this weekend. Or, you could do the gentlemanly thing and share. [emoji6] not putting my private repo out there, lol... there's stuff in there that breaks things.

damn it, that's me pretty much stuck in legacy mode then, can't wait two hours (or until next cycle) to test new builds and how they load from CA.

Truth be told, the closer I can get using dockers to be more of an appstore experience, the better off the whole thing will be. Support questions shouldn't really be on the most basic items involved in setup. If LT wants to get into the less tech savvy customers field of view, then anything that can ease them into the environment is good.

I personally do NOT agree with setting up paths like this. At this point in this experiment, I wouldn't even recommend a new user to turn the feature on. Its merely a starting point for one of the two big support problems with containers right now. Paths and Ports. Both of which are not the easiest subjects to explain to new users. This is merely one option for the problem of paths. No one can deny the ease of setting up host paths of /mnt/user. The appdata and cache only thing was really an after thought since I was modifying the template anyways. That being said, its feedback like yours that is necessary and wanted on anything like this. hear hear.. feedback is crucial..

Tried it out with that container we've been working on and here are the first results....

i'll give it a whirl in a bit....

Better question would be why when I set appdata to be /mnt/user/appdata/$APPNAME and mover moves it why do I have problems since that path is still valid regardless of whether the files are sitting on the cache drive or on the data drives. something about mover and files in use i don't know tbh...

Q why should my appdata share be cache only A because the damn mover will move files and the docker won't be able to find them... refine as appropriate, lol.