-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dryrun mode ? #16
Comments
Dry run mode should not post on D* neither fill the posts.txt in my opinion, the goal being just simulating sending a post. It's misleading to call an option --dry-run if it actually modifies your data, in this case your posts.txt . |
Ok, I understand your concern. |
First time I was switching from by-hand to using feedDiasp so I guess it was not really an issue. But we could definitly use an option like "--populate-db" or something to create the posts.txt with the last entries in the RSS without actually posting them on D*. Guess it could be useful while launching new instance of feedDiasp. |
I agree the option should be more explicit. to explicitly distinguish and control the behaviour. Thanks for the feedback, does everybody agree ? |
if --populate-db=True and --post-items=True, you get the normal behaviour don't you? So what's the use case for --post-items=True? I'm not sure to use a --populate-db=False and --post-items=True It's clear to me that --populate-db should not post rss entries but I'm not sure to ever use the --post-items=True if --populate-db option by itself does not post itself on D*. I' think the two following options are interesting:
|
@chaica Then |
Still a great idea to me :) |
sorry, subject still interesting, but no time to work on it properly. thanks for the feedbacks |
I plan to implement a dryrun option in order to test without posting, mainly to fill post.txt database with old articles without posting them to Diaspora.
Or maybe there is another way to achieve this ?
The text was updated successfully, but these errors were encountered: