- User Since
- May 14 2019, 5:56 PM (14 w, 4 h)
Sun, Aug 18
I'll take this after T609 is in
Sat, Aug 17
Fri, Aug 16
I like the paper key idea, or even a set of recovery keys. Usually 8-12 random keys that the user prints or writes down. Then when needed they use one in place of a password, and are directed to set a new password. These are single use.
This was put on hold for now as the fix mentioned only allowed a single tag/category and the 3 supported feeds all allow multiple per item.
Wed, Aug 14
Looks like Category is missing from the feed Item type, there was an issue where a PR was mentioned but never opened. https://github.com/gorilla/feeds/issues/51
Mon, Aug 12
Fri, Aug 9
Fri, Aug 2
Thu, Aug 1
Mon, Jul 22
Cool, and maybe not overwrite the default if there is one. Users would likely expect when editing the config file it should retain their defaults.
Jul 21 2019
Weird I email responded but it didn't come through.
I should add that the config.ini should have a default section. i.e.
Everything still seems to be working as I remember. Can you tell me more about what isn't working like you expect?
I can double check, but I believe it was working last I tried.
Jun 26 2019
More ideas from discussion on the forum.
Jun 18 2019
taken from Z2, and trimmed/paraphrased:
Jun 15 2019
Jun 14 2019
sure, I'll add that in.
quick ascii cast demo, running on my local machine so the restart fails as it's not running.
Jun 13 2019
I guess initially just a script would work. I haven't looked yet but the a go utillity would be nice, the admin could then just have a check for updates button which could then ask to download and confirm upgrade/restart.
ok, super strange but it does work now without the collection being sent.
OK, let's revert that commit and I will test more to see what the real problem is.
Sorry I missed that part. I admit I was eager to do some work yesterday.
fixed upstream issue, v2.0.1
Jun 12 2019
Will be both, I'm thinking of loading the config at the start of each command and pass it down through calls. Some command paths may call LoadConfig 2 or 3 times which is a waste.
In progress as there is no writefreely CLI yet on that branch
in go-writeas PostParams tells JSON to ignore the Collection field
I've got a weird issue, maybe it is by design.
Jun 11 2019
I reverted the change for now, maybe we can revisit in the future but it might be a limitation of the library.
weird, it doesn't work without the flags all being listed as global. Which feels wrong as we never access global flags directly and the cli library docs do not mention anything about that working this way.
removed parent as this should not be a hard requirement but a nice to have feature
Jun 10 2019
second iteration for structure and hierarchy
Another question, do we want to have write.as as the default? as above. Or as a host like others, so we would require writefreely CLI users to either specify a host or set a default. I'm leaning towards this myself.
I've been thinking about this one this morning.
Jun 7 2019
any CLI flags provided should override the stored preferences
This task will include the full new directory structure.