Fix some bugs : update doc, codename and fix wizard (#522)

* change localhost to 127.0.0.1 + fix uninstall in wizard
* remove beta from repo

README.md

@@ -25,7 +25,7 @@
 :speech_balloon: <a href="https://gitter.im/crowdsec-project/community?utm_source=share-link&utm_medium=link&utm_campaign=share-link">Gitter Chat</a>
 </p>
 
-> Crowdsec is in BETA version. It shouldn't, and didn't crash any production so far we know, but some features might be missing or undergo evolutions. IP Blocklists are limited to very-safe-to-ban IPs only (~5% of the global database so far, will grow soon)
+> Crowdsec shouldn't, and didn't crash any production so far we know, but some features might be missing or undergo evolutions. IP Blocklists are limited to very-safe-to-ban IPs only (~5% of the global database so far, will grow soon)
 
 If you want to be notified of software **updates**, <a href="https://docs.google.com/forms/d/e/1FAIpQLSdirOC4OMYtR-HG2c54T8Ubwrq8oPLZ5k-VHOjrANip-O_KfA/viewform">click here</a>
 
@@ -151,8 +151,4 @@ This repository contains the code for the two main components of crowdsec :
  - `crowdsec` : the daemon a-la-fail2ban that can read, parse, enrich and apply heuristis to logs. This is the component in charge of "detecting" the attacks
  - `cscli` : the cli tool mainly used to interact with crowdsec : ban/unban/view current bans, enable/disable parsers and scenarios.
 
-## :warning: Beta version
-
-Please note that crowdsec is currently in beta version, use with caution !
-
 

RELEASE.json

@@ -1,3 +1,3 @@
 {
-    "CodeName": "beta"
+    "CodeName": "alphaga"
 }

config/config.yaml

@@ -35,7 +35,7 @@ api:
     credentials_path: /etc/crowdsec/local_api_credentials.yaml
   server:
     log_level: info
-    listen_uri: localhost:8080
+    listen_uri: 127.0.0.1:8080
     profiles_path: /etc/crowdsec/profiles.yaml
     online_client: # Crowdsec API credentials (to push signals and receive bad IPs)
       credentials_path: /etc/crowdsec/online_api_credentials.yaml

config/dev.yaml

@@ -31,7 +31,7 @@ api:
     credentials_path: ./config/local_api_credentials.yaml
   server:
     #insecure_skip_verify: true
-    listen_uri: localhost:8081
+    listen_uri: 127.0.0.1:8081
     profiles_path: ./config/profiles.yaml
     tls:
       #cert_file: ./cert.pem

config/local_api_credentials.yaml

@@ -1 +1 @@
-url: http://localhost:8080
+url: http://127.0.0.1:8080

config/user.yaml

@@ -31,7 +31,7 @@ api:
     credentials_path: /etc/crowdsec/local_api_credentials.yaml
   server:
     #log_level: info
-    listen_uri: localhost:8080
+    listen_uri: 127.0.0.1:8080
     profiles_path: /etc/crowdsec/profiles.yaml
     online_client: # Crowdsec API
       credentials_path: /etc/crowdsec/online_api_credentials.yaml

docs/v1.X/docs/localAPI/index.md

@@ -94,7 +94,7 @@ Then see [how to configure your crowdsec to use a remote API](/Crowdsec/v1/local
 
 #### Enable SSL
 
-The most common use case of the local API is to listen on localhost. In that case there's no need for
+The most common use case of the local API is to listen on 127.0.0.1. In that case there's no need for
 configuring any ssl layer. In some cases, the local API will listen for other crowdsec installation that
 will report its triggered scenarios. In that case, the endpoint may be configured with ssl.
 You can see how to configure SSL on your local API [here](/Crowdsec/v1/references/crowdsec-config/#tls).

docs/v1.X/docs/migration.md

@@ -69,7 +69,7 @@ $ sudo systemctl enable crowdsec
 $ sudo systemctl start crowdsec
 $ sudo cscli lapi status
 INFO[0000] Loaded credentials from /etc/crowdsec/local_api_credentials.yaml 
-INFO[0000] Trying to authenticate with username ... on http://localhost:8080/ 
+INFO[0000] Trying to authenticate with username ... on http://127.0.0.1:8080/ 
 INFO[0000] You can successfully interact with Local API (LAPI) 
 $ sudo cscli capi status
 INFO[0000] Loaded credentials from /etc/crowdsec/online_api_credentials.yaml 

docs/v1.X/docs/references/crowdsec-config.md

@@ -47,7 +47,7 @@ api:
     credentials_path: /etc/crowdsec/local_api_credentials.yaml
   server:
     log_level: info
-    listen_uri: localhost:8080
+    listen_uri: 127.0.0.1:8080
     profiles_path: /etc/crowdsec/profiles.yaml
     online_client: # Crowdsec API
       credentials_path: /etc/crowdsec/online_api_credentials.yaml

docs/v1.X/docs/user_guide/forensic_mode.md

@@ -88,7 +88,7 @@ api:
     credentials_path: /tmp/local_api_credentials.yaml
   server:
     # we edit the listen_uri so that it doesn't try to listen on the same port as the existing Local API
-    listen_uri: localhost:8081
+    listen_uri: 127.0.0.1:8081
 ```
 
 With the following edits, we ensure that :
@@ -108,7 +108,7 @@ $ cscli -c forensic.yaml machines add --auto
 INFO[0000] Machine '...' created successfully 
 INFO[0000] API credentials dumped to '/tmp/local_api_credentials.yaml' 
 $ cat /tmp/local_api_credentials.yaml
-url: http://localhost:8081
+url: http://127.0.0.1:8081
 login: ...
 password: ...
 ```

pkg/models/localapi_swagger.yaml

@@ -5,7 +5,7 @@ info:
   description: CrowdSec local API
   contact:
     email: contact@crowdsec.net
-host: localhost
+host: 127.0.0.1
 basePath: /v1
 securityDefinitions:
   JWTAuthorizer:

wizard.sh

@@ -376,7 +376,7 @@ uninstall_crowdsec() {
     rm -rf /tmp/data/
     ## end tmp
 
-    rm -rf ${CROWDSEC_PATH} || echo ""
+    find /etc/crowdsec -maxdepth 1 -mindepth 1 | grep -v "bouncer" | xargs rm -rf || echo ""
     rm -f ${CROWDSEC_LOG_FILE} || echo ""
     rm -f ${CROWDSEC_DB_PATH} || echo ""
     rm -rf ${CROWDSEC_LIB_DIR} || echo ""