When publishing a website, the dashboard will first store the website's files in the user's file system at public/Apps/appname/Published and then grab the CID of that directory and tell fission to change the site's DNSLink.
If the user then changes the content in their file system e.g. via Drive or other apps, then it can get out of sync with the actual, published site content.
Ultimately, we'd love to make the WNFS the source-of-truth for uploaded app content.
In the mean time we could implement some UI to indicate that the file system's content is not up-to-date with what's served under the app.
When publishing a website, the dashboard will first store the website's files in the user's file system at
public/Apps/appname/Publishedand then grab the CID of that directory and tell fission to change the site's DNSLink.If the user then changes the content in their file system e.g. via Drive or other apps, then it can get out of sync with the actual, published site content.
Ultimately, we'd love to make the WNFS the source-of-truth for uploaded app content.
In the mean time we could implement some UI to indicate that the file system's content is not up-to-date with what's served under the app.