@thisismissem@hachyderm.io @e_nomem@hachyderm.io You could yes, presumably using a tool like rclone with them both entered as remote targets. Although... that sort of brings into question "why?". Assuming these are referring to stuff like hachyderm.io's logo, icons and other branding, wouldn't the point be to keep them separate? They aren't going to change much unlike user uploaded content. I think it'd be interesting to have some sort of version control backing your static assets. Not sure git is the answer here but presumably the workflow would be "commits a change -> approved -> some action invokes rclone to copy the newly changed asset and deploy it".
=> More informations about this toot | View the thread | More toots from puppygirlhornypost2@transfem.social
=> View thisismissem@hachyderm.io profile | View e_nomem@hachyderm.io profile
text/geminiThis content has been proxied by September (3851b).