Skip to content
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

Automatically post to social networks #96

Open
bixel opened this issue May 24, 2017 · 3 comments
Open

Automatically post to social networks #96

bixel opened this issue May 24, 2017 · 3 comments

Comments

@bixel
Copy link
Member

bixel commented May 24, 2017

We could use the Social Network APIs to post to our Facebook, XING, and LinkedIn feeds. We could add a token to the yaml head in the posts to decide which one should be shared to which network. We probably need some kind of dumb database on the server-side to prevent reposting everything while building a new version.

Just for reference:

@ccauet
Copy link
Member

ccauet commented May 26, 2017

We could use the Social Network APIs to post to our Facebook, XING, and LinkedIn feeds.

How would this be triggered? During deployment? By the CI pipeline?

We probably need some kind of dumb database on the server-side to prevent reposting everything while building a new version.

Just a txt file in the repo? Post slug + channels?

@bixel
Copy link
Member Author

bixel commented May 26, 2017

How would this be triggered? During deployment? By the CI pipeline?

My first idea would be to add a plain-text template which contains the raw post. After the CI build-stage on the master branch, this could be read by a very basic python or bash script which checks whether the filename (as the unique identifier) is contained in "the database" and if not, performs the API interaction.

Edit: ... and adds the filename to the database, of course :)

Just a txt file in the repo? Post slug + channels?

Storing e.g. the filename in a txt file should be enough.

@ccauet
Copy link
Member

ccauet commented May 26, 2017

After the CI build-stage on the master branch, this could be read by a very basic python or bash script which checks whether the filename (as the unique identifier) is contained in "the database" and if not, performs the API interaction.

Sounds reasonably simple ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants