hubcio commented on PR #2178:
URL: https://github.com/apache/iggy/pull/2178#issuecomment-3312027675

   @sobczal2 recently, we had to introduce a change in which iggy doesn't 
create root user (iggy) with default password (iggy), but some randomized 
password.
   
   due to that, if you are starting iggy-server via docker i suggest to add 
`IGGY_ROOT_USERNAME=iggy` and `IGGY_ROOT_PASSWORD=iggy`
   
   if you are starting iggy via binary, you can just call 
`target/debug/iggy-server --fresh --with-default-root-credentials`
   ```bash
     -f, --fresh
             Remove system path before starting (WARNING: THIS WILL DELETE ALL 
DATA!)
   
             This flag will completely remove the system data directory 
(local_data by default)
             before starting the server. Use this for clean development setups 
or testing.
   
             Examples:
               iggy-server --fresh                          # Start with fresh 
data directory
               iggy-server -f                               # Short form
   
         --with-default-root-credentials
             Use default root credentials (INSECURE - FOR DEVELOPMENT ONLY!)
   
             When this flag is set, the root user will be created with username 
'iggy'
             and password 'iggy' if it doesn't exist. If the root user already 
exists,
             this flag has no effect and a warning will be printed.
   
             This flag is equivalent to setting IGGY_ROOT_USERNAME=iggy and 
IGGY_ROOT_PASSWORD=iggy,
             but environment variables take precedence over this flag.
   
             WARNING: This is insecure and should only be used for development 
and testing!
   
             Examples:
               iggy-server --with-default-root-credentials     # Use 
'iggy/iggy' as root credentials
   ```
   
   i rebased your PR, let's see if CI will work


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to