Update package-lock.json

docs/cli/commands/login.mdx

@@ -9,4 +9,7 @@ infisical login
 
 ## Description
 The CLI uses authentication to verify your identity. When you enter the correct email and password for your account, a token is generated and saved in your system Keyring to allow you to make future interactions with the CLI. 
-If you want to change where the login credentials are stored, visit the [vaults command](./vault)
+
+To change where the login credentials are stored, visit the [vaults command](./vault).
+
+If you have added multiple users, you can switch between the users by using the [user command](./user).

docs/cli/commands/user.mdx

@@ -0,0 +1,29 @@
+---
+title: "infisical user"
+description: "Manage logged in users"
+---
+
+```bash
+infisical user
+```
+
+## Description
+This command allows you to manage the current logged in users on the CLI
+
+### Sub-commands 
+<Accordion title="infisical user switch" defaultOpen="true">
+  Use this command to switch between profiles that are currently logged into the CLI 
+
+  ```bash
+  infisical user switch
+  ```
+</Accordion>
+
+<Accordion title="infisical user update domain">
+  With this command, you can modify the backend API that is utilized for all requests associated with a specific profile. 
+  For instance, you have the option to point the profile to use either the Infisical Cloud or your own self-hosted Infisical instance.
+
+  ```bash 
+  infisical user update domain
+  ```
+</Accordion>

docs/cli/faq.mdx

@@ -1,6 +1,6 @@
 ---
 title: "FAQ"
-description: "Frequently Asked Questions about Infisical"
+description: "Frequently Asked Questions about Infisical CLI"
 ---
 
 Frequently asked questions about the CLI can be found on this page. 

docs/cli/overview.mdx

@@ -109,7 +109,10 @@ infisical login
 <Accordion title="Optional: point CLI to self-hosted">
 The CLI is set to connect to Infisical Cloud by default, but if you're running your own instance of Infisical, you can direct the CLI to it using one of the methods provided below.
 
-#### Method 1: Export environment variable 
+#### Method 1: Use the updated CLI
+Beginning with CLI version V0.4.0, it is now possible to choose between logging in through the Infisical cloud or your own self-hosted instance. Simply execute the `infisical login` command and follow the on-screen instructions.
+
+#### Method 2: Export environment variable 
 You can point the CLI to the self hosted Infisical instance by exporting the environment variable `INFISICAL_API_URL` in your terminal.
 
 <Tabs>
@@ -135,7 +138,7 @@ You can point the CLI to the self hosted Infisical instance by exporting the env
   </Tab>
 </Tabs>
 
-#### Method 2: Set manually on every command
+#### Method 3: Set manually on every command
 Another option to point the CLI to your self hosted Infisical instance is to set it via a flag on every command you run.
 
 ```bash 

docs/mint.json

@@ -101,7 +101,8 @@
       "pages": [
         "self-hosting/overview",
         "self-hosting/configuration/envars",
-        "self-hosting/configuration/email"
+        "self-hosting/configuration/email",
+        "self-hosting/faq"
       ]
     },
     {
@@ -118,6 +119,7 @@
             "cli/commands/secrets",
             "cli/commands/export",
             "cli/commands/vault",
+            "cli/commands/user",
             "cli/commands/reset"
           ]
         },

docs/self-hosting/faq.mdx

@@ -0,0 +1,27 @@
+---
+title: "FAQ"
+description: "Frequently Asked Questions about Infisical self hosting"
+---
+
+Frequently asked questions about self hosted instance of Infisical can be found on this page. 
+If you can't find the answer you are looking for, please create an issue on our GitHub repository or join our Slack channel for additional support.
+
+<Accordion title="When I refresh any page, it logs me out" defaultOpen="true">
+This issue is typically seen when you haven't set up SSL for your self hosted instance of Infisical. When SSL is not enabled, you can't receive secure cookies, preventing the session data to not be saved.
+
+To fix this, we highly recommend that you set up SSL for your instance. 
+However, in the event you choose to use Infisical without SSL, you can do so by setting the `HTTPS_ENABLED` environment variable to `"false"` for the backend application.
+
+[Learn more about secure cookies](https://really-simple-ssl.com/definition/what-are-secure-cookies/)
+</Accordion>
+
+<Accordion title="Is self hosted Infisical HA?">
+ Infisical leverages the robust container orchestration capabilities of Kubernetes and the inherent high availability features of Bitnami MongoDB to ensure resilience and fault tolerance. 
+ By deploying multiple replicas of Infisical application on Kubernetes, operations can continue even if a single instance fails. 
+
+ Additionally, Bitnami MongoDB supports replica sets, which provide data redundancy and automatic failover for the underlying database. 
+ Kubernetes Services facilitate load balancing, effectively distributing traffic across your application's instances and ensuring optimal performance. 
+ The combination of Kubernetes' self-healing mechanisms and Bitnami MongoDB's failover capabilities work together to create a highly available and fault-tolerant application capable of recovering gracefully from unexpected failures.
+
+ To further increase data redundancy, we recommend that you use a managed MongoDB service for your self hosted instance of Infisical.
+</Accordion>