You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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:
The text was updated successfully, but these errors were encountered: