mirror of
https://github.com/pi-hole/docs.git
synced 2025-12-20 03:08:45 +00:00
Merge pull request #1271 from pi-hole/remove/reconfigure
Remove old "reconfigure" option
This commit is contained in:
@@ -5,10 +5,10 @@ The standard Pi-hole customization abilities apply to this docker, but with dock
|
|||||||
!!! warning "Always Read The Release Notes!"
|
!!! warning "Always Read The Release Notes!"
|
||||||
Ensure you read the release notes for both the Docker release and the main Pi-hole component releases. This will help you avoid common problems due to known issues with upgrading or newly required arguments or variables. The release notes can be found in the respective repository for [Core](https://github.com/pi-hole/pi-hole/releases), [FTL](https://github.com/pi-hole/FTL/releases), [Web](https://github.com/pi-hole/web/releases) and [Docker](https://github.com/pi-hole/docker-pi-hole/releases).
|
Ensure you read the release notes for both the Docker release and the main Pi-hole component releases. This will help you avoid common problems due to known issues with upgrading or newly required arguments or variables. The release notes can be found in the respective repository for [Core](https://github.com/pi-hole/pi-hole/releases), [FTL](https://github.com/pi-hole/FTL/releases), [Web](https://github.com/pi-hole/web/releases) and [Docker](https://github.com/pi-hole/docker-pi-hole/releases).
|
||||||
|
|
||||||
## Upgrading / Reconfiguring
|
## Upgrading / Repairing
|
||||||
|
|
||||||
!!! Note
|
!!! Note
|
||||||
The normal Pi-hole functions to upgrade (`pihole -up`) or reconfigure (`pihole -r`) are disabled within the docker container. New images will be released, and you can upgrade by replacing your old container with a fresh upgraded image, which is more in line with the 'docker way'. Long-living docker containers are not the docker way since they aim to be portable and reproducible, why not re-create them often! Just to prove you can.
|
The normal Pi-hole functions to upgrade (`pihole -up`) or repair (`pihole -r`) are disabled within the docker container. New images will be released, and you can upgrade by replacing your old container with a fresh upgraded image, which is more in line with the 'docker way'. Long-living docker containers are not the docker way since they aim to be portable and reproducible, why not re-create them often!
|
||||||
|
|
||||||
### Docker Compose
|
### Docker Compose
|
||||||
|
|
||||||
|
|||||||
@@ -14,7 +14,7 @@ Pi-hole makes use of many commands, and here we will break down those required t
|
|||||||
| [Allowlisting, Denylisting and Regex](#allowlisting-denylisting-and-regex) | `pihole allow`, `pihole deny`, `pihole --regex`, `pihole --wild`, `pihole --allow-regex`, `pihole --allow-wild` |
|
| [Allowlisting, Denylisting and Regex](#allowlisting-denylisting-and-regex) | `pihole allow`, `pihole deny`, `pihole --regex`, `pihole --wild`, `pihole --allow-regex`, `pihole --allow-wild` |
|
||||||
| [Debugger](#debugger) | `pihole debug` |
|
| [Debugger](#debugger) | `pihole debug` |
|
||||||
| [Log Flush](#log-flush) | `pihole flush` |
|
| [Log Flush](#log-flush) | `pihole flush` |
|
||||||
| [Reconfigure](#reconfigure) | `pihole reconfigure` |
|
| [Repair](#repair) | `pihole repair` |
|
||||||
| [Tail](#tail) | `pihole tail` |
|
| [Tail](#tail) | `pihole tail` |
|
||||||
| [Set password](#password) | `pihole setpassword` |
|
| [Set password](#password) | `pihole setpassword` |
|
||||||
| [Gravity](#gravity) | `pihole updateGravity` |
|
| [Gravity](#gravity) | `pihole updateGravity` |
|
||||||
@@ -75,22 +75,19 @@ The Pi-hole debugger will attempt to diagnose any issues, and link to an FAQ wit
|
|||||||
|
|
||||||
When invoked manually, this command will allow you to empty Pi-hole's log, which is located at `/var/log/pihole/pihole.log`. The command also serves to rotate the log daily, if the `logrotate` application is installed.
|
When invoked manually, this command will allow you to empty Pi-hole's log, which is located at `/var/log/pihole/pihole.log`. The command also serves to rotate the log daily, if the `logrotate` application is installed.
|
||||||
|
|
||||||
### Reconfigure
|
### Repair
|
||||||
|
|
||||||
| | |
|
| | |
|
||||||
| -------------- | -------------- |
|
| -------------- | -------------- |
|
||||||
| Help Command | N/A |
|
| Help Command | N/A |
|
||||||
| Script Location | [`/etc/.pihole/automated install/basic-install.sh`](https://github.com/pi-hole/pi-hole/blob/master/automated%20install/basic-install.sh) |
|
| Script Location | [`/etc/.pihole/automated install/basic-install.sh`](https://github.com/pi-hole/pi-hole/blob/master/automated%20install/basic-install.sh) |
|
||||||
| Example Usage | `pihole reconfigure` |
|
| Example Usage | `pihole repair` |
|
||||||
|
|
||||||
There are times where the administrator will need to repair or reconfigure the Pi-hole installation, which is performed via this command.
|
There are times where the administrator will need to repair the Pi-hole installation, which is performed via this command.
|
||||||
|
|
||||||
**Basic Script Process**:
|
**Basic Script Process**:
|
||||||
|
|
||||||
* [`basic-install.sh`](https://github.com/pi-hole/pi-hole/blob/master/automated%20install/basic-install.sh) will be run
|
* [`basic-install.sh`](https://github.com/pi-hole/pi-hole/blob/master/automated%20install/basic-install.sh) will be run with **Repair** option, which will retain your existing settings and will attempt to repair any scripts or dependencies as necessary. The rest of `basic-install.sh` will then run as appropriate.
|
||||||
* **Reconfigure** will run through the first-time installation prompts, asking for upstream DNS provider, IP protocols, etc
|
|
||||||
* **Repair** will retain your existing settings and will attempt to repair any scripts or dependencies as necessary
|
|
||||||
* The rest of `basic-install.sh` will then run as appropriate
|
|
||||||
|
|
||||||
### Tail
|
### Tail
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user