Old files remain deployed

[TysonMN]

I renamed my img folder to images. The images are now accessible via that directory, but they are still available at the previous one as well.

• New URL, expected to work and does
  • https://tysonwilliams.coding.blog/images/cb-banner-dark.svg
• Old URL, expected to 404 but doesn't
  • https://tysonwilliams.coding.blog/img/cb-banner-dark.svg

Alternatively, looking at my gh-pages branch shows both the img and images folders.

I expected old files like those in img to be deleted from gh-pages when I push to master commits that removed those files (and all the files inside them).

Is the fix to delete the pre-existing files in the run step of the GitHub deploy script?

I tried removing files from dist with the command rm -rf dist/, but my deploy fails.

[loreanvictor]

for cleaning up your gh-pages build, I suspect the cleanest way is to switch to gh-pages branch locally, remove files you do not want on the branch anymore (and ensure codedoc doesn't generate them again), and then push the branch.

on coding.blog, this is an issue and currently there is no mechanism for cleaning up old files. it is on our roadmap, so I'll keep this issue open for monitoring the release of that feature.

@must

[TysonMN]

for cleaning up your gh-pages build, I suspect the cleanest way is to switch to gh-pages branch locally, remove files you do not want on the branch anymore (and ensure codedoc doesn't generate them again), and then push the branch.

I removed all the files in the img folder of my gh-pages branch, pushed that branch, then triggered another deploy (by pushing some "no-op" change to master), but https://tysonwilliams.coding.blog/img/cb-banner-dark.svg still exists (...as long as I am not being tricked by a cache).

Whatever. I don't really like having to do that anyway. I would rather wait for an automated solution (but this might help in creating the automated solution, so I thought I would share it).

[loreanvictor]

for cleaning up your gh-pages build, I suspect the cleanest way is to switch to gh-pages branch locally, remove files you do not want on the branch anymore (and ensure codedoc doesn't generate them again), and then push the branch.

I removed all the files in the img folder of my gh-pages branch, pushed that branch, then triggered another deploy (by pushing some "no-op" change to master), but https://tysonwilliams.coding.blog/img/cb-banner-dark.svg still exists (...as long as I am not being tricked by a cache).

That solution is for your GitHub pages site not for coding.blog, which is an independent deploy. For example, while your GitHub pages deploys contents of gh-pages branch, coding.blog deploys contents of your main branch, which can be completely different.

Anyways, as mentioned before, currently there is no way to clear files from your coding.blog (but there is for GitHub pages), which is why this issue is open.

[must]

This relates to the diff system that we will implement. Then we will be able to update the published files to reflect the latest published built files (i.e. removing ones that don't result from the build any more).