insanity54 / futureporn

Unofficial ProjektMelody Chaturbate VOD Archive. For Adults Only.
https://futureporn.net
26 stars 3 forks source link

Strapi Content Types data sources are not reactive #174

Closed insanity54 closed 1 year ago

insanity54 commented 1 year ago

Inspired by the Mux plugin for Strapi which deletes the Mux Asset (on Mux's servers) when deleted in Strapi, I think the "correct way" to implement content types in strapi is to have them behave similarly, with the backing data structure tightly linked to the content type in Strapi.

Example. vod.videoSrcHash is a text field. It can be updated and deleted and nothing happens in IPFS world.

Ideally, adding text to vod.videoSrcHash would trigger an IPFS add/pin in the IPFS cluster, without the admin having to do that themselves, or a QA server handling said pin or add.

Similarly, deleting the text from vod.videoSrcHash would remove the IPFS pin from the cluster.

I think this would require a custom Strapi content type which has hooks like beforeUpdate, beforeDelete, etc. There could also be fields in this content type which show status of the CID. status: PINNED|PINNING|PENDING, etc., things that are normally only visible via IPFS cluster CLI.

I think this is an ideal setup and I will go in the direction of implementing this.

insanity54 commented 1 year ago

moved to https://github.com/futureporn/futureporn-strapi/issues/5