Skip to content

Commit ae38bb1

Browse files
committed
including the rest of the rough draft
1 parent 1aa7bb7 commit ae38bb1

File tree

1 file changed

+18
-5
lines changed

1 file changed

+18
-5
lines changed

source/content/guides/filesystem/06-troubleshooting.md

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -53,11 +53,24 @@ Changing the file permissions to `770` from `660` via SFTP will cause a silent f
5353
### Wipe all files from environment
5454
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.
5555

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.
6174

6275
## More Resources
6376

0 commit comments

Comments
 (0)