- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 6 2019
Limiting customizations like this also helps people set up more simplified instances, e.g. T681: Reader-page-centric multi-user instances.
Aug 5 2019
Aug 4 2019
I agree about not wanting to have passwords in command line users' history, but I think supporting an optional password flag would be the simplest route. I'm thinking of the mysql client as an example, where you can supply -p without anything else and it'll interactively prompt for a password, or accept a password along with the flag if you want.
Aug 3 2019
One prerequisite I see for this is changing the authentication process. Currently the write.as cli asks for input in the form of the password, after you feed it a username. I'm not sure
if there's a way to provide that input from a GTK app. So, there are two options I can think of:
Aug 2 2019
Aug 1 2019
Went with ReqLog(), not InfoLog()
Pull request #148: https://github.com/writeas/writefreely/pull/148
Pull request #149: https://github.com/writeas/writefreely/pull/149
Jul 30 2019
Jul 26 2019
We decided on pherephone for the name: https://github.com/writeas/pherephone
Jul 23 2019
Jul 22 2019
Just a heads up @robjloranger: noticed a bug in WriteFreely when testing this, and fixed it in #144. Basically the full collection URL wasn't getting sent back, so after publishing I'd see /matt/new-post instead of https://team.write.as/matt/new-post
Awesome 👍
Yep, if there's already a default set when running auth it won't be overwritten. And there will be a message displayed either way. The idea with setting it that first time is to make that process more seamless, and save people some typing.
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.
Ah, gotcha. I'll add that in then.
Jul 21 2019
Weird I email responded but it didn't come through.
Right now there's no config.ini file being created in my ~/.writefreely... But it's entirely possible I messed something up. I'm looking into it now
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.
@robjloranger How does this work right now? After playing around with wf-cli this is definitely the default behavior I'd like to see, but I'm not seeing it work that way.
Just checking this off the list