I'd say yes, we should support being authenticated for multiple users on one host. So .writefreely/host/username.ini or .writefreely/host/username/config.ini. As for the location to store posts, see T584#10089.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
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 9 2019
This is dependent on backend changes (T637: Support more attributes when creating a collection).
I threw together an offline importer for this: rWFM / https://github.com/writeas/wf-migrate -- for reference in building this into the web application.
Jun 8 2019
Jun 7 2019
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.
already working
I think maybe the description for fetch should be updated.
not so much a bug as a quirk.