- User Since
- May 14 2019, 5:56 PM (5 w, 6 d)
Tue, Jun 18
taken from Z2, and trimmed/paraphrased:
Sat, Jun 15
Fri, Jun 14
sure, I'll add that in.
quick ascii cast demo, running on my local machine so the restart fails as it's not running.
Thu, Jun 13
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
Wed, Jun 12
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.
Tue, Jun 11
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
Mon, Jun 10
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.
Fri, Jun 7
any CLI flags provided should override the stored preferences
This task will include the full new directory structure.
I don't think we should store the posts.json and use it for subsequent requests. For example, when would it expire? There may be more posts on the remote or something may have changed.
or re: fetch text, could just add a description text for clarification.
I think maybe the description for fetch should be updated.