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
Copy file name to clipboardExpand all lines: source/content/guides/filesystem/06-troubleshooting.md
+18-5Lines changed: 18 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -53,11 +53,24 @@ Changing the file permissions to `770` from `660` via SFTP will cause a silent f
53
53
### Wipe all files from environment
54
54
Sites with overpopulated or large directories may experience difficulties deleting files from particular environments. One solution is to wipe everything in the `/files` directory from an environment, keeping the database and code intact, then selectively re-upload the `/files` that need to be kept afterwards. We highly recommend this is done via a Multidev environment for better safety of the site, available to Gold+ customers, but the Dev environment can be used if Multidev is not available.
55
55
56
-
1. Create a Multidev by going to the Multidev tab of your site, and give it a name such as "file-reset".
57
-
1. If using Dev, make sure no unstaged commits are present.
58
-
2.
59
-
2. Navigate to the Database/Files tab of the Multidev, then select "Wipe"
60
-
1.
56
+
(if you are using Dev, we highly recommend creating a Backup before beginning)
57
+
58
+
1. Create a new Multidev
59
+
- It does not matter which environment you select to clone information from.
60
+
2. Navigate to the Database/Files tab of the new Multidev.
61
+
3. Navigate to the "Wipe" subtab and click on **Wipe the {env} Environment**, then fill out the confirmation modal.
62
+
- This will delete all of the environments Files and drop the Database entirely. You cannot undo this action, which is why we recommend using a Multidev.
63
+
4. Within the Multidev, navigate to Databse/Files again, then the "Clone" section.
64
+
1. Update the "From this Environment:" field to select "Live"
65
+
2. Uncheck "Clone Files"
66
+
3. Keep "Clear Caches" unchecked
67
+
4. Click the button at the bottom to begin the clone, wait for it to finish.
68
+
5. Test the fileless environment. At this point the environment should be fully functional, but have zero files associated with it.
69
+
6. At this point, you can use [SFTP + Rsync](https://docs.pantheon.io/guides/sftp/rsync-and-sftp) to upload the files you want to keep back into the Multidev.
70
+
71
+
Pantheon Notes:
72
+
- If customers wish to do this via Live, it's likely not a good idea to wipe all files then slowly replace them. [This solution is likely better](https://docs.pantheon.io/guides/sftp/rsync-and-sftp#empty-a-folder-recursively-using-rsync).
73
+
- We should clearly define a good use case for this workflow, such as testing if files are a problem.
0 commit comments