# Removing a plugin for debugging
**URL:** https://meta.discourse.org/t/removing-a-plugin-for-debugging/323463
**Category:** Development
**Created:** [August 26, 2024, 9:05pm UTC](https://meta.discourse.org/t/removing-a-plugin-for-debugging/323463 "2024-08-26T21:05:21Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [August 26, 2024, 9:05pm UTC](https://meta.discourse.org/t/removing-a-plugin-for-debugging/323463/1 "2024-08-26T21:05:21Z")
A while ago @pfaffman showed me how to remove plugins directly via the file structure (i.e. within the container for a non-dev site) - thus markedly speeding up the debugging process when you suspect you’ve got a naughty plugin but few clues.
I remember it being something like deleting the plugin folder somewhere, but can’t recall the details. As I’m now stuck in an annoying rebuild cycle, my thoughts have drifted back to that method.
Can anyone shed some light on it?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 26, 2024, 9:10pm UTC](https://meta.discourse.org/t/removing-a-plugin-for-debugging/323463/2 "2024-08-26T21:10:35Z")
```plaintext
docker exec -it app bash
```
or
```plaintext
./launcher enter app
```
then
```plaintext
cd /var/www/discourse/plugins
rm -rf plugin-directory
sv restart unicorn
```
For each `plugin-directory` you want to get rid of.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [September 25, 2024, 9:10pm UTC](https://meta.discourse.org/t/removing-a-plugin-for-debugging/323463/3 "2024-09-25T21:10:36Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.