increase chart version

backend/src/ee/controllers/v1/secretApprovalRequestsController.ts

@@ -17,12 +17,12 @@ export const getSecretApprovalRequestCount = async (req: Request, res: Response)
   } = await validateRequest(reqValidator.getSecretApprovalRequestCount, req);
 
   if (!(req.authData.authPayload instanceof User)) return;
-
+  
   const membership = await Membership.findOne({
     user: req.authData.authPayload._id,
     workspace: new Types.ObjectId(workspaceId)
   });
-
+  
   if (!membership) throw UnauthorizedRequestError();
 
   const approvalRequestCount = await SecretApprovalRequest.aggregate([
@@ -73,12 +73,12 @@ export const getSecretApprovalRequests = async (req: Request, res: Response) =>
   } = await validateRequest(reqValidator.getSecretApprovalRequests, req);
 
   if (!(req.authData.authPayload instanceof User)) return;
-
+  
   const membership = await Membership.findOne({
     user: req.authData.authPayload._id,
     workspace: new Types.ObjectId(workspaceId)
   });
-
+  
   if (!membership) throw UnauthorizedRequestError();
 
   const query = {
@@ -168,13 +168,13 @@ export const getSecretApprovalRequestDetails = async (req: Request, res: Respons
     user: req.authData.authPayload._id,
     workspace: secretApprovalRequest.workspace
   });
-
+  
   if (!membership) throw UnauthorizedRequestError();
 
   // allow to fetch only if its admin or is the committer or approver
   if (
     membership.role !== "admin" &&
-    !secretApprovalRequest.committer.equals(membership.id) &&
+    secretApprovalRequest.committer !== membership.id &&
     !secretApprovalRequest.policy.approvers.find(
       (approverId) => approverId.toString() === membership._id.toString()
     )
@@ -215,7 +215,7 @@ export const updateSecretApprovalReviewStatus = async (req: Request, res: Respon
     user: req.authData.authPayload._id,
     workspace: secretApprovalRequest.workspace
   });
-
+  
   if (!membership) throw UnauthorizedRequestError();
 
   if (
@@ -257,7 +257,7 @@ export const mergeSecretApprovalRequest = async (req: Request, res: Response) =>
     user: req.authData.authPayload._id,
     workspace: secretApprovalRequest.workspace
   });
-
+  
   if (!membership) throw UnauthorizedRequestError();
 
   if (
@@ -307,7 +307,7 @@ export const updateSecretApprovalRequestStatus = async (req: Request, res: Respo
     user: req.authData.authPayload._id,
     workspace: secretApprovalRequest.workspace
   });
-
+  
   if (!membership) throw UnauthorizedRequestError();
 
   if (

backend/src/ee/models/auditLog/enums.ts

@@ -8,10 +8,7 @@ export enum UserAgentType {
   WEB = "web",
   CLI = "cli",
   K8_OPERATOR = "k8-operator",
-  TERRAFORM = "terraform",
-  OTHER = "other",
-  PYTHON_SDK = "InfisicalPythonSDK",
-  NODE_SDK = "InfisicalNodeSDK"
+  OTHER = "other"
 }
 
 export enum EventType {

backend/src/helpers/rateLimiter.ts

@@ -10,7 +10,7 @@ export const apiLimiter = rateLimit({
   //   errorHandler: console.error.bind(null, 'rate-limit-mongo')
   // }),
   windowMs: 60 * 1000,
-  max: 480,
+  max: 350,
   standardHeaders: true,
   legacyHeaders: false,
   skip: (request) => {
@@ -30,7 +30,7 @@ const authLimit = rateLimit({
   //   collectionName: "expressRateRecords-authLimit",
   // }),
   windowMs: 60 * 1000,
-  max: 300,
+  max: 100,
   standardHeaders: true,
   legacyHeaders: false,
   keyGenerator: (req, res) => {
@@ -46,8 +46,8 @@ export const passwordLimiter = rateLimit({
   //   errorHandler: console.error.bind(null, 'rate-limit-mongo'),
   //   collectionName: "expressRateRecords-passwordLimiter",
   // }),
-  windowMs: 60 * 1000,
-  max: 300,
+  windowMs: 60 * 60 * 1000,
+  max: 10,
   standardHeaders: true,
   legacyHeaders: false,
   keyGenerator: (req, res) => {

backend/src/utils/posthog.ts

@@ -7,14 +7,8 @@ export const getUserAgentType = function (userAgent: string | undefined) {
     return UserAgentType.CLI;
   } else if (userAgent == UserAgentType.K8_OPERATOR) {
     return UserAgentType.K8_OPERATOR;
-  } else if (userAgent == UserAgentType.TERRAFORM) {
-    return UserAgentType.TERRAFORM;
   } else if (userAgent.toLowerCase().includes("mozilla")) {
     return UserAgentType.WEB;
-  } else if (userAgent.includes(UserAgentType.NODE_SDK)) {
-    return UserAgentType.NODE_SDK;
-  } else if (userAgent.includes(UserAgentType.PYTHON_SDK)) {
-    return UserAgentType.PYTHON_SDK;
   } else {
     return UserAgentType.OTHER;
   }

backend/src/validation/serviceTokenData.ts

@@ -158,7 +158,7 @@ export const CreateServiceTokenV2 = z.object({
     encryptedKey: z.string().trim(),
     iv: z.string().trim(),
     tag: z.string().trim(),
-    expiresIn: z.number().nullable().optional(),
+    expiresIn: z.number(),
     permissions: z.enum(["read", "write"]).array()
   })
 });

cli/packages/cmd/export.go

@@ -102,7 +102,7 @@ var exportCmd = &cobra.Command{
 
 		fmt.Print(output)
 
-		// Telemetry.CaptureEvent("cli-command:export", posthog.NewProperties().Set("secretsCount", len(secrets)).Set("version", util.CLI_VERSION))
+		Telemetry.CaptureEvent("cli-command:export", posthog.NewProperties().Set("secretsCount", len(secrets)).Set("version", util.CLI_VERSION))
 	},
 }
 

docs/documentation/platform/sso/azure.mdx

@@ -10,97 +10,97 @@ description: "Configure Azure SAML for Infisical SSO"
    then you should contact team@infisical.com to purchase an enterprise license to use it.
 </Info>
 
-<Steps>
-   <Step title="Prepare the SAML SSO configuration in Infisical">
-      In Infisical, head over to your organization Settings > Authentication > SAML SSO Configuration and select **Set up SAML SSO**.
+1. In Infisical, head over to your organization Settings > Authentication > SAML SSO Configuration and select **Set up SAML SSO**.
+   Next, copy the **Reply URL (Assertion Consumer Service URL)** and **Identifier (Entity ID)** to use when configuring the Azure SAML application.
 
-      Next, copy the **Reply URL (Assertion Consumer Service URL)** and **Identifier (Entity ID)** to use when configuring the Azure SAML application.
+![Azure SAML initial configuration](../../../images/sso/azure/init-config.png)
 
-      ![Azure SAML initial configuration](../../../images/sso/azure/init-config.png)
-   </Step>
-   <Step title="Create a SAML application in Azure">
-      In the Azure Portal, navigate to the Azure Active Directory and select **Enterprise applications**. On this screen, select **+ New application**.
+2. In the Azure Portal, navigate to the Azure Active Directory and select **Enterprise applications**. On this screen, select
+   **+ New application**.
 
-      ![Azure SAML enterprise applications](../../../images/sso/azure/enterprise-applications.png)
+![Azure SAML enterprise applications](../../../images/sso/azure/enterprise-applications.png)
 
-      ![Azure SAML new application](../../../images/sso/azure/new-application.png)
-      
-      On the next screen, press the **+ Create your own application** button.
-      Give the application a unique name like Infisical; choose the "Integrate any other application you don't find in the gallery (Non-gallery)"
-      option and hit the **Create** button.
+![Azure SAML new application](../../../images/sso/azure/new-application.png)
 
-      ![Azure SAML create own application](../../../images/sso/azure/create-own-application.png)
+2. On the next screen, press the **+ Create your own application** button.
+   Give the application a unique name like Infisical; choose the "Integrate any other application you don't find in the gallery (Non-gallery)"
+   option and hit the **Create** button.
 
-      On the application overview screen, select **Single sign-on** from the left sidebar. From there, select the **SAML** single sign-on method.
+![Azure SAML create own application](../../../images/sso/azure/create-own-application.png)
 
-      ![Azure SAML sign on method](../../../images/sso/azure/sso-method.png)
+3. On the application overview screen, select **Single sign-on** from the left sidebar. From there,
+   select the **SAML** single sign-on method.
 
-      Next, select **Edit** in the **Basic SAML Configuration** section and add/set the **Identifier (Entity ID)** to **Entity ID** and add/set the **Reply URL (Assertion Consumer Service URL)** to **ACS URL** from step 1.
+![Azure SAML sign on method](../../../images/sso/azure/sso-method.png)
 
-      ![Azure SAML edit basic configuration](../../../images/sso/azure/edit-basic-config.png)
+4. Next, select **Edit** in the **Basic SAML Configuration** section and add/set the **Identifier (Entity ID)**
+   to **Entity ID** and add/set the **Reply URL (Assertion Consumer Service URL)** to **ACS URL** from step 1.
 
-      ![Azure SAML edit basic configuration 2](../../../images/sso/azure/edit-basic-config-2.png)
+![Azure SAML edit basic configuration](../../../images/sso/azure/edit-basic-config.png)
 
-      <Note>
-      If you're self-hosting Infisical, then you will want to replace
-      `https://app.infisical.com` with your own domain.
-      </Note>
+![Azure SAML edit basic configuration 2](../../../images/sso/azure/edit-basic-config-2.png)
 
-      Back in the **Set up Single Sign-On with SAML** screen, select **Edit** in the **Attributes & Claims** section and configure the following map:
+<Note>
+  If you're self-hosting Infisical, then you will want to replace
+  `https://app.infisical.com` with your own domain.
+</Note>
 
-      - `email -> user.userprinciplename`
-      - `firstName -> user.firstName`
-      - `lastName -> user.lastName`
+5. Back in the **Set up Single Sign-On with SAML** screen, select **Edit** in the **Attributes & Claims** section and configure the following map:
 
-      ![Azure SAML edit attributes and claims](../../../images/sso/azure/edit-attributes-claims.png)
+- `email -> user.userprinciplename`
+- `firstName -> user.firstName`
+- `lastName -> user.lastName`
 
-      ![Azure SAML edit attributes and claims 2](../../../images/sso/azure/edit-attributes-claims-2.png)
+![Azure SAML edit attributes and claims](../../../images/sso/azure/edit-attributes-claims.png)
 
-      Back in the **Set up Single Sign-On with SAML** screen, select **Edit** in the **SAML Certificates** section and set the **Signing Option** field to **Sign SAML response and assertion**.
+![Azure SAML edit attributes and claims 2](../../../images/sso/azure/edit-attributes-claims-2.png)
 
-      ![Azure SAML edit certificate](../../../images/sso/azure/edit-saml-certificate.png)
+6. Back in the **Set up Single Sign-On with SAML** screen, select **Edit** in the **SAML Certificates** section and set the **Signing Option** field to **Sign SAML response and assertion**.
 
-      ![Azure SAML edit certificate signing option](../../../images/sso/azure/edit-saml-certificate-2.png)
-   </Step>
-   <Step title="Retrieve Identity Provider (IdP) Information from Okta">
-      In the **Set up Single Sign-On with SAML** screen, copy the **Login URL** and **SAML Certificate** to use when finishing configuring Azure SAML in Infisical.
+![Azure SAML edit certificate](../../../images/sso/azure/edit-saml-certificate.png)
 
-      ![Azure SAML identity provider values 1](../../../images/sso/azure/idp-values.png)
+![Azure SAML edit certificate signing option](../../../images/sso/azure/edit-saml-certificate-2.png)
 
-      In the **Properties** screen, copy the **Application ID** to use when finishing configuring Azure SAML in Infisical.
+7. Get IdP values:
 
-      ![Azure SAML identity provider values 2](../../../images/sso/azure/idp-values-2.png)
-   </Step>
-   <Step title="Finish configuring SAML in Infisical">
-      Back in Infisical, set **Login URL**, **Azure Application ID**, and **SAML Certificate** from step 3. Once you've done that, press **Update** to complete the required configuration.
+In the **Set up Single Sign-On with SAML** screen, copy the **Login URL** and **SAML Certificate** to use when finishing configuring Azure SAML in Infisical.
 
-      ![Azure SAML paste identity provider values](../../../images/sso/azure/idp-values-3.png)
+![Azure SAML identity provider values 1](../../../images/sso/azure/idp-values.png)
 
-      <Note>
-      When pasting the certificate into Infisical, you'll want to retain `-----BEGIN
-      CERTIFICATE-----` and `-----END CERTIFICATE-----` at the first and last line
-      of the text area respectively.
+In the **Properties** screen, copy the **Application ID** to use when finishing configuring Azure SAML in Infisical.
 
-      Having trouble?, try copying the X509 certificate information from the Federation Metadata XML file in Azure.
+![Azure SAML identity provider values 2](../../../images/sso/azure/idp-values-2.png)
 
-      </Note>
-   </Step>
-   <Step title="Assign users in Azure to the application">
-      Back in Azure, navigate to the **Users and groups** tab and select **+ Add user/group** to assign access to the login with SSO application on a user or group-level.
-      
-      ![Azure SAML assignment](../../../images/sso/azure/assignment.png)
-   </Step>   
-   <Step title="Enable SAML SSO in Infisical">
-      Enabling SAML SSO enforces all members in your organization to only be able to log into Infisical via Azure.
+Back in Infisical, set **Login URL**, **Azure Application ID**, and **SAML Certificate** from above. Once you've done that, press **Update** to complete the required configuration.
 
-      ![Azure SAML assignment](../../../images/sso/azure/enable-saml.png)
-   </Step>
-</Steps>
+![Azure SAML paste identity provider values](../../../images/sso/azure/idp-values-3.png)
+
+<Note>
+When pasting the certificate into Infisical, you'll want to retain `-----BEGIN
+  CERTIFICATE-----` and `-----END CERTIFICATE-----` at the first and last line
+  of the text area respectively.
+
+Having trouble?, try copying the X509 certificate information from the Federation Metadata XML file in Azure.
+
+</Note>
+
+7. Assignments
+
+Back in Azure, navigate to the **Users and groups** tab and select **+ Add user/group** to assign access to the login with SSO application on a user or group-level.
+![Azure SAML assignment](../../../images/sso/azure/assignment.png)
+
+8. Return to Infisical and enable SAML SSO.
+
+Enabling SAML SSO enforces all members in your organization to only be able to log into Infisical via Azure.
+
+![Azure SAML assignment](../../../images/sso/azure/enable-saml.png)
 
 <Note>
    If you're configuring SAML SSO on a self-hosted instance of Infisical, make sure to
-   set the `AUTH_SECRET` and `SITE_URL` environment variable for it to work:
+   set the `JWT_PROVIDER_AUTH_SECRET` and `SITE_URL` environment variable for it to work:
    
-   - `AUTH_SECRET`: A secret key used for signing and verifying JWT. This can be a random 32-byte base64 string generated with `openssl rand -base64 32`.
+   - `JWT_PROVIDER_AUTH_SECRET`: This is secret key used for signing and verifying JWT. This could be a randomly-generated 256-bit hex string.
    - `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
-</Note>
+</Note>
+
+

docs/documentation/platform/sso/github.mdx

@@ -5,39 +5,38 @@ description: "Configure GitHub SSO for Infisical"
 
 Using GitHub SSO on a self-hosted instance of Infisical requires configuring an OAuth2 application in GitHub and registering your instance with it.
 
-<Steps>
-  <Step title="Create an OAuth application in GitHub">
-    Navigate to your user Settings > Developer settings > OAuth Apps to create a new GitHub OAuth application.
+## Create an OAuth application in GitHub
 
-    ![GitHub settings](../../../images/sso/github/settings.png)
-    ![GitHub developer settings](../../../images/sso/github/dev-settings.png)
-    ![GitHub create new OAuth application](../../../images/sso/github/new-app.png)
+Navigate to your user Settings > Developer settings > OAuth Apps to create a new GitHub OAuth application.
 
-    Create the OAuth application. As part of the form, set the **Homepage URL** to your self-hosted domain `https://your-domain.com`
-    and the **Authorization callback URL** to `https://your-domain.com/api/v1/sso/github`.
+![GitHub settings](../../../images/sso/github/settings.png)
+![GitHub developer settings](../../../images/sso/github/dev-settings.png)
+![GitHub create new OAuth application](../../../images/sso/github/new-app.png)
 
-    ![GitHub create new OAuth application form](../../../images/sso/github/new-app-form.png)
+Create the OAuth application. As part of the form, set the **Homepage URL** to your self-hosted domain `https://your-domain.com`
+and the **Authorization callback URL** to `https://your-domain.com/api/v1/sso/github`.
 
-    <Note>
-        If you have a GitHub organization, you can create an OAuth application under it
-        in your organization Settings > Developer settings > OAuth Apps > New Org OAuth App.
-    </Note>
-  </Step>
-  <Step title="Add your OAuth application credentials to Infisical">
-    Obtain the **Client ID** and generate a new **Client Secret** for your GitHub OAuth application.
+![GitHub create new OAuth application form](../../../images/sso/github/new-app-form.png)
 
-    ![GCP obtain OAuth2 credentials](../../../images/sso/github/credentials.png)
+<Note>
+    If you have a GitHub organization, you can create an OAuth application under it
+    in your organization Settings > Developer settings > OAuth Apps > New Org OAuth App.
+</Note>
 
-    Back in your Infisical instance, make sure to set the following environment variables:
+## Add your OAuth application credentials to Infisical
 
-    - `CLIENT_ID_GITHUB_LOGIN`: The **Client ID** of your GitHub OAuth application.
-    - `CLIENT_SECRET_GITHUB_LOGIN`: The **Client Secret** of your GitHub OAuth application.
-    - `AUTH_SECRET`: A secret key used for signing and verifying JWT. This can be a random 32-byte base64 string generated with `openssl rand -base64 32`.
-    - `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
-      
-    Once added, restart your Infisical instance and log in with GitHub.
-  </Step>
-</Steps>
+Obtain the **Client ID** and generate a new **Client Secret** for your GitHub OAuth application.
+
+![GCP obtain OAuth2 credentials](../../../images/sso/github/credentials.png)
+
+Back in your Infisical instance, make sure to set the following environment variables:
+
+- `CLIENT_ID_GITHUB_LOGIN`: The **Client ID** of your GitHub OAuth application.
+- `CLIENT_SECRET_GITHUB_LOGIN`: The **Client Secret** of your GitHub OAuth application.
+- `JWT_PROVIDER_AUTH_SECRET`: A secret key used for signing and verifying JWT. This could be a randomly-generated 256-bit hex string.
+- `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
+   
+Once added, restart your Infisical instance and log in with GitHub.
 
 ## FAQ
 
@@ -46,7 +45,7 @@ Using GitHub SSO on a self-hosted instance of Infisical requires configuring an
     It is likely that you have misconfigured your self-hosted instance of Infisical. You should:
 
     - Check that you have set the `CLIENT_ID_GITHUB_LOGIN`, `CLIENT_SECRET_GITHUB_LOGIN`, 
-    `AUTH_SECRET`, and `SITE_URL` environment variables.
+    `JWT_PROVIDER_AUTH_SECRET`, and `SITE_URL` environment variables.
     - Check that the **Authorization callback URL** specified in GitHub matches the `SITE_URL` environment variable.
     For example, if the former is `https://app.infisical.com/api/v1/sso/github` then the latter should be `https://app.infisical.com`.
   </Accordion>

docs/documentation/platform/sso/gitlab.mdx

@@ -5,39 +5,38 @@ description: "Configure GitLab SSO for Infisical"
 
 Using GitLab SSO on a self-hosted instance of Infisical requires configuring an OAuth application in GitLab and registering your instance with it.
 
-<Steps>
-  <Step title="Create an OAuth application in GitLab">
-    Navigate to your user Settings > Applications to create a new GitLab application.
+## Create an OAuth application in GitLab
 
-    ![sso gitlab config](/images/sso/gitlab/edit-profile.png) 
-    ![sso gitlab config](/images/sso/gitlab/new-app.png) 
+Navigate to your user Settings > Applications to create a new GitLab application.
 
-    Create the application. As part of the form, set the **Redirect URI** to `https://your-domain.com/api/v1/sso/gitlab`.
-    Note that only `read_user` is required as part of the **Scopes** configuration.
+![sso gitlab config](/images/sso/gitlab/edit-profile.png) 
+![sso gitlab config](/images/sso/gitlab/new-app.png) 
 
-    ![sso gitlab config](/images/sso/gitlab/new-app-form.png) 
+Create the application. As part of the form, set the **Redirect URI** to `https://your-domain.com/api/v1/sso/gitlab`.
+Note that only `read_user` is required as part of the **Scopes** configuration.
 
-    <Note>
-        If you have a GitLab group, you can create an OAuth application under it
-        in your group Settings > Applications.
-    </Note>
-  </Step>
-  <Step title="Add your OAuth application credentials to Infisical">
-    Obtain the **Application ID** and **Secret** for your GitLab application.
+![sso gitlab config](/images/sso/gitlab/new-app-form.png) 
 
-    ![sso gitlab config](/images/sso/gitlab/credentials.png) 
+<Note>
+    If you have a GitLab group, you can create an OAuth application under it
+    in your group Settings > Applications.
+</Note>
 
-    Back in your Infisical instance, make sure to set the following environment variables:
+## Add your OAuth application credentials to Infisical
 
-    - `CLIENT_ID_GITLAB_LOGIN`: The **Client ID** of your GitLab application.
-    - `CLIENT_SECRET_GITLAB_LOGIN`: The **Secret** of your GitLab application.
-    - (optional) `URL_GITLAB_LOGIN`: The URL of your self-hosted instance of GitLab where the OAuth application is registered. If no URL is passed in, this will default to `https://gitlab.com`.
-    - `AUTH_SECRET`: A secret key used for signing and verifying JWT. This can be a random 32-byte base64 string generated with `openssl rand -base64 32`.
-    - `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
-      
-    Once added, restart your Infisical instance and log in with GitLab.
-  </Step>
-</Steps>
+Obtain the **Application ID** and **Secret** for your GitLab application.
+
+![sso gitlab config](/images/sso/gitlab/credentials.png) 
+
+Back in your Infisical instance, make sure to set the following environment variables:
+
+- `CLIENT_ID_GITLAB_LOGIN`: The **Client ID** of your GitLab application.
+- `CLIENT_SECRET_GITLAB_LOGIN`: The **Secret** of your GitLab application.
+- (optional) `URL_GITLAB_LOGIN`: The URL of your self-hosted instance of GitLab where the OAuth application is registered. If no URL is passed in, this will default to `https://gitlab.com`.
+- `JWT_PROVIDER_AUTH_SECRET`: A secret key used for signing and verifying JWT. This could be a randomly-generated 256-bit hex string.
+- `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
+   
+Once added, restart your Infisical instance and log in with GitLab.
 
 ## FAQ
 
@@ -46,7 +45,7 @@ Using GitLab SSO on a self-hosted instance of Infisical requires configuring an
     It is likely that you have misconfigured your self-hosted instance of Infisical. You should:
 
     - Check that you have set the `CLIENT_ID_GITLAB_LOGIN`, `CLIENT_SECRET_GITLAB_LOGIN`, 
-    `AUTH_SECRET`, and `SITE_URL` environment variables.
+    `JWT_PROVIDER_AUTH_SECRET`, and `SITE_URL` environment variables.
     - Check that the **Redirect URI** specified in GitLab matches the `SITE_URL` environment variable.
     For example, if the former is `https://app.infisical.com/api/v1/sso/gitlab` then the latter should be `https://app.infisical.com`.
   </Accordion>

docs/documentation/platform/sso/google.mdx

@@ -5,32 +5,31 @@ description: "Configure Google SSO for Infisical"
 
 Using Google SSO on a self-hosted instance of Infisical requires configuring an OAuth2 application in GCP and registering your instance with it.
 
-<Steps>
-  <Step title="Create an OAuth2 application in GCP">
-    Navigate to your project API & Services > Credentials to create a new OAuth2 application.
-        
-    ![GCP API services](../../../images/sso/google/api-services.png)
-    ![GCP create new OAuth2 application](../../../images/sso/google/new-app.png)
+## Create an OAuth2 application in GCP
 
-    Create the application. As part of the form, add to **Authorized redirect URIs**: `https://your-domain.com/api/v1/sso/google`.
+Navigate to your project API & Services > Credentials to create a new OAuth2 application.
+    
+![GCP API services](../../../images/sso/google/api-services.png)
+![GCP create new OAuth2 application](../../../images/sso/google/new-app.png)
 
-    ![GCP create new OAuth2 application form](../../../images/sso/google/new-app-form.png)
-  </Step>
-  <Step title="Add your OAuth2 application credentials to Infisical">
-    Obtain the **Client ID** and **Client Secret** for your GCP OAuth2 application.
+Create the application. As part of the form, add to **Authorized redirect URIs**: `https://your-domain.com/api/v1/sso/google`.
 
-    ![GCP obtain OAuth2 credentials](../../../images/sso/google/credentials.png)
-      
-    Back in your Infisical instance, make sure to set the following environment variables:
+![GCP create new OAuth2 application form](../../../images/sso/google/new-app-form.png)
 
-    - `CLIENT_ID_GOOGLE_LOGIN`: The **Client ID** of your GCP OAuth2 application.
-    - `CLIENT_SECRET_GOOGLE_LOGIN`: The **Client Secret** of your GCP OAuth2 application.
-    - `AUTH_SECRET`: A secret key used for signing and verifying JWT. This can be a random 32-byte base64 string generated with `openssl rand -base64 32`.
-    - `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
-      
-    Once added, restart your Infisical instance and log in with Google
-  </Step>
-</Steps>
+## Add your OAuth2 application credentials to Infisical
+   
+Obtain the **Client ID** and **Client Secret** for your GCP OAuth2 application.
+
+![GCP obtain OAuth2 credentials](../../../images/sso/google/credentials.png)
+   
+Back in your Infisical instance, make sure to set the following environment variables:
+
+- `CLIENT_ID_GOOGLE_LOGIN`: The **Client ID** of your GCP OAuth2 application.
+- `CLIENT_SECRET_GOOGLE_LOGIN`: The **Client Secret** of your GCP OAuth2 application.
+- `JWT_PROVIDER_AUTH_SECRET`: A secret key used for signing and verifying JWT. This could be a randomly-generated 256-bit hex string.
+- `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
+   
+Once added, restart your Infisical instance and log in with Google
 
 ## FAQ
 
@@ -39,7 +38,7 @@ Using Google SSO on a self-hosted instance of Infisical requires configuring an
     It is likely that you have misconfigured your self-hosted instance of Infisical. You should:
 
     - Check that you have set the `CLIENT_ID_GOOGLE_LOGIN`, `CLIENT_SECRET_GOOGLE_LOGIN`, 
-    `AUTH_SECRET`, and `SITE_URL` environment variables.
+    `JWT_PROVIDER_AUTH_SECRET`, and `SITE_URL` environment variables.
     - Check that the **Authorized redirect URI** specified in GCP matches the `SITE_URL` environment variable.
     For example, if the former is `https://app.infisical.com/api/v1/sso/google` then the latter should be `https://app.infisical.com`.
   </Accordion>

docs/documentation/platform/sso/jumpcloud.mdx

@@ -10,77 +10,73 @@ description: "Configure JumpCloud SAML for Infisical SSO"
    then you should contact team@infisical.com to purchase an enterprise license to use it.
 </Info>
 
-<Steps>
-   <Step title="Prepare the SAML SSO configuration in Infisical">
-      In Infisical, head over to your organization Settings > Authentication > SAML SSO Configuration and select **Set up SAML SSO**.
+1. In Infisical, head over to your organization Settings > Authentication > SAML SSO Configuration and select **Set up SAML SSO**.
+   Next, copy the **ACS URL** and **SP Entity ID** to use when configuring the JumpCloud SAML application.
 
-      Next, copy the **ACS URL** and **SP Entity ID** to use when configuring the JumpCloud SAML application.
+![JumpCloud SAML initial configuration](../../../images/sso/jumpcloud/init-config.png)
 
-      ![JumpCloud SAML initial configuration](../../../images/sso/jumpcloud/init-config.png)
-   </Step>
-   <Step title="Create a SAML application in JumpCloud">
-      2.1. In the JumpCloud Admin Portal, navigate to User Authentication > SSO and create an application. If this is your first application, select **Get Started**; if not, select **+Add New Application**
+2. In the JumpCloud Admin Portal, navigate to User Authentication > SSO and create an application. If this is your first application, select **Get Started**;
+   if not, select **+Add New Application**
 
-      ![JumpCloud SAML new application](../../../images/sso/jumpcloud/new-application.png)
+![JumpCloud SAML new application](../../../images/sso/jumpcloud/new-application.png)
 
-      2.2. Next, select **Custom SAML App** to open up the **New SSO** dialog.
+3. Next, select **Custom SAML App** to open up the **New SSO** dialog.
 
-      ![JumpCloud custom SAML app](../../../images/sso/jumpcloud/custom-saml-app.png)
+![JumpCloud custom SAML app](../../../images/sso/jumpcloud/custom-saml-app.png)
 
-      2.3. In the **General Info** tab, give the application a unique name like Infisical.
+4. In the **General Info** tab, give the application a unique name like Infisical.
 
-      ![JumpCloud general info](../../../images/sso/jumpcloud/general-info.png)
+![JumpCloud general info](../../../images/sso/jumpcloud/general-info.png)
 
-      2.4. In the **SSO** tab, set the **SP Entity ID** and **ACS URL** from step 1; set the **IdP Entity ID** to the same value as the **SP Entity ID**.
+5. In the **SSO** tab, set the **SP Entity ID** and **ACS URL** from step 1; set the **IdP Entity ID** to the same value as the **SP Entity ID**.
 
-      ![JumpCloud edit basic config](../../../images/sso/jumpcloud/edit-basic-config.png)
+![JumpCloud edit basic config](../../../images/sso/jumpcloud/edit-basic-config.png)
 
-      2.5. On the same tab, check the **Sign Assertion** checkbox and fill the **IDP URL** to something unique.
-         Copy the **IDP URL** to use when finishing configuring the JumpCloud SAML in Infisical.
+6. On the same tab, check the **Sign Assertion** checkbox and fill the **IDP URL** to something unique.
+   Copy the **IDP URL** to use when finishing configuring the JumpCloud SAML in Infisical.
 
-      ![JumpCloud edit basic config 2](../../../images/sso/jumpcloud/edit-basic-config-2.png)
+![JumpCloud edit basic config 2](../../../images/sso/jumpcloud/edit-basic-config-2.png)
 
-      2.6. On the same tab, in the **Attributes** section, configure the following map:
+7. On the same tab, in the **Attributes** section, configure the following map:
 
-      - `email -> email`
-      - `firstName -> firstname`
-      - `lastName -> lastname`
+- `email -> email`
+- `firstName -> firstname`
+- `lastName -> lastname`
 
-      ![JumpCloud attribute statements](../../../images/sso/jumpcloud/attribute-statements.png)
+![JumpCloud attribute statements](../../../images/sso/jumpcloud/attribute-statements.png)
 
-      Finally press activate to create the SAML application.
+Finally press activate to create the SAML application.
 
-      2.7. Next, select the newly created SAML application and select **Download certificate** under the **IDP Certificate Valid** dropdown
+8. Next, select the newly created SAML application and select **Download certificate** under the **IDP Certificate Valid** dropdown
 
-      ![JumpCloud download certificate](../../../images/sso/jumpcloud/download-saml-certificate.png)
-   </Step>
-   <Step title="Finish configuring SAML in Infisical">
-      Back in Infisical, set the **IDP URL** from step 2.5 and the **IdP Entity ID** from step 2.4. Also, paste the certificate from the previous step.
+![JumpCloud download certificate](../../../images/sso/jumpcloud/download-saml-certificate.png)
 
-      ![JumpCloud IdP values](../../../images/sso/jumpcloud/idp-values.png)
+9. Back in Infisical, set the **IDP URL** from step 6 and the **IdP Entity ID** from step 5. Also, paste the certificate from the previous step.
 
-      <Note>
-         When pasting the certificate into Infisical, you'll want to retain `-----BEGIN
-         CERTIFICATE-----` and `-----END CERTIFICATE-----` at the first and last line
-         of the text area respectively.
-      </Note>
-   </Step>
-   <Step title="Assign users in JumpCloud to the application">
-      Back in JumpCloud, navigate to the **User Groups** tab and assign users to the newly created application.
+![JumpCloud IdP values](../../../images/sso/jumpcloud/idp-values.png)
 
-      ![JumpCloud SAML assignment](../../../images/sso/jumpcloud/assignment.png)
-   </Step>
-   <Step title="Enable SAML SSO in Infisical">
-      Enabling SAML SSO enforces all members in your organization to only be able to log into Infisical via JumpCloud.
+<Note>
+  When pasting the certificate into Infisical, you'll want to retain `-----BEGIN
+  CERTIFICATE-----` and `-----END CERTIFICATE-----` at the first and last line
+  of the text area respectively.
+</Note>
 
-      ![JumpCloud SAML assignment](../../../images/sso/jumpcloud/enable-saml.png)
-   </Step>
-</Steps>
+10. Assignments
+
+Back in JumpCloud, navigate to the **User Groups** tab and assign users to the newly created application.
+
+![JumpCloud SAML assignment](../../../images/sso/jumpcloud/assignment.png)
+
+11. Return to Infisical and enable SAML SSO.
+
+Enabling SAML SSO enforces all members in your organization to only be able to log into Infisical via JumpCloud.
+
+![JumpCloud SAML assignment](../../../images/sso/jumpcloud/enable-saml.png)
 
 <Note>
    If you're configuring SAML SSO on a self-hosted instance of Infisical, make sure to
-   set the `AUTH_SECRET` and `SITE_URL` environment variable for it to work:
+   set the `JWT_PROVIDER_AUTH_SECRET` and `SITE_URL` environment variable for it to work:
    
-   - `AUTH_SECRET`: A secret key used for signing and verifying JWT. This can be a random 32-byte base64 string generated with `openssl rand -base64 32`.
+   - `JWT_PROVIDER_AUTH_SECRET`: This is secret key used for signing and verifying JWT. This could be a randomly-generated 256-bit hex string.
    - `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
 </Note>

docs/documentation/platform/sso/okta.mdx

@@ -10,80 +10,78 @@ description: "Configure Okta SAML 2.0 for Infisical SSO"
    then you should contact team@infisical.com to purchase an enterprise license to use it.
 </Info>
 
-<Steps>
-   <Step title="Prepare the SAML SSO configuration in Infisical">
-      In Infisical, head over to your organization Settings > Authentication > SAML SSO Configuration and select **Set up SAML SSO**.
-      
-      Next, copy the **Single sign-on URL** and **Audience URI (SP Entity ID)** to use when configuring the Okta SAML 2.0 application.
-      ![Okta SAML initial configuration](../../../images/sso/okta/init-config.png)
-   </Step>
-   <Step title="Create a SAML application in Okta">
-      In the Okta Admin Portal, select Applications > Applications from the navigation. On the Applications screen, select the **Create App Integration**
-      button.
+1. In Infisical, head over to your organization Settings > Authentication > SAML SSO Configuration and select **Set up SAML SSO**.
+   Next, copy the **Single sign-on URL** and **Audience URI (SP Entity ID)** to use when configuring the Okta SAML 2.0 application.
 
-      ![SAML Okta create app integration](../../../images/sso/okta/create-app-integration.png)
-      
-      In the Create a New Application Integration dialog, select the **SAML 2.0** radio button:
+![Okta SAML initial configuration](../../../images/sso/okta/init-config.png)
 
-      ![SAML Okta create SAML 2.0 integration](../../../images/sso/okta/create-saml-app.png)
-      
-      On the General Settings screen, give the application a unique name like Infisical and select **Next**.
-      
-      ![SAML Okta create SAML 2.0 integration](../../../images/sso/okta/general-settings.png)
-      
-      On the Configure SAML screen, set the **Single sign-on URL** and **Audience URI (SP Entity ID)** from step 1.
+2. In the Okta Admin Portal, select Applications > Applications from the
+   navigation. On the Applications screen, select the **Create App Integration**
+   button.
 
-      ![SAML Okta configure IdP fields](../../../images/sso/okta/configure-saml.png)
-      
-      <Note>
-         If you're self-hosting Infisical, then you will want to replace
-         `https://app.infisical.com` with your own domain.
-      </Note>
-      
-      Also on the Configure SAML screen, configure the **Attribute Statements** to map:
+![SAML Okta create app integration](../../../images/sso/okta/create-app-integration.png)
 
-      - `id -> user.id`,
-      - `email -> user.email`,
-      - `firstName -> user.firstName`
-      - `lastName -> user.lastName`
+3. In the Create a New Application Integration dialog, select the **SAML 2.0** radio button:
 
-      ![SAML Okta attribute statements](../../../images/sso/okta/attribute-statements.png)
+![SAML Okta create SAML 2.0 integration](../../../images/sso/okta/create-saml-app.png)
 
-      Once configured, select **Next** to proceed to the Feedback screen and select **Finish**.
-   </Step>
-   <Step title="Retrieve Identity Provider (IdP) Information from Okta">
-      Once your application is created, select the **Sign On** tab for the app and select the **View Setup Instructions** button located on the right side of the screen:
+4. On the General Settings screen, give the application a unique name like Infisical and select **Next**.
 
-      ![SAML Okta view setup instructions](../../../images/sso/okta/view-setup-instructions.png)
+![SAML Okta create SAML 2.0 integration](../../../images/sso/okta/general-settings.png)
 
-      Copy the **Identity Provider Single Sign-On URL**, the **Identity Provider Issuer**, and the **X.509 Certificate** to use when finishing configuring Okta SAML in Infisical.
+5. On the Configure SAML screen, set the **Single sign-on URL** and **Audience URI (SP Entity ID)** from step 1.
 
-      ![SAML Okta IdP values](../../../images/sso/okta/idp-values.png)
-   </Step>
-   <Step title="Finish configuring SAML in Infisical">
-      Back in Infisical, set **Identity Provider Single Sign-On URL**, **Identity Provider Issuer**,
-      and **Certificate** to **X.509 Certificate** from step 3. Once you've done that, press **Update** to complete the required configuration.
+![SAML Okta configure IdP fields](../../../images/sso/okta/configure-saml.png)
 
-      ![SAML Okta paste values into Infisical](../../../images/sso/okta/idp-values-2.png)
-   </Step>
-   <Step title="Assign users in Okta to the application">
-      Back in Okta, navigate to the **Assignments** tab and select **Assign**. You can assign access to the application on a user-by-user basis using the Assign to People option, or in-bulk using the Assign to Groups option.
+<Note>
+  If you're self-hosting Infisical, then you will want to replace
+  `https://app.infisical.com` with your own domain.
+</Note>
 
-      ![SAML Okta assignment](../../../images/sso/okta/assignment.png)
+6. Also on the Configure SAML screen, configure the **Attribute Statements** to map:
 
-      At this point, you have configured everything you need within the context of the Okta Admin Portal.
-   </Step>
-   <Step title="Enable SAML SSO in Infisical">
-      Enabling SAML SSO enforces all members in your organization to only be able to log into Infisical via Okta.
+- `id -> user.id`,
+- `email -> user.email`,
+- `firstName -> user.firstName`
+- `lastName -> user.lastName`
 
-      ![SAML Okta assignment](../../../images/sso/okta/enable-saml.png)
-   </Step>
-</Steps>
+![SAML Okta attribute statements](../../../images/sso/okta/attribute-statements.png)
+
+Once configured, select **Next** to proceed to the Feedback screen and select **Finish**.
+
+7. Get IdP values
+
+Once your application is created, select the **Sign On** tab for the app and select the **View Setup Instructions** button located on the right side of the screen:
+
+![SAML Okta view setup instructions](../../../images/sso/okta/view-setup-instructions.png)
+
+Copy the **Identity Provider Single Sign-On URL**, the **Identity Provider Issuer**, and the **X.509 Certificate** to use when finishing configuring Okta SAML in Infisical.
+
+![SAML Okta IdP values](../../../images/sso/okta/idp-values.png)
+
+Back in Infisical, set **Identity Provider Single Sign-On URL**, **Identity Provider Issuer**,
+and **Certificate** to **X.509 Certificate** from above. Once you've done that, press **Update** to complete the required configuration.
+
+![SAML Okta paste values into Infisical](../../../images/sso/okta/idp-values-2.png)
+
+8. Finally, navigate to the **Assignments** tab and select **Assign**
+
+You can assign access to the application on a user-by-user basis using the Assign to People option, or in-bulk using the Assign to Groups option.
+
+![SAML Okta assignment](../../../images/sso/okta/assignment.png)
+
+At this point, you have configured everything you need within the context of the Okta Admin Portal.
+
+9. Return to Infisical and enable SAML SSO.
+
+Enabling SAML SSO enforces all members in your organization to only be able to log into Infisical via Okta.
+
+![SAML Okta assignment](../../../images/sso/okta/enable-saml.png)
 
 <Note>
    If you're configuring SAML SSO on a self-hosted instance of Infisical, make sure to
-   set the `AUTH_SECRET` and `SITE_URL` environment variable for it to work:
+   set the `JWT_PROVIDER_AUTH_SECRET` and `SITE_URL` environment variable for it to work:
    
-   - `AUTH_SECRET`: A secret key used for signing and verifying JWT. This can be a random 32-byte base64 string generated with `openssl rand -base64 32`.
+   - `JWT_PROVIDER_AUTH_SECRET`: This is secret key used for signing and verifying JWT. This could be a randomly-generated 256-bit hex string.
    - `SITE_URL`: The URL of your self-hosted instance of Infisical - should be an absolute URL including the protocol (e.g. https://app.infisical.com)
 </Note>

docs/mint.json

@@ -159,16 +159,10 @@
           "pages": [
             "self-hosting/overview",
             "self-hosting/deployment-options/standalone-infisical",
-            "self-hosting/deployment-options/docker-compose",
             "self-hosting/deployment-options/kubernetes-helm",
             "self-hosting/deployment-options/aws-ec2",
-            "self-hosting/deployment-options/aws-lightsail",
-            "self-hosting/deployment-options/gcp-cloud-run",
-            "self-hosting/deployment-options/azure-app-services",
-            "self-hosting/deployment-options/azure-container-instances",
-            "self-hosting/deployment-options/digital-ocean-marketplace",
-            "self-hosting/deployment-options/fly.io",
-            "self-hosting/deployment-options/railway"
+            "self-hosting/deployment-options/docker-compose",
+            "self-hosting/deployment-options/digital-ocean-marketplace"
           ]
         },
         "self-hosting/configuration/envars",

docs/sdks/languages/go.mdx

@@ -5,4 +5,5 @@ icon: "golang"
 
 Coming soon.
 
-Star our GitHub repository to stay updated [cross-language SDK](https://github.com/Infisical/sdk) GitHub repository to stay updated.
+Follow this GitHub
+[issue](https://github.com/Infisical/infisical/issues/436) to stay updated.

docs/sdks/languages/java.mdx

@@ -3,307 +3,7 @@ title: "Java"
 icon: "java"
 ---
 
-If you're working with Java, the official [Infisical Java SDK](https://github.com/Infisical/sdk/tree/main/languages/java) package is the easiest way to fetch and work with secrets for your application.
+Coming soon.
 
-## Basic Usage
-
-```java
-package com.example.app;
-
-import com.infisical.sdk.InfisicalClient;
-import com.infisical.sdk.schema.*;
-
-public class Example {
-    public static void main(String[] args) {
-        // Create a new Infisical Client
-        ClientSettings settings = new ClientSettings();
-        settings.setClientID("MACHINE_IDENTITY_CLIENT_ID");
-        settings.setClientSecret("MACHINE_IDENTITY_CLIENT_SECRET");
-        settings.setCacheTTL(Long.valueOf(300)); // 300 seconds, 5 minutes
-
-        InfisicalClient client = new InfisicalClient(settings);
-
-        // Create the options for fetching the secret
-        GetSecretOptions options = new GetSecretOptions();
-        options.setSecretName("TEST");
-        options.setEnvironment("dev");
-        options.setProjectID("PROJECT_ID");
-
-        // Fetch the sercret with the provided options
-        GetSecretResponseSecret secret = client.getSecret(options);
-
-        // Print the value
-        System.out.println(secret.getSecretValue());
-
-        // Important to avoid memory leaks!
-        // If you intend to use the client throughout your entire application, you can omit this line.
-        client.close();
-    }
-}
-```
-
-This example demonstrates how to use the Infisical Java SDK in a Java application. The application retrieves a secret named `TEST` from the `dev` environment of the `PROJECT_ID` project.
-
-<Warning>
-    We do not recommend hardcoding your [Machine Identity Tokens](/platform/identities/overview). Setting it as an environment variable would be best.
-</Warning>
-
-# Installation
-
-The Infisical Java SDK is hosted on the GitHub Packages Apache Maven registry. Because of this you need to configure your environment properly so it's able to pull dependencies from the GitHub registry. Please check [this guide from GitHub](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) on how to achieve this.
-
-Our package is [located here](https://github.com/Infisical/sdk/packages/2019741). Please follow the installation guide on the page.
-
-# Configuration
-
-Import the SDK and create a client instance with your [Machine Identity](/platform/identities/universal-auth).
-
-```java
-import com.infisical.sdk.InfisicalClient;
-import com.infisical.sdk.schema.*;
-
-public class App {
-    public static void main(String[] args) {
-
-        ClientSettings settings = new ClientSettings();
-        settings.setClientID("MACHINE_IDENTITY_CLIENT_ID");
-        settings.setClientSecret("MACHINE_IDENTITY_CLIENT_SECRET");
-
-        InfisicalClient client = new InfisicalClient(settings); // Your client!
-    }
-}
-```
-
-### ClientSettings methods
-
-<ParamField query="options" type="object">
-    <Expandable title="properties">
-        <ParamField query="setClientID()" type="string" optional>
-            Your machine identity client ID.
-        </ParamField>
-          <ParamField query="setClientSecret()" type="string" optional>
-            Your machine identity client secret.
-        </ParamField>
-
-         <ParamField query="setAccessToken()" type="string" optional>
-            An access token obtained from the machine identity login endpoint.
-        </ParamField>
-
-        <ParamField query="setCacheTTL()" type="number" default="300" optional>
-            Time-to-live (in seconds) for refreshing cached secrets.
-            If manually set to 0, caching will be disabled, this is not recommended.
-        </ParamField>
-
-        <ParamField query="setSiteURL()" type="string" default="https://app.infisical.com" optional>
-            Your self-hosted absolute site URL including the protocol (e.g. `https://app.infisical.com`)
-        </ParamField>
-    </Expandable>
-
-</ParamField>
-
-### Caching
-
-To reduce the number of API requests, the SDK temporarily stores secrets it retrieves. By default, a secret remains cached for 5 minutes after it's first fetched. Each time it's fetched again, this 5-minute timer resets. You can adjust this caching duration by setting the "cacheTTL" option when creating the client.
-
-## Working with Secrets
-
-### client.listSecrets(options)
-
-```java
-ListSecretsOptions options = new ListSecretsOptions();
-options.setEnvironment("dev");
-options.setProjectID("PROJECT_ID");
-options.setPath("/foo/bar");
-options.setIncludeImports(false);
-
-SecretElement[] secrets = client.listSecrets(options);
-```
-
-Retrieve all secrets within the Infisical project and environment that client is connected to
-
-### Methods
-
-<ParamField query="Parameters" type="object">
-    <Expandable title="properties">
-        <ParamField query="setEnvironment()" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-
-        <ParamField query="setProjectID()" type="string">
-            The project ID where the secret lives in.
-        </ParamField>
-
-         <ParamField query="setPath()" type="string" optional>
-            The path from where secrets should be fetched from.
-        </ParamField>
-
-        <ParamField query="setAttachToProcessEnv()" type="boolean" default="false" optional>
-             Whether or not to set the fetched secrets to the process environment. If true, you can access the secrets like so `System.getenv("SECRET_NAME")`.
-        </ParamField>
-
-        <ParamField query="setIncludeImports()" type="boolean" default="false" optional>
-             Whether or not to include imported secrets from the current path. Read about [secret import](/documentation/platform/secret-reference)
-        </ParamField>
-    </Expandable>
-
-</ParamField>
-
-### client.getSecret(options)
-
-```java
-GetSecretOptions options = new GetSecretOptions();
-options.setSecretName("TEST");
-options.setEnvironment("dev");
-options.setProjectID("PROJECT_ID");
-
-GetSecretResponseSecret secret = client.getSecret(options);
-
-String secretValue = secret.getSecretValue();
-```
-
-Retrieve a secret from Infisical.
-
-By default, `getSecret()` fetches and returns a shared secret.
-
-### Methods
-
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="setSecretName()" type="string" required>
-            The key of the secret to retrieve.
-        </ParamField>
-        <ParamField query="setProjectID()" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="setEnvironment()" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="setPath()" type="string" optional>
-            The path from where secret should be fetched from.
-        </ParamField>
-        <ParamField query="setType()" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
-</ParamField>
-
-### client.createSecret(options)
-
-```java
-CreateSecretOptions createOptions = new CreateSecretOptions();
-createOptions.setSecretName("NEW_SECRET");
-createOptions.setEnvironment("dev");
-createOptions.setProjectID("PROJECT_ID");
-createOptions.setSecretValue("SOME SECRET VALUE");
-createOptions.setPath("/"); // Default
-createOptions.setType("shared"); // Default
-
-CreateSecretResponseSecret newSecret = client.createSecret(createOptions);
-```
-
-Create a new secret in Infisical.
-
-### Methods
-
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="setSecretName()" type="string" required>
-            The key of the secret to create.
-        </ParamField>
-        <ParamField query="setSecretValue()" type="string" required>
-            The value of the secret.
-        </ParamField>
-        <ParamField query="setProjectID()" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="setEnvironment()" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="setPath()" type="string" optional>
-            The path from where secret should be created.
-        </ParamField>
-        <ParamField query="setType()" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
-</ParamField>
-
-### client.updateSecret(options)
-
-```java
-UpdateSecretOptions options = new UpdateSecretOptions();
-
-options.setSecretName("SECRET_TO_UPDATE");
-options.setSecretValue("NEW SECRET VALUE");
-options.setEnvironment("dev");
-options.setProjectID("PROJECT_ID");
-options.setPath("/"); // Default
-options.setType("shared"); // Default
-
-UpdateSecretResponseSecret updatedSecret = client.updateSecret(options);
-```
-
-Update an existing secret in Infisical.
-
-### Methods
-
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="setSecretName()" type="string" required>
-            The key of the secret to update.
-        </ParamField>
-        <ParamField query="setSecretValue()" type="string" required>
-            The new value of the secret.
-        </ParamField>
-        <ParamField query="setProjectID()" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="setEnvironment()" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="setPath()" type="string" optional>
-            The path from where secret should be updated.
-        </ParamField>
-        <ParamField query="setType()" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
-</ParamField>
-
-### client.deleteSecret(options)
-
-```java
-DeleteSecretOptions options = new DeleteSecretOptions();
-
-options.setSecretName("SECRET_TO_DELETE");
-options.setEnvironment("dev");
-options.setProjectID("PROJECT_ID");
-options.setPath("/"); // Default
-options.setType("shared"); // Default
-
-DeleteSecretResponseSecret deletedSecret = client.deleteSecret(options);
-```
-
-Delete a secret in Infisical.
-
-### Methods
-
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="setSecretName()" type="string">
-            The key of the secret to update.
-        </ParamField>
-        <ParamField query="setProjectID()" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="setEnvironment()" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="setPath()" type="string" optional>
-            The path from where secret should be deleted.
-        </ParamField>
-        <ParamField query="setType()" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
-</ParamField>
+Follow this GitHub
+[issue](https://github.com/Infisical/infisical/issues/434) to stay updated.

docs/sdks/languages/node.mdx

@@ -3,315 +3,205 @@ title: "Node"
 icon: "node"
 ---
 
-If you're working with Node.js, the official [infisical-node](https://github.com/Infisical/sdk/tree/main/languages/node) package is the easiest way to fetch and work with secrets for your application.
+If you're working with Node.js, the official [infisical-node](https://github.com/Infisical/infisical-node) package is the easiest way to fetch and work with secrets for your application.
 
 ## Basic Usage
 
 ```js
 import express from "express";
-
-import { InfisicalClient, LogLevel } from "@infisical/sdk";
-
+import InfisicalClient from "infisical-node";
 const app = express();
-
 const PORT = 3000;
 
 const client = new InfisicalClient({
-    clientId: "YOUR_CLIENT_ID",
-    clientSecret: "YOUR_CLIENT_SECRET",
-    logLevel: LogLevel.Error
+  token: "YOUR_INFISICAL_TOKEN"
 });
 
 app.get("/", async (req, res) => {
-    // access value
-
-    const name = await client.getSecret({
-        environment: "dev",
-        projectId: "PROJECT_ID",
-        path: "/",
-        type: "shared",
-        secretName: "NAME"
-    });
-
-    res.send(`Hello! My name is: ${name.secretValue}`);
+  // access value
+  const name = await client.getSecret("NAME");
+  res.send(`Hello! My name is: ${name.secretValue}`);
 });
 
 app.listen(PORT, async () => {
-    // initialize client
-
-    console.log(`App listening on port ${port}`);
+  console.log(`App listening on port ${PORT}`);
 });
 ```
 
 This example demonstrates how to use the Infisical Node SDK with an Express application. The application retrieves a secret named "NAME" and responds to requests with a greeting that includes the secret value.
 
 <Warning>
-    We do not recommend hardcoding your [Machine Identity Tokens](/documentation/platform/identities/overview). Setting it as an environment variable
-    would be best.
+  We do not recommend hardcoding your [Infisical
+  Token](/documentation/platform/token). Setting it as an environment
+  variable would be best.
 </Warning>
 
 ## Installation
 
-Run `npm` to add `@infisical/sdk` to your project.
+Run `npm` to add `infisical-node` to your project.
 
 ```console
-$ npm install @infisical/sdk
+$ npm install infisical-node --save
 ```
 
 ## Configuration
 
-Import the SDK and create a client instance with your [Machine Identity](/documentation/platform/identities/overview).
+Import the SDK and create a client instance with your [Infisical Token](/documentation/platform/token).
 
 <Tabs>
   <Tab title="ES6">
     ```js
-    import { InfisicalClient, LogLevel } from "@infisical/sdk";
-
+    import InfisicalClient from "infisical-node";
+    
     const client = new InfisicalClient({
-        clientId: "YOUR_CLIENT_ID",
-        clientSecret: "YOUR_CLIENT_SECRET",
-        logLevel: LogLevel.Error
+      token: "your_infisical_token"
     });
     ```
 
   </Tab>
   <Tab title="ES5">
     ```js
-    const { InfisicalClient, LogLevel } = require("@infisical/sdk");
-
+    const InfisicalClient = require("infisical-node");
+    
     const client = new InfisicalClient({
-        clientId: "YOUR_CLIENT_ID",
-        clientSecret: "YOUR_CLIENT_SECRET",
-        logLevel: LogLevel.Error
+      token: "your_infisical_token"
     });
     ````
-
   </Tab>
+
 </Tabs>
 
 ### Parameters
 
 <ParamField query="options" type="object">
-    <Expandable title="properties">
-        <ParamField query="clientId" type="string" optional>
-            Your machine identity client ID.
-        </ParamField>
-          <ParamField query="clientSecret" type="string" optional>
-            Your machine identity client secret.
-        </ParamField>
-
-         <ParamField query="accessToken" type="string" optional>
-            An access token obtained from the machine identity login endpoint.
-        </ParamField>
-
-        <ParamField query="cacheTtl" type="number" default="300" optional>
-            Time-to-live (in seconds) for refreshing cached secrets.
-            If manually set to 0, caching will be disabled, this is not recommended.
-        </ParamField>
-
-        <ParamField query="siteUrl" type="string" default="https://app.infisical.com" optional>
-            Your self-hosted absolute site URL including the protocol (e.g. `https://app.infisical.com`)
-        </ParamField>
-        <ParamField query="logLevel" type="enum" default="Error" optional>
-            The level of logs you wish to log The logs are derived from Rust, as we have written our base SDK in Rust.
-        </ParamField>
-    </Expandable>
-
+  <Expandable title="properties">
+    <ParamField query="token" type="string" optional>
+      An [Infisical Token](/documentation/platform/token) scoped to a project
+      and environment
+    </ParamField>
+    <ParamField
+      query="siteURL"
+      type="string"
+      default="https://app.infisical.com"
+      optional
+    >
+      Your self-hosted absolute site URL including the protocol (e.g.
+      `https://app.infisical.com`)
+    </ParamField>
+    <ParamField query="cacheTTL" type="number" default="300" optional>
+      Time-to-live (in seconds) for refreshing cached secrets. Default: `300`.
+    </ParamField>
+    <ParamField query="debug" type="boolean" default="false" optional>
+      Whether or not debug mode is on
+    </ParamField>
+  </Expandable>
 </ParamField>
 
-### Caching
+## Caching
 
-To reduce the number of API requests, the SDK temporarily stores secrets it retrieves. By default, a secret remains cached for 5 minutes after it's first fetched. Each time it's fetched again, this 5-minute timer resets. You can adjust this caching duration by setting the "cacheTtl" option when creating the client.
+The SDK caches every secret and updates it periodically based on the provided `cacheTTL`. For example, if `cacheTTL` of `300` is provided, then a secret will be refetched 5 minutes after the first fetch; if the fetch fails, the cached secret is returned.
+
+<Tip>
+  For optimal performance, we recommend creating a single instance of the Infisical client and exporting it to be used across your entire app to take advantage of caching benefits.
+</Tip>
 
 ## Working with Secrets
 
-### client.listSecrets(options)
+### client.getAllSecrets()
 
 ```js
-const secrets = await client.listSecrets({
-    environment: "dev",
-    projectId: "PROJECT_ID",
-    path: "/foo/bar/",
-    includeImports: false
-});
+const secrets = await client.getAllSecrets();
 ```
 
 Retrieve all secrets within the Infisical project and environment that client is connected to
 
-### Parameters
-
-<ParamField query="Parameters" type="object">
-    <Expandable title="properties">
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-          <ParamField query="projectId" type="string" required>
-            The project ID where the secret lives in. 
-        </ParamField>
-
-         <ParamField query="path" type="string" optional>
-            The path from where secrets should be fetched from.
-        </ParamField>
-
-        <ParamField query="attachToProcessEnv" type="boolean" default="false" optional>
-            Whether or not to set the fetched secrets to the process environment. If true, you can access the secrets like so `process.env["SECRET_NAME"]`.
-        </ParamField>
-
-        <ParamField query="includeImports" type="false" default="boolean" optional>
-             Whether or not to include imported secrets from the current path. Read about [secret import](/documentation/platform/secret-reference)
-        </ParamField>
-    </Expandable>
-
-</ParamField>
-
-### client.getSecret(options)
+### client.getSecret(secretName, options)
 
 ```js
-const secret = await client.getSecret({
-    environment: "dev",
-    projectId: "PROJECT_ID",
-    secretName: "API_KEY",
-    path: "/",
-    type: "shared"
-});
+const secret = await client.getSecret("API_KEY");
+const value = secret.secretValue; // get its value
 ```
 
 Retrieve a secret from Infisical.
 
-By default, `getSecret()` fetches and returns a shared secret.
+By default, `getSecret()` fetches and returns a personal secret. If not found, it returns a shared secret, or tries to retrieve the value from `process.env`. If a secret is fetched, `getSecret()` caches it to reduce excessive calls and re-fetches periodically based on the `cacheTTL` option (default is `300` seconds) when initializing the client — for more information, see the caching section.
 
 ### Parameters
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secretName" type="string" required>
-            The key of the secret to retrieve.
-        </ParamField>
-        <ParamField query="projectId" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be fetched from.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secretName" type="string" required>
+  The key of the secret to retrieve
+</ParamField>
+<ParamField query="options" type="object" optional>
+  <Expandable title="properties">
+    <ParamField query="type" type="string" default="personal" optional>
+      The type of the secret. Valid options are "shared" or "personal"
+    </ParamField>
+  </Expandable>
 </ParamField>
 
-### client.createSecret(options)
+### client.createSecret(secretName, secretValue, options)
 
 ```js
-const newApiKey = await client.createSecret({
-    projectId: "PROJECT_ID",
-    environment: "dev",
-    secretName: "API_KEY",
-    secretValue: "SECRET VALUE",
-    path: "/",
-    type: "shared"
-});
+const newApiKey = await client.createSecret("API_KEY", "FOO");
 ```
 
 Create a new secret in Infisical.
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secretName" type="string" required>
-            The key of the secret to create.
-        </ParamField>
-        <ParamField query="secretValue" type="string" required>
-            The value of the secret.
-        </ParamField>
-        <ParamField query="projectId" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be created.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secretName" type="string" required>
+  The key of the secret to create
+</ParamField>
+<ParamField query="secretName" type="string" required>
+  The value of the secret to create
+</ParamField>
+<ParamField query="options" type="object" default="object" optional>
+  <Expandable title="properties">
+    <ParamField query="type" type="string" default="shared" optional>
+      The type of the secret. Valid options are "shared" or "personal". A personal secret can only be created if a shared secret with the same name exists.
+    </ParamField>
+  </Expandable>
 </ParamField>
 
-### client.updateSecret(options)
+### client.updateSecret(secretName, secretValue, options)
 
 ```js
-const updatedApiKey = await client.updateSecret({
-    secretName: "API_KEY",
-    secretValue: "NEW SECRET VALUE",
-    projectId: "PROJECT_ID",
-    environment: "dev",
-    path: "/",
-    type: "shared"
-});
+const updatedApiKey = await client.updateSecret("API_KEY", "BAR");
 ```
 
 Update an existing secret in Infisical.
 
 ### Parameters
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secretName" type="string" required>
-            The key of the secret to update.
-        </ParamField>
-        <ParamField query="secretValue" type="string" required>
-            The new value of the secret.
-        </ParamField>
-        <ParamField query="projectId" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be updated.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secretName" type="string" required>
+  The key of the secret to update
+</ParamField>
+<ParamField query="secretName" type="string" required>
+  The new value of the secret
+</ParamField>
+<ParamField query="options" type="object" default="object" optional>
+  <Expandable title="properties">
+    <ParamField query="type" type="string" default="shared" optional>
+      The type of the secret. Valid options are "shared" or "personal"
+    </ParamField>
+  </Expandable>
 </ParamField>
 
-### client.deleteSecret(options)
+### client.deleteSecret(secretName, options)
 
 ```js
-const deletedSecret = await client.deleteSecret({
-    secretName: "API_KEY",
-
-    environment: "dev",
-    projectId: "PROJECT_ID",
-    path: "/",
-
-    type: "shared"
-});
+const deletedSecret = await client.deleteSecret("API_KEY");
 ```
 
 Delete a secret in Infisical.
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secretName" type="string">
-            The key of the secret to update.
-        </ParamField>
-        <ParamField query="projectId" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be deleted.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secretName" type="string" required>
+  The key of the secret to delete
 </ParamField>
+<ParamField query="options" type="object" default="object" optional>
+  <Expandable title="properties">
+    <ParamField query="type" type="string" default="shared" optional>
+      The type of the secret. Valid options are "shared" or "personal". Note that deleting a shared secret also deletes all associated personal secrets.
+    </ParamField>
+  </Expandable>
+</ParamField>
+
+

docs/sdks/languages/php.mdx

@@ -5,4 +5,4 @@ icon: "php"
 
 Coming soon.
 
-Star our GitHub repository to stay updated [cross-language SDK](https://github.com/Infisical/sdk) GitHub repository to stay updated.
+Follow this GitHub [issue](https://github.com/Infisical/infisical/issues/531) to stay updated.

docs/sdks/languages/python.mdx

@@ -3,38 +3,31 @@ title: "Python"
 icon: "python"
 ---
 
-If you're working with Python, the official [infisical-python](https://github.com/Infisical/sdk/edit/main/crates/infisical-py) package is the easiest way to fetch and work with secrets for your application.
+If you're working with Python, the official [infisical-python](https://github.com/Infisical/infisical-python) package is the easiest way to fetch and work with secrets for your application.
 
 ## Basic Usage
 
 ```py
 from flask import Flask
-from infisical_client import ClientSettings, InfisicalClient, GetSecretOptions
+from infisical import InfisicalClient
 
 app = Flask(__name__)
 
-client = InfisicalClient(ClientSettings(
-    client_id="MACHINE_IDENTITY_CLIENT_ID",
-    client_secret="MACHINE_IDENTITY_CLIENT_SECRET",
-))
+client = InfisicalClient(token="your_infisical_token")
 
 @app.route("/")
 def hello_world():
     # access value
-
-    name = client.getSecret(options=GetSecretOptions(
-       environment="dev",
-       project_id="PROJECT_ID",
-       secret_name="NAME"
-    ))
-
+    name = client.get_secret("NAME")
     return f"Hello! My name is: {name.secret_value}"
 ```
 
 This example demonstrates how to use the Infisical Python SDK with a Flask application. The application retrieves a secret named "NAME" and responds to requests with a greeting that includes the secret value.
 
 <Warning>
-    We do not recommend hardcoding your [Machine Identity Tokens](/platform/identities/overview). Setting it as an environment variable would be best.
+  We do not recommend hardcoding your [Infisical
+  Token](/documentation/platform/token). Setting it as an environment
+  variable would be best.
 </Warning>
 
 ## Installation
@@ -42,244 +35,135 @@ This example demonstrates how to use the Infisical Python SDK with a Flask appli
 Run `pip` to add `infisical-python` to your project
 
 ```console
-$ pip install infisical-python
+$ pip install infisical
 ```
 
 Note: You need Python 3.7+.
 
 ## Configuration
 
-Import the SDK and create a client instance with your [Machine Identity](/api-reference/overview/authentication).
+Import the SDK and create a client instance with your [Infisical Token](/documentation/platform/token).
 
 ```py
-from infisical_client import ClientSettings, InfisicalClient
+from infisical import InfisicalClient
 
-client = InfisicalClient(ClientSettings(
-    client_id="MACHINE_IDENTITY_CLIENT_ID",
-    client_secret="MACHINE_IDENTITY_CLIENT_SECRET",
-))
+client = InfisicalClient(token="your_infisical_token")
 ```
 
 ### Parameters
 
-<ParamField query="options" type="object">
-    <Expandable title="properties">
-        <ParamField query="client_id" type="string" optional>
-            Your Infisical Client ID.
-        </ParamField>
-        <ParamField query="client_secret" type="string" optional>
-            Your Infisical Client Secret.
-        </ParamField>
-        <ParamField query="access_token" type="string" optional>
-            If you want to directly pass an access token obtained from the authentication endpoints, you can do so.
-        </ParamField>
+    <ParamField query="token" type="string" optional>
+      An [Infisical Token](/documentation/platform/token) scoped to a project
+      and environment
+    </ParamField>
+    <ParamField
+      query="site_url"
+      type="string"
+      default="https://app.infisical.com"
+      optional
+    >
+      Your self-hosted absolute site URL including the protocol (e.g.
+      `https://app.infisical.com`)
+    </ParamField>
+    <ParamField query="cache_ttl" type="number" default="300" optional>
+      Time-to-live (in seconds) for refreshing cached secrets. Default: `300`.
+    </ParamField>
+    <ParamField query="debug" type="boolean" default="false" optional>
+      Whether or not debug mode is on
+    </ParamField>
 
-        <ParamField query="cache_ttl" type="number" default="300" optional>
-            Time-to-live (in seconds) for refreshing cached secrets.
-            If manually set to 0, caching will be disabled, this is not recommended.
-        </ParamField>
+## Caching
 
+The SDK caches every secret and updates it periodically based on the provided `cache_ttl`. For example, if `cache_ttl` of `300` is provided, then a secret will be refetched 5 minutes after the first fetch; if the fetch fails, the cached secret is returned.
 
-        <ParamField
-        query="site_url"
-        type="string"
-        default="https://app.infisical.com"
-        optional
-        >
-        Your self-hosted absolute site URL including the protocol (e.g.
-        `https://app.infisical.com`)
-        </ParamField>
-    </Expandable>
-
-</ParamField>
-
-### Caching
-
-To reduce the number of API requests, the SDK temporarily stores secrets it retrieves. By default, a secret remains cached for 5 minutes after it's first fetched. Each time it's fetched again, this 5-minute timer resets. You can adjust this caching duration by setting the "cache_ttl" option when creating the client.
+<Tip>
+  For optimal performance, we recommend creating a single instance of the Infisical client and exporting it to be used across your entire app to take advantage of caching benefits.
+</Tip>
 
 ## Working with Secrets
 
-### client.listSecrets(options)
+### client.get_all_secrets()
 
 ```py
-client.listSecrets(options=ListSecretsOptions(
-    environment="dev",
-    project_id="PROJECT_ID"
-))
+secrets = client.get_all_secrets()
 ```
 
 Retrieve all secrets within the Infisical project and environment that client is connected to
 
-### Parameters
-
-<ParamField query="Parameters" type="object">
-    <Expandable title="properties">
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-          <ParamField query="project_id" type="string" required>
-            The project ID where the secret lives in. 
-        </ParamField>
-
-         <ParamField query="path" type="string" optional>
-            The path from where secrets should be fetched from.
-        </ParamField>
-
-        <ParamField query="attach_to_process_env" type="boolean" default="false" optional>
-            Whether or not to set the fetched secrets to the process environment. If true, you can access the secrets like so `process.env["SECRET_NAME"]`.
-        </ParamField>
-
-        <ParamField query="include_imports" type="boolean" default="false" optional>
-             Whether or not to include imported secrets from the current path. Read about [secret import](/documentation/platform/secret-reference)
-        </ParamField>
-    </Expandable>
-
-</ParamField>
-
-### client.getSecret(options)
+### client.get_secret(secret_name, options)
 
 ```py
-secret = client.getSecret(options=GetSecretOptions(
-    environment="dev",
-    project_id="PROJECT_ID",
-    secret_name="API_KEY"
-))
+secret = client.get_secret("API_KEY")
 value = secret.secret_value # get its value
 ```
 
-By default, `getSecret()` fetches and returns a shared secret. If not found, it returns a personal secret.
+By default, `get_secret()` fetches and returns a personal secret. If not found, it returns a shared secret, or tries to retrieve the value from `os.environ`. If a secret is fetched, `get_secret()` caches it to reduce excessive calls and re-fetches periodically based on the `cacheTTL` option (default is 300 seconds) when initializing the client — for more information, see the caching section.
 
 ### Parameters
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secret_name" type="string" required>
-            The key of the secret to retrieve
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="project_id" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be fetched from.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "personal".
-        </ParamField>
-        <ParamField query="include_imports" type="boolean" default="false" optional>
-            Whether or not to include imported secrets from the current path. Read about [secret import](/documentation/platform/secret-reference)
-        </ParamField>
-    </Expandable>
+<ParamField query="secret_name" type="string" required>
+  The key of the secret to retrieve
+</ParamField>
+<ParamField query="type" type="string" default="personal" optional>
+  The type of the secret. Valid options are "shared" or "personal"
 </ParamField>
 
-### client.createSecret(options)
+### client.create_secret(secret_name, secret_value, options)
 
 ```py
-api_key = client.createSecret(options=CreateSecretOptions(
-    secret_name="API_KEY",
-    secret_value="Some API Key",
-    environment="dev",
-    project_id="PROJECT_ID"
-))
+new_api_key = client.create_secret("API_KEY", "FOO");
 ```
 
 Create a new secret in Infisical.
 
 ### Parameters
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secret_name" type="string" required>
-            The key of the secret to create.
-        </ParamField>
-        <ParamField query="secret_value" type="string" required>
-            The value of the secret.
-        </ParamField>
-        <ParamField query="project_id" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be created.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secret_name" type="string" required>
+  The key of the secret to create
+</ParamField>
+<ParamField query="secret_value" type="string" required>
+  The value of the secret to create
+</ParamField>
+<ParamField query="type" type="string" default="shared" optional>
+  The type of the secret. Valid options are "shared" or "personal". A personal secret can only be created if a shared secret with the same name exists.
 </ParamField>
 
-### client.updateSecret(options)
+### client.update_secret(secret_name, secret_value, options)
 
 ```py
-client.updateSecret(options=UpdateSecretOptions(
-    secret_name="API_KEY",
-    secret_value="NEW_VALUE",
-    environment="dev",
-    project_id="PROJECT_ID"
-))
+updated_api_key = client.update_secret("API_KEY", "BAR");
 ```
 
 Update an existing secret in Infisical.
 
 ### Parameters
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secret_name" type="string" required>
-            The key of the secret to update.
-        </ParamField>
-        <ParamField query="secret_value" type="string" required>
-            The new value of the secret.
-        </ParamField>
-        <ParamField query="project_id" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be updated.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secret_name" type="string" required>
+  The key of the secret to update
+</ParamField>
+<ParamField query="secret_value" type="string" required>
+  The new value of the secret
+</ParamField>
+<ParamField query="type" type="string" default="shared" optional>
+  The type of the secret. Valid options are "shared" or "personal"
 </ParamField>
 
-### client.deleteSecret(options)
+### client.delete_secret(secret_name, options)
 
 ```py
-client.deleteSecret(options=DeleteSecretOptions(
-    environment="dev",
-    project_id="PROJECT_ID",
-    secret_name="API_KEY"
-))
+deleted_secret = client.delete_secret("API_KEY");
 ```
 
 Delete a secret in Infisical.
 
 ### Parameters
 
-<ParamField query="Parameters" type="object" optional>
-    <Expandable title="properties">
-        <ParamField query="secret_name" type="string">
-            The key of the secret to update.
-        </ParamField>
-        <ParamField query="project_id" type="string" required>
-            The project ID where the secret lives in.
-        </ParamField>
-        <ParamField query="environment" type="string" required>
-            The slug name (dev, prod, etc) of the environment from where secrets should be fetched from.
-        </ParamField>
-        <ParamField query="path" type="string" optional>
-            The path from where secret should be deleted.
-        </ParamField>
-        <ParamField query="type" type="string" optional>
-            The type of the secret. Valid options are "shared" or "personal". If not specified, the default value is "shared".
-        </ParamField>
-    </Expandable>
+<ParamField query="secret_name" type="string" required>
+  The key of the secret to delete
 </ParamField>
+<ParamField query="type" type="string" default="shared" optional>
+  The type of the secret. Valid options are "shared" or "personal"
+</ParamField>
+
+Follow this GitHub
+[issue](https://github.com/Infisical/infisical/issues/433) to stay updated.

docs/sdks/languages/ruby.mdx

@@ -5,4 +5,5 @@ icon: "gem"
 
 Coming soon.
 
-Star our GitHub repository to stay updated [cross-language SDK](https://github.com/Infisical/sdk) GitHub repository to stay updated.
+Follow this GitHub
+[issue](https://github.com/Infisical/infisical/issues/435) to stay updated.

docs/sdks/languages/rust.mdx

@@ -5,4 +5,5 @@ icon: "rust"
 
 Coming soon.
 
-Star our GitHub repository to stay updated [cross-language SDK](https://github.com/Infisical/sdk) GitHub repository to stay updated.
+Follow this GitHub
+[issue](https://github.com/Infisical/infisical/issues/437) to stay updated.

docs/sdks/overview.mdx

@@ -2,52 +2,104 @@
 title: "Introduction"
 ---
 
-From local development to production, Infisical SDKs provide the easiest way for your app to fetch back secrets from Infisical on demand.
+From local development to production, Infisical SDKs provide the easiest way for your app to fetch back secrets from Infisical on demand. 
 
--   Install and initialize a language-specific client SDK into your application
--   Provision the client scoped-access to a project and environment in Infisical
--   Fetch secrets on demand
+- Install and initialize a language-specific client SDK into your application
+- Provision the client scoped-access to a project and environment in Infisical
+- Fetch secrets on demand
 
 <CardGroup cols={2}>
-    <Card title="Node" href="/sdks/languages/node" icon="node" color="#68a063">
-        Manage secrets for your Node application on demand
-    </Card>
-    <Card href="/sdks/languages/python" title="Python" icon="python" color="#4c8abe">
-        Manage secrets for your Python application on demand
-    </Card>
-    <Card href="/sdks/languages/java" title="Java" icon="java" color="#e41f23">
-        Manage secrets for your Java application on demand
-    </Card>
-    <Card href="/sdks/languages/ruby" title="Ruby" icon="gem" color="#ac0d01">
-        Manage secrets for your Ruby application on demand
-    </Card>
-    <Card href="/sdks/languages/go" title="Golang" icon="golang" color="#00add8">
-        Manage secrets for your Go application on demand
-    </Card>
-    <Card href="/sdks/languages/rust" title="Rust" icon="rust" color="#cd412b">
-        Manage secrets for your Rust application on demand
-    </Card>
-    <Card href="/sdks/languages/php" title="PHP" icon="php" color="#787cb4">
-        Manage secrets for your PHP application on demand
-    </Card>
+  <Card
+    title="Node"
+    href="https://github.com/Infisical/infisical-node"
+    icon="node"
+    color="#68a063"
+  >
+    Manage secrets for your Node application on demand
+  </Card>
+  <Card 
+    href="https://github.com/Infisical/infisical-python" 
+    title="Python" 
+    icon="python" 
+    color="#4c8abe"
+    >
+    Manage secrets for your Python application on demand
+  </Card>
+  <Card 
+    href="/sdks/languages/java" 
+    title="Java" 
+    icon="java"
+    color="#e41f23"
+>
+    Manage secrets for your Java application on demand
+  </Card>
+  <Card
+    href="/sdks/languages/ruby"
+    title="Ruby"
+    icon="gem"
+    color="#ac0d01"
+  >
+    Manage secrets for your Ruby application on demand
+  </Card>
+  <Card
+    href="/sdks/languages/go"
+    title="Golang"
+    icon="golang"
+    color="#00add8"
+  >
+    Manage secrets for your Go application on demand
+  </Card>
+  <Card
+    href="/sdks/languages/rust"
+    title="Rust"
+    icon="rust"
+    color="#cd412b"
+  >
+    Manage secrets for your Rust application on demand
+  </Card>
+  <Card
+    href="/sdks/languages/php"
+    title="PHP"
+    icon="php"
+    color="#787cb4"
+  >
+    Manage secrets for your PHP application on demand
+  </Card>
 </CardGroup>
 
 ## FAQ
 
 <AccordionGroup>
-    <Accordion title="Isn't it inefficient if my app makes a request every time it needs a secret?">
-        The client SDK caches every secret and implements a 5-minute waiting period before re-requesting it. The waiting period can be controlled by
-        setting the `cacheTTL` parameter at the time of initializing the client.
-        
-        Note: The exact parameter name may differ depending on the language.
+    <Accordion title="Are my secrets exposed in transit every time the SDK fetches them?">
+        No. Infisical uses end-to-end encryption which ensures that secrets are always encrypted in transit
+        and decrypted on the client side. In fact, not even the server can decrypt your secrets (unless 
+        that permission is explicitly granted from within the platform).
+
+        Check out the [security guide](/security/overview).
     </Accordion>
-    <Accordion title="Can I attach the environment variables to my process environment?">
-        Yes you can! The client SDK provides a method to attach the secrets to your process environment. When using the `listSecrets()` method, you
-        can pass a `attachToProcessEnv` parameter, which tells the SDK to attach all the found secrets to your process environment.
-        
-        Note: The exact parameter name may differ depending on the language.
+    <Accordion title="Isn't it inefficient if my app makes a request every time it needs a secret?">
+        The client SDK caches every secret and implements a 5-minute waiting period before
+        re-requesting it. The waiting period can be controlled by setting the `cacheTTL` parameter at
+        the time of initializing the client.
     </Accordion>
     <Accordion title="What if a request for a secret fails?">
-        The SDK caches every secret and falls back to the cached value if a request fails. If no cached value is found, and the request fails, then the SDK throws an error.
+        The SDK caches every secret and falls back to the cached value if a request fails. If no cached
+        value ever-existed, the SDK falls back to whatever value is on `process.env`.
     </Accordion>
-</AccordionGroup>
+    <Accordion title="Can I still use process.env with the SDK?">
+        Yes. If no `token` parameter is passed in at the time of initializing the client or nothing is found when requesting for a secret,
+        then the SDK falls back to whatever value is on `process.env`.
+    </Accordion>
+    <Accordion title="What's the point if I still have to manage a token for the SDK?">
+        The token enables the SDK to authenticate with Infisical to fetch back your secrets.
+        Although the SDK requires you to pass in a token, it enables greater efficiency and security
+        than if you managed dozens of secrets yourself without it. Here're some benefits:
+
+        - You always pull in the right secrets because they're fetched on demand from a centralize source that is Infisical.
+        - You can use the Infisical which comes with tons of benefits like secret versioning, access controls, audit logs, etc.
+        - You now risk leaking one token that can be revoked instead of dozens of raw secrets.
+        
+        And much more.
+    </Accordion>
+    
+</AccordionGroup>

docs/self-hosting/configuration/envars.mdx

@@ -18,14 +18,15 @@ Other environment variables are listed below to increase the functionality of yo
       Must be a random 32 byte base64 string. Can be generated with `openssl rand -base64 32`
     </ParamField>
 
-    <ParamField query="MONGO_URL" type="string" default="none" required>
-      Mongo connection string. *TLS based connection string is not yet supported
-    </ParamField>
+<ParamField query="MONGO_URL" type="string" default="none" required>
+  *TLS based connection string is not yet supported
+</ParamField>
 
-    <ParamField query="REDIS_URL" type="string" default="none" required>
-      Redis connection string
-    </ParamField>
-  </Tab>
+<ParamField query="REDIS_URL" type="string" default="none" required>
+  Redis connection string
+</ParamField>
+
+</Tab>
   <Tab title="Email service">
     <Info>When email service is not configured, Infisical will have limited functionality</Info>
 

docs/self-hosting/deployment-options/aws-lightsail.mdx

@@ -1,66 +0,0 @@
----
-title: "AWS Lightsail"
-description: "Deploy Infisical with AWS Lightsail"
----
-
-Prerequisites:
-- Have an account with [Amazon Web Services (AWS)](https://aws.amazon.com/)
-
-<Steps>
-    <Step title="Create a container service in AWS Lightsail">
-        1.1. In AWS, navigate to the **Lightsail** service and press **Create container service** under the **Containers** tab.
-        ![AWS Lightsail](/images/self-hosting/deployment-options/aws-lightsail/awsl-select-lightsail.png)
-        
-        ![AWS Lightsail create container service](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service.png)
-        
-        1.2. In the **Container service location** section, select the AWS region that's closest to your infrastructure. 
-        
-        Afterwards, in the **Container service capacity** section, set the power level and scale to fit your needs; you may opt for the default setting
-        and adjust accordingly in the future.
-        
-        ![AWS Lightsail container service capacity](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-capacity.png)
-        
-        1.3. In the **Set up your first deployment** section, select the **Specify a custom deployment** option. Give the container a friendly name like **infisical** and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the **Image** field; this will pull the image from Docker Hub.
-        
-        For example, in order to opt for Infisical `v0.43.4`, you would input: `infisical/infisical:v0.43.4`.
-        
-        ![AWS Lightsail container service deployment](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-deployment.png)
-        
-        1.4. Running Infisical requires a few environment variables to be set for the container service.
-        At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-        which you can read more about [here](/self-hosting/configuration/envars).
-        
-        In the **Environment variables** section, fill in the required environment variables.
-        
-        <Note>
-            To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars).
-        </Note>
-        
-        Also, under the **Open ports** section, add an entry for port `8080` and protocol `HTTP` since Infisical listens on port `8080`.
-
-        ![AWS Lightsail container service environment variables](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-envars.png)
-        
-        1.5. In the **Public endpoint** section, select the container from the previous steps from the dropdown; this will make the container accessible over the public internet.
-        
-        ![AWS Lightsail container service public endpoint](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-public-endpoint.png)
-        
-        1.6. Finally, in the **Identify your service** section, give the container service a unique name like infisical and press **Create container service**.
-        
-        ![AWS Lightsail container service summary](/images/self-hosting/deployment-options/aws-lightsail/awsl-create-container-service-summary.png)
-    </Step>
-    <Step title="Navigate to your deployed instance of Infisical">
-        On the newly-created container service page, wait for the **Status** to turn to **Running** and check out the **Public domain** of the container service; you can access your instance of Infisical by this URL.
-        
-        ![AWS Lightsail container service overview](/images/self-hosting/deployment-options/aws-lightsail/awsl-container-service-overview.png)
-    </Step>
-</Steps>
-
-<AccordionGroup>
-  <Accordion title="Do you have any recommendations for deploying Infisical with AWS Lightsail?">
-    Yes, here are a few that come to mind:
-    - In step 1.3, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags)
-    instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues.
-  
-    We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned!
-  </Accordion>
-</AccordionGroup>

docs/self-hosting/deployment-options/azure-app-services.mdx

@@ -1,71 +0,0 @@
----
-title: "Azure App Services"
-description: "Deploy Infisical with Azure App Service"
----
-
-Prerequisites:
-    - Have an account with [Microsoft Azure](https://azure.microsoft.com/en-us)
-
-<Steps>
-    <Step title="Create a Web App in Azure App Services">
-        1.1. In Azure, navigate to the **App Services** solution and press **Create > Web App**.
-        
-        ![Azure app services](/images/self-hosting/deployment-options/azure-app-services/aas-select-app-services.png)
-        
-        ![Azure create app service](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service.png)
-        
-        1.2. In the **Basics** section, specify the **Subscription** and **Resource group** to manage the deployed resource.
-        
-        Also, give the container a friendly name like Infisical and specify a **Region** for it to be deployed to.
-        
-        ![Azure app service basics](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service-basics.png)
-        
-        1.3. In the **Docker** section, select the **Single Container** option under **Options** and specify **Docker Hub** as the image source
-        
-        Next, under the **Docker hub options** sub-section, select the **Public** option under **Access Type** and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the **Image and tag** field; this will pull the image from Docker Hub.
-        
-        For example, in order to opt for Infisical `v0.43.4`, you would input: `infisical/infisical:v0.43.4`.
-        
-        ![Azure app service docker](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service-docker.png)
-        
-        1.4. Finally, in the **Review + create** section, double check the information from the previous steps and press **Create** to create the Azure app service.
-        
-        ![Azure app service review](/images/self-hosting/deployment-options/azure-app-services/aas-create-app-service-review.png)
-        
-        1.5. Next, wait a minute or two on the deployment overview page for the app to be created. Once the deployment is complete, press **Go to resource**
-        to head to the **App Service dashboard** for the newly-created app.
-
-        ![Azure app service deployment complete](/images/self-hosting/deployment-options/azure-app-services/aas-app-service-deployment-complete.png)
-        
-        1.6. Running Infisical requires a few environment variables to be set for the Azure app service.
-        At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-        which you can read more about [here](/self-hosting/configuration/envars).
-
-        <Note>
-            To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars).
-        </Note>
-        
-        Additionally, you must set the variable `WEBSITES_PORT=8080` since
-        Infisical listens on port `8080`.
-        
-        In the **Settings > Configuration** section of the newly-created app service, fill in the required environment variables.
-        
-        ![Azure app service deployment complete](/images/self-hosting/deployment-options/azure-app-services/aas-app-service-configuration.png)
-    </Step>
-    <Step title="Navigate to your deployed instance of Infisical">
-        In the **Overview** section, check out the **Default domain** for your instance of Infisical; you can visit the instance at this URL.
-
-        ![Azure app service deployment complete](/images/self-hosting/deployment-options/azure-app-services/aas-app-service-overview.png)
-    </Step>
-</Steps>
-
-<AccordionGroup>
-  <Accordion title="Do you have any recommendations for deploying Infisical with Azure App Services?">
-    Yes, here are a few that come to mind:
-    - In step 1.3, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags)
-    instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues.
-    - In step 1.2, we recommend selecting a **Region** option that is closest to your infrastructure/clients to reduce latency.
-  
-    We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned!
-  </Accordion>
-</AccordionGroup>

docs/self-hosting/deployment-options/azure-container-instances.mdx

@@ -1,88 +0,0 @@
----
-title: "Azure Container Instances"
-description: "Deploy Infisical with Azure Container Instances"
----
-
-Prerequisites:
-- Have an account with [Microsoft Azure](https://azure.microsoft.com/en-us)
-
-<Note>
-    This brief goes over how to deploy an instance of Infisical with Azure Container Instances without TLS/SSL configuration.
-
-    There are various options for enabling TLS/SSL with Azure Container Instances more suitable for production including:
-    - [Enabling a TLS endpoint in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-ssl).
-    - [Enabling automatic HTTPS with Caddy in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-automatic-ssl).
-    - Using Azure Function Proxies, Application Gateway, etc.
-
-    For a simpler deployment experience with complete TLS/SSL setup, you may try [deploying Infisical with Azure App Services](/self-hosting/deployment-options/azure-app-services).
-</Note>
-
-<Steps>
-    <Step title="Create a container instance in Azure Container Instances">
-        1.1. In Azure, navigate to the **Container Instances** solution and press **Create**.
-        
-        ![Azure container instance](/images/self-hosting/deployment-options/azure-container-instances/aci-select-container-instances.png)
-        
-        ![Azure create container instance](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance.png)
-        
-        1.2. In the **Basics** section, specify the **Subscription** and **Resource group** to manage the deployed resource.
-        
-        Also, give the container a friendly name like Infisical and specify a **Region** for it to be deployed to.
-
-        ![Azure container instance basics](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-basics-1.png)
-        
-        Next, select the **Public** option under **Image type** and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the **Image** field; this will pull the image from Docker Hub.
-        
-        For example, in order to opt for Infisical `v0.43.4`, you would input: `infisical/infisical:v0.43.4`.
-        
-        ![Azure container instance basics](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-basics-2.png)
-        
-        <Note>
-            Depending on your use-case and requirements, you may find it helpful to further configure your Azure container instance.
-
-            For example, you may want to adjust the **Region** option to specify which region to deploy the container for your
-            instance of Infisical to minimize distance and therefore latency between the instance and your infrastructure.
-        </Note>
-        
-        1.3. In the **Networking** section, select the **Public** option under **Networking type**; this will make the container accessible over the public internet.
-        
-        Next, under the **Ports** section, add an entry for port `8080` and protocol `TCP` since Infisical listens on port `8080`.
-        
-        ![Azure container instance networking](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-networking.png)
-        
-        1.4. Running Infisical requires a few environment variables to be set for the Azure container instance.
-        At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-        which you can read more about [here](/self-hosting/configuration/envars).
-        
-        In the **Advanced** section, fill in the required environment variables.
-        
-        <Note>
-            To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars).
-        </Note>
-        
-        ![Azure container instance advanced](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-advanced.png)
-        
-        1.5. Finally, in the **Review + create** section, double check the information from the previous steps and press **Create** to create the Azure container instance.
-
-        ![Azure container instance review](/images/self-hosting/deployment-options/azure-container-instances/aci-create-container-instance-review.png)
-    </Step>
-    <Step title="Navigate to your deployed instance of Infisical">
-        Head to the **Overview** page of the newly-created container instance to view its **IP address (Public)**; you can access your instance of Infisical by this IP address under the port `:8080`. 
-        
-        For example, in the image below, the IP address of the sample deployed container instance is `4.255.87.109`; the instance would be accessible in the browser by heading to `4.255.87.109:8080`.
-
-        ![Azure container instance overview](/images/self-hosting/deployment-options/azure-container-instances/aci-container-instance-overview.png)
-    </Step>
-</Steps>
-
-<AccordionGroup>
-  <Accordion title="Do you have any recommendations for deploying Infisical with Azure Container Instances?">
-    Yes, here are a few that come to mind:
-    - In step 1.2, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags)
-    instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues.
-    - In step 1.2, we recommend selecting a **Region** option that is closest to your infrastructure/clients to reduce latency.
-    - Enable TLS/SSL with Azure Container Instances. There are various options for doing so including [enabling a TLS endpoint in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-ssl), [enabling automatic HTTPS with Caddy in a sidecar container](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-container-group-automatic-ssl), and using Azure Function Proxies, Application Gateway, etc.
-  
-    We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned!
-  </Accordion>
-</AccordionGroup>

docs/self-hosting/deployment-options/docker-compose.mdx

@@ -1,54 +1,51 @@
 ---
 title: "Docker Compose"
-description: "Run Infisical with Docker Compose template"
+description: "Learn to install Infisical using our Docker Compose template"
 ---
 
-<Steps>
-  <Step title="Install Docker on your VM">
-    ```bash
-    # Example in ubuntu
-    apt-get update
-    apt-get upgrade
-    apt install docker-compose
-    ```
-  </Step>
-  <Step title="Download required files">
-    2.1. Run the command below to download the `.env` file template.
-    
-    ```bash
-    wget -O .env https://raw.githubusercontent.com/Infisical/infisical/main/.env.example
-    ```
-    
-    2.2. Run the command below to download the docker compose template.
-    
-    ```bash
-    wget -O docker-compose.yml https://raw.githubusercontent.com/Infisical/infisical/main/docker-compose.yml
-    ```
-    
-    2.3. Run the command below to download the `nginx` config file.
-    
-    ```bash
-    mkdir nginx && wget -O ./nginx/default.conf https://raw.githubusercontent.com/Infisical/infisical/main/nginx/default.dev.conf
-    ```
-  
-  </Step>
-  <Step title="Update the .env file">
-    Running Infisical requires a few environment variables to be set.
-    At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL` which you can read more about [here](/self-hosting/configuration/envars).
+## Install Docker on your VM
 
-    Tweak the `.env` accordingly.
+```bash
+# Example in ubuntu
+apt-get update
+apt-get upgrade
+apt install docker-compose
+```
 
-    ```bash
-    nano .env
-    ```
-  </Step>
-  <Step title="Start Infisical">
-    Finally, run the command below to get Infisical up and running (in detached mode).
+## Download the required files
 
-    ```bash
-    docker-compose -f docker-compose.yml up -d
-    ```
+```bash
+# Download env file template
+wget -O .env https://raw.githubusercontent.com/Infisical/infisical/main/.env.example
 
-    Your Infisical installation is complete and should be running on port `80` or `http://localhost:80`.
-  </Step>
-</Steps>
+# Download docker compose template
+wget -O docker-compose.yml https://raw.githubusercontent.com/Infisical/infisical/main/docker-compose.yml
+
+# Download nginx config
+mkdir nginx && wget -O ./nginx/default.conf https://raw.githubusercontent.com/Infisical/infisical/main/nginx/default.dev.conf
+```
+
+## Update .env file 
+Tweak the `.env` according to your preferences. Refer to the available [environment variables](/self-hosting/configuration/envars)
+
+```bash
+# update environment variables like mongo login
+nano .env
+```
+
+<Info>
+  Infisical assumes that you have configured HTTPS. If you didn't configure HTTPS, set `HTTPS_ENABLED` to `false` in the .env file to avoid frequent logouts.
+</Info>
+
+## Get the service up and running
+
+```bash
+# Start up services in detached mode
+docker-compose -f docker-compose.yml up -d
+```
+
+Your Infisical installation is complete and should be running on [http://localhost:80](http://localhost:80). Please note that the containers are not exposed to the internet and only bind to the localhost. It's up to you to configure a firewall, SSL certificates, and implement any additional security measures.
+
+<Info>
+Once installation is complete, you will have to create the first account. No default account is provided.
+</Info>

docs/self-hosting/deployment-options/fly.io.mdx

@@ -1,108 +1,63 @@
 ---
 title: "Fly.io"
-description: "Deploy Infisical with Fly.io"
+description: "Learn to install Infisical on Fly.io"
 ---
 
-Prerequisites:
-- Have an account with [Fly.io](https://fly.io/)
-- Have installed the [Fly.io CLI](https://fly.io/docs/hands-on/install-flyctl/)
+**Prerequisites**
+- Familiar with Fly.io deployment 
+- Logged in via fly CLI
 
-<Steps>
-  <Step title="Create an app with Fly.io">
-    In your terminal, run the following command from the source directory of your project to create a new Fly.io app
-    with a `fly.toml` configuration file:
-    
-    ```
-    fly launch
-    ```
-  </Step>
-  <Step title="Edit the fly.toml configuration file">
-    Add a **build** section to the `fly.toml` file to specify the [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical):
+#### 1. Make a copy of the deployment config
+To begin, you'll to make a copy of the following file on your local machine
 
-    ```
-    [build]                                                                         
-    image = "infisical/infisical:v0.43.4"
-    ```
+```toml fly.toml 
+# fly.toml app configuration file generated for infisical on 2023-05-05T08:57:03-04:00
+#
+# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
+#
 
-    Afterwards, your `fly.toml` file should look similar to:
+app = "infisical"
+primary_region = "iad"
 
-    ```
-    app = "infisical"
-    primary_region = "lax"
+[build]
+  image = "infisical/infisical:latest"
 
-    [http_service]
-    internal_port = 8080
-    force_https = true
-    auto_stop_machines = true
-    auto_start_machines = true
-    min_machines_running = 0
-    processes = ["app"]
+[env]
+  ENCRYPTION_KEY = <>
+  JWT_AUTH_SECRET = <>
+  JWT_REFRESH_SECRET = <>
+  JWT_SERVICE_SECRET = <>
+  JWT_SIGNUP_SECRET = <>
+  MONGO_URL = <>
 
-    [[vm]]
-    cpu_kind = "shared"
-    cpus = 1
-    memory_mb = 1024
+[http_service]
+  internal_port = 8080
 
-    [build]
-    image = "infisical/infisical:v0.43.4"
-    ```
-    
-    <Note>
-      Depending on your use-case and requirements, you may find it helpful to further configure your `fly.toml` file
-      with options [here](https://fly.io/docs/reference/configuration/).
+```
 
-      For example, you may want to adjust the `primary-region` option to specify which [region](https://fly.io/docs/reference/regions/) to create the new machine for your
-      instance of Infisical to minimize distance and therefore latency between the instance and your infrastructure.
-    </Note>
-    
-  </Step>
-  <Step title="Set secrets for your Fly.io app">
-    Running Infisical requires a few environment variables to be set on the Fly.io machine.
-    At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-    which you can read more about [here](/self-hosting/configuration/envars).
-    
-    For this step, we recommend setting the variables as Fly.io [app secrets](https://fly.io/docs/reference/secrets/) which 
-    are made available to the app as environment variables. You can set the variables either via the Fly.io CLI or project [dashboard](https://fly.io/dashboard).
-    
-    <Tabs>
-      <Tab title="CLI">
-        Run the following command (with each `VALUE` replaced) in the source directory of your project to set the required variables:
+#### 2. Add environment variables
 
-        ```
-        flyctl secrets set ENCRYPTION_KEY=VALUE AUTH_SECRET=VALUE MONGO_URL=VALUE REDIS_URL=VALUE...
-        ```
-      </Tab>
-      <Tab title="Dashboard">
-        In Fly.io, head to your Project > Secrets and add the required variables.
+Before we can deploy Infisical, we'll need to provide values for the keys under `[env]` config block. For each of the following keys
 
-        ![Fly.io deployment secrets](/images/self-hosting/deployment-options/flyio/flyio-secrets.png)
-      </Tab>
-    </Tabs>
-    
-    <Note>
-      To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars).
-    </Note>
-  </Step>
-  <Step title="Deploy the Fly.io app">
-    Finally, run the following command in the source directory of your project to deploy your Infisical instance on Fly.io
-    with the updated `fly.toml` configuration file from step 2 and secrets from step 3:
+- `ENCRYPTION_KEY`
+- `JWT_AUTH_SECRET`
+- `JWT_REFRESH_SECRET`
+- `JWT_SERVICE_SECRET`
+- `JWT_SIGNUP_SECRET`
 
-    ```
-    fly deploy
-    ```
-  </Step>
-</Steps>
+you will need to generate a random 16 byte hex string. This can can be generated with `openssl rand -hex 16`. 
 
-<AccordionGroup>
-  <Accordion title="Do you have any recommendations for deploying Infisical with Fly.io?">
-    Yes, here are a few that come to mind:
-    - In step 2, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags)
-    instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues.
-    - In step 2, we recommend selecting a `primary_region` option that is closest to your infrastructure/clients to reduce latency; a full list of regions supported by Fly.io can be found [here](https://fly.io/docs/reference/regions/).
-  
-    We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned!
-  </Accordion>
-</AccordionGroup>
 
-Resources:
-- [Fly.io documentation](https://fly.io/docs/)
+Lastly, the `MONGO_URL` environment variable requires a document database connection URL. 
+You can obtain this URL by creating a document database using services such as [MongoDB](https://www.mongodb.com/), [AWS DocumentDB](https://aws.amazon.com/documentdb/), and others.
+
+#### 3. Deploy
+
+Run `fly launch` in the directory where you have the local version of config from step 1 and follow the instructions. 
+Once done, your very own instance of Infisical should be up and running on Fly.io.
+
+Please note that this version of Infisical requires at least 250MB of memory to operate smoothly.
+
+<Info>
+Once installation is complete, you will have to create the first account. No default account is provided.
+</Info>

docs/self-hosting/deployment-options/gcp-cloud-run.mdx

@@ -1,67 +0,0 @@
----
-title: "GCP Cloud Run"
-description: "Deploy Infisical with GCP Cloud Run"
----
-
-Prerequisites:
-- Have an account with [Google Cloud Platform (GCP)](https://cloud.google.com/)
-
-<Steps>
-    <Step title="Create a project in GCP">
-        In GCP, create a new project and give it a friendly name like Infisical.
-
-        ![GCP create project](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-project.png)
-
-        ![GCP create project](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-project-2.png)
-    </Step>
-    <Step title="Create a service in GCP Cloud Run">
-        2.1. Inside the GCP project, navigate to the **Cloud Run** product and create a new service.
-        
-        ![GCP Cloud Run](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-select-cloud-run.png)
-
-        ![GCP Cloud Run create service](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-service.png)
-        
-        2.2. In the service creation form, select the **Deploy one revision from an existing container image** option and fill in your intended [Infisical public Docker image](https://hub.docker.com/r/infisical/infisical) in the container image URL.
-
-        For example, in order to opt for Infisical `v0.43.4`, you would input: `docker.io/infisical/infisical:v0.43.4`.
-        
-        ![GCP Cloud Run create service docker image specification](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-service-docker-image.png)
-
-        2.3. Running Infisical requires a few environment variables to be set for the GCP Cloud Run service.
-        At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-        which you can read more about [here](/self-hosting/configuration/envars).
-        
-        For this step, fill in the required environment variables in the Edit Container > Variables & Secrets > Environment variables section.
-        
-        <Note>
-            To use more features like emailing and single sign-on, you can set additional configuration options [here](/self-hosting/configuration/envars).
-        </Note>
-
-        ![GCP Cloud Run create service environment variable specification](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-create-service-envars.png)
-
-        <Note>
-            Depending on your use-case and requirements, you may find it helpful to further configure your GCP Cloud Run service.
-
-            For example, you may want to adjust the **Region** option to specify which region to deploy the underlying container for your
-            instance of Infisical to minimize distance and therefore latency between the instance and your infrastructure.
-        </Note>
-
-        Finally, press **Create** to finish setting up the GCP Cloud Run service.
-    </Step>
-    <Step title="Navigate to your deployed instance of Infisical">
-        Head to the **Service details** of the newly-created service to view its URL; you can access your instance of Infisical by clicking on the URL.
-        
-        ![GCP Cloud Run service details](/images/self-hosting/deployment-options/gcp-cloud-run/gcp-cloud-run-service-details.png)
-    </Step>
-</Steps>
-
-<AccordionGroup>
-  <Accordion title="Do you have any recommendations for deploying Infisical with GCP Cloud Run?">
-    Yes, here are a few that come to mind:
-    - In step 2, we recommend pinning the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags)
-    instead of referring to the `latest` tag to avoid any unexpected version-to-version migration issues.
-    - In step 2, we recommend selecting a **Region** option that is closest to your infrastructure/clients to reduce latency.
-  
-    We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned!
-  </Accordion>
-</AccordionGroup>

docs/self-hosting/deployment-options/kubernetes-helm.mdx

@@ -161,3 +161,4 @@ Once installation is complete, you will have to create the first account. No def
 
 ## Related blogs
 - [Set up Infisical in a development cluster](https://iamunnip.hashnode.dev/infisical-open-source-secretops-kubernetes-setup)
+- [Set up Infisical in AKS using ArgoCD + Helm and integrate with an application using kustomize](https://mrdevops.medium.com/infisical-open-source-secretops-apply-it-using-gitops-approach-245f57fcd67e)

docs/self-hosting/deployment-options/railway.mdx

@@ -1,61 +0,0 @@
----
-title: "Railway"
-description: "Deploy Infisical with Railway"
----
-
-Prerequisites:
-- Have an account with [Railway](https://railway.app/)
-
-<Steps>
-    <Step title="Deploy the Infisical template with Railway">
-        1.1. In Railway, create a new project and select **Deploy a template > Infisical**.
-        
-        ![Railway create project](/images/self-hosting/deployment-options/railway/railway-create-project.png)
-
-        ![Railway deploy template](/images/self-hosting/deployment-options/railway/railway-deploy-template.png)
-
-        ![Railway deploy template infisical](/images/self-hosting/deployment-options/railway/railway-deploy-template-infisical.png)
-        
-        ![Railway template overview](/images/self-hosting/deployment-options/railway/railway-template-overview.png)
-
-        1.2. At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-        which you can read more about [here](/self-hosting/configuration/envars).
-        
-        By default, the Infisical template on Railway pre-configures environment variables on each service in the deployment but requires you to supply two for the Redis and MongoDB services.
-        
-        On the MongoDB service, supply a value for the `MONGO_INITDB_ROOT_PASSWORD` variable.
-        
-        ![Railway template MongoDB configuration](/images/self-hosting/deployment-options/railway/railway-template-mongodb.png)
-        
-        On the Redis service, supply a value for the `REDIS_PASSWORD` variable.
-        
-        ![Railway template Redis configuration](/images/self-hosting/deployment-options/railway/railway-template-redis.png)
-        
-        ![Railway template Redis configuration](/images/self-hosting/deployment-options/railway/railway-template-redis.png)
-        
-        <Note>
-            To use more features like emailing and single sign-on, you can set additional configuration options on the Infisical service [here](/self-hosting/configuration/envars).
-        </Note>
-        
-        Finally, press **Deploy** to create the project and deploy the services within it.
-        
-        ![Railway template Infisical configuration](/images/self-hosting/deployment-options/railway/railway-template-infisical.png)
-        
-        ![Railway Infisical architecture](/images/self-hosting/deployment-options/railway/railway-infisical-architecture.png)
-    </Step>
-    <Step title="Navigate to your deployed instance of Infisical">
-        Head to the newly-created Infisical service to view its URL under Networking > Public Networking; you can access your instance of Infisical by clicking on the URL.
-        
-        ![Railway Infisical service](/images/self-hosting/deployment-options/railway/railway-infisical-service.png)
-    </Step>
-</Steps>
-
-<AccordionGroup>
-  <Accordion title="Do you have any recommendations for deploying Infisical with Railway?">
-    Yes, here are a few that come to mind:
-    - While the Infisical template on Railway uses the `latest` tag to get the latest version of Infisical, we recommend creating a Railway deployment that pins the Docker image to a specific [version of Infisical](https://hub.docker.com/r/infisical/infisical/tags) to avoid any unexpected version-to-version migration issues.
-    - We recommend selecting **Deployment region** options for your Railway service deployments to be closest to your infrastructure/clients to reduce latency.
-  
-    We're working on putting together a fuller list of deployment best practices as well as minimum resource configuration requirements for running Infisical so stay tuned!
-  </Accordion>
-</AccordionGroup>

docs/self-hosting/deployment-options/standalone-infisical.mdx

@@ -1,49 +1,65 @@
 ---
 title: "Docker"
-description: "Run Infisical with Docker"
+description: "Learn to install Infisical purely on docker"
 ---
 
-Prerequisites:
-- Basic knowledge of [Docker](https://www.docker.com/)
-- Have Docker installed on your system. If not, follow the installation guide [here](https://docs.docker.com/get-docker/).
+The Infisical standalone version combines all the essential components into a single container, making deployment and management more straightforward than other methods. 
 
-<Steps>
-  <Step title="Pull the Infisical Docker image">
-    Run the following command in your terminal to pull the Infisical Docker image:
-    
-    ```
-    docker pull infisical/infisical:latest
-    ```
-  </Step>
-  <Step title="Start Infisical">
-    2.1. Running Infisical requires a few environment variables to be set.
-    At minimum, Infisical requires that you set the variables `ENCRYPTION_KEY`, `AUTH_SECRET`, `MONGO_URL`, and `REDIS_URL`
-    which you can read more about [here](/self-hosting/configuration/envars).
-    
-    Once you have added the required environment variables to your docker run command, execute it in your terminal to get Infisical up and running.
-    
-    For example:
+## Prerequisites
 
-    ```bash
-    docker run -p 80:8080  \
-    -e ENCRYPTION_KEY=f40c9178624764ad85a6830b37ce239a \
-    -e AUTH_SECRET="q6LRi7c717a3DQ8JUxlWYkZpMhG4+RHLoFUVt3Bvo2U=" \
-    -e MONGO_URL="<>" \
-    infisical/infisical:latest
-    ```
-    
-    <Warning>
-      The above environment variable values are only to be used as an example and should not be used in production 
-    </Warning>
-    
-    2.2. Once the container is running, verify the installation by opening your web browser and navigating to `http://localhost:80`.
-  </Step>
-</Steps>
+This guide assumes you have basic knowledge of Docker and have it installed on your system. If you don't have Docker installed, please follow the official installation guide [here](https://docs.docker.com/get-docker/).
 
-<AccordionGroup>
-  <Accordion title="What are the system requirements for running Infisical?">
-    To have a functional deployment, we recommended compute with 2GB of RAM and 1 CPU.
-    
-    However, depending on your usage, you may need to further scale up system resources to meet demand.
-  </Accordion>
-</AccordionGroup>
+#### System requirements
+To have a functional deployment, we recommended compute with **2GB of RAM** and **1 CPU**.
+However, depending on your usage, you may need to further scale up system resources to meet demand.
+
+## Pull the Infisical Docker image
+
+Open your terminal or command prompt and enter the following command to pull the Infisical Docker image:
+
+```
+docker pull infisical/infisical:latest
+```
+
+## Run with docker 
+To run Infisical, we'll need to configure the required configs listed below.
+Other configs can be found [here](../configuration/envars)
+
+<ParamField query="ENCRYPTION_KEY" type="string" default="none" required>
+  Must be a random 16 byte hex string. Can be generated with `openssl rand -hex 16`
+</ParamField>
+
+<ParamField query="AUTH_SECRET" type="string" default="none" required>
+  Must be a random 16 byte hex string. Can be generated with `openssl rand -hex 16`
+</ParamField>
+
+<ParamField query="MONGO_URL" type="string" default="none" required>
+  A MongoDB connection string. Can use any MongoDB PaaS such as Mongo Atlas, AWS Document DB, etc. 
+  *TLS based connection string is not yet supported
+</ParamField>
+
+<ParamField query="REDIS_URL" type="string" default="none">
+  Redis connection string. Only required if you plan to use web integrations or secret reminders.
+</ParamField>
+
+
+Once you have added the required environment variables to your docker run command, execute it in your terminal.
+
+```bash
+docker run -p 80:8080  \
+-e ENCRYPTION_KEY=f40c9178624764ad85a6830b37ce239a \
+-e AUTH_SECRET=5239fea3a4720c0e524f814a540e14a2 \
+-e MONGO_URL="<>" \
+infisical/infisical:latest
+```
+
+<Warning>
+  The above environment variable values are only to be used as an example and should not be used in production 
+</Warning>
+
+## Verify the installation:
+Once the container is running, open a web browser and navigate to http://localhost:80. That's it! You have successfully installed the Infisical application using a single Docker image.
+
+<Info>
+Once installation is complete, you will have to create the first account. No default account is provided.
+</Info>

docs/self-hosting/overview.mdx

@@ -1,9 +1,10 @@
 ---
 title: "Introduction"
-description: "Self-host Infisical on your own infrastructure"
+description: "Explore deployment options for self hosting Infisical"
 ---
 
-Self-hosting Infisical lets you retain data on your own infrastructure and network.
+To meet various compliance requirements, you may want to self-host Infisical instead of using [Infisical Cloud](https://app.infisical.com/).
+Self-hosted Infisical allows you to maintain your sensitive information within your own infrastructure and network, ensuring complete control over your data.
 Choose from a variety of deployment options listed below to get started.
 
 <Card
@@ -21,6 +22,9 @@ Choose from a variety of deployment options listed below to get started.
   >
     Automatically create and deploy Infisical on to a Kubernetes cluster
   </Card>
+  <Card title="AWS EC2" color="#0285c7" href="deployment-options/aws-ec2">
+    Install infisical with just a few clicks using our Cloud Formation template
+  </Card>
   <Card
     title="Docker Compose"
     color="#0285c7"
@@ -29,59 +33,10 @@ Choose from a variety of deployment options listed below to get started.
     Install Infisical using our Docker Compose template
   </Card>
   <Card
-    title="Kubernetes"
-    color="#ea5a0c"
-    href="deployment-options/kubernetes-helm"
-  >
+  title="Kubernetes"
+  color="#ea5a0c"
+  href="deployment-options/kubernetes-helm"
+>
   Use our Helm chart to Install Infisical on your Kubernetes cluster
-  </Card>
-  <Card 
-    title="AWS EC2" 
-    color="#0285c7" 
-    href="deployment-options/aws-ec2"
-  >
-    Install infisical with just a few clicks using our Cloud Formation template
-  </Card>
-  <Card 
-    title="AWS Lightsail" 
-    color="#0285c7" 
-    href="deployment-options/aws-lightsail"
-  >
-    Deploy Infisical with AWS Lightsail
-  </Card>
-  <Card
-    title="GCP Cloud Run"
-    color="#ea5a0c"
-    href="deployment-options/gcp-cloud-run"
-  >
-    Deploy Infisical with GCP Cloud Run
-  </Card>
-  <Card
-    title="Azure App Services"
-    color="#ea5a0c"
-    href="deployment-options/azure-app-services"
-  >
-    Deploy Infisical with Azure App Services
-  </Card>
-  <Card
-    title="Azure Container Instances"
-    color="#ea5a0c"
-    href="deployment-options/azure-container-instances"
-  >
-    Deploy Infisical with Azure Container Instances
-  </Card>
-  <Card
-    title="Fly.io"
-    color="#ea5a0c"
-    href="deployment-options/fly.io"
-  >
-    Deploy Infisical with Fly.io
-  </Card>
-  <Card
-    title="Railway"
-    color="#ea5a0c"
-    href="deployment-options/railway"
-  >
-    Deploy Infisical with Railway
-  </Card>
+</Card>
 </CardGroup>

frontend/src/hooks/api/auditLogs/constants.tsx

@@ -50,8 +50,5 @@ export const userAgentTTypeoNameMap: { [K in UserAgentType]: string } = {
     [UserAgentType.WEB]: "Web",
     [UserAgentType.CLI]: "CLI",
     [UserAgentType.K8_OPERATOR]: "K8s operator",
-    [UserAgentType.TERRAFORM]: "Terraform",
-    [UserAgentType.NODE_SDK]: "InfisicalNodeSDK",
-    [UserAgentType.PYTHON_SDK]: "InfisicalPythonSDK",
     [UserAgentType.OTHER]: "Other",
 };

frontend/src/hooks/api/auditLogs/enums.tsx

@@ -8,9 +8,6 @@ export enum UserAgentType {
   WEB = "web",
   CLI = "cli",
   K8_OPERATOR = "k8-operator",
-  TERRAFORM = "terraform",
-  NODE_SDK = "node-sdk",
-  PYTHON_SDK = "python-sdk",
   OTHER = "other"
 }
 

frontend/src/views/SecretApprovalPage/components/SecretApprovalRequest/SecretApprovalRequest.tsx

@@ -63,7 +63,7 @@ export const SecretApprovalRequest = () => {
     (prev, curr) => ({ ...prev, [curr._id]: curr }),
     {}
   );
-  const myMembershipId = members?.find(({ user }) => user._id === presentUser?._id)?._id;
+  const myMembershipId = members?.find(({ user }) => user._id === presentUser._id)?._id;
   const isSecretApprovalScreen = Boolean(selectedApproval);
 
   const handleGoBackSecretRequestDetail = () => {
@@ -101,7 +101,7 @@ export const SecretApprovalRequest = () => {
           exit={{ opacity: 0, translateX: 30 }}
           className="rounded-md text-gray-300"
         >
-          <div className="flex items-center space-x-8 rounded-t-md border-x border-t border-mineshaft-600 bg-mineshaft-800 p-4 px-8">
+          <div className="p-4 px-8 flex items-center space-x-8 bg-mineshaft-800 rounded-t-md border-t border-x border-mineshaft-600">
             <div
               role="button"
               tabIndex={0}
@@ -110,7 +110,7 @@ export const SecretApprovalRequest = () => {
                 if (evt.key === "Enter") setStatusFilter("open");
               }}
               className={
-                statusFilter === "close" ? "text-gray-500 duration-100 hover:text-gray-400" : ""
+                statusFilter === "close" ? "text-gray-500 hover:text-gray-400 duration-100" : ""
               }
             >
               <FontAwesomeIcon icon={faCodeBranch} className="mr-2" />
@@ -118,7 +118,7 @@ export const SecretApprovalRequest = () => {
             </div>
             <div
               className={
-                statusFilter === "open" ? "text-gray-500 duration-100 hover:text-gray-400" : ""
+                statusFilter === "open" ? "text-gray-500 hover:text-gray-400 duration-100" : ""
               }
               role="button"
               tabIndex={0}
@@ -130,7 +130,7 @@ export const SecretApprovalRequest = () => {
               <FontAwesomeIcon icon={faCheck} className="mr-2" />
               {isSecretApprovalReqCountSuccess && secretApprovalRequestCount.closed} Closed
             </div>
-            <div className="flex flex-grow justify-end space-x-8">
+            <div className="flex-grow flex justify-end space-x-8">
               <DropdownMenu>
                 <DropdownMenuTrigger>
                   <Button
@@ -185,7 +185,7 @@ export const SecretApprovalRequest = () => {
               </DropdownMenu>
             </div>
           </div>
-          <div className="flex flex-col rounded-b-md border-x border-t border-b border-mineshaft-600 border-mineshaft-600 bg-mineshaft-800">
+          <div className="flex flex-col border-t border-mineshaft-600 bg-mineshaft-800 rounded-b-md border-b border-x border-mineshaft-600">
             {isRequestListEmpty && (
               <div className="py-12">
                 <EmptyState title="No more requests pending." />
@@ -246,9 +246,9 @@ export const SecretApprovalRequest = () => {
                   >
                     <div className="mb-2 flex items-center">
                       <FontAwesomeIcon icon={faCodeBranch} className="mr-2" />
-                      <Skeleton className="w-1/4 bg-mineshaft-600" />
+                      <Skeleton className="bg-mineshaft-600 w-1/4" />
                     </div>
-                    <Skeleton className="w-1/2 bg-mineshaft-600" />
+                    <Skeleton className="bg-mineshaft-600 w-1/2" />
                   </div>
                 ))}
               </div>

frontend/src/views/SecretApprovalPage/components/SecretApprovalRequest/components/SecretApprovalRequestAction.tsx

@@ -22,7 +22,6 @@ type Props = {
   isMergable?: boolean;
   status: "close" | "open";
   approvals: number;
-  canApprove?: boolean;
   statusChangeByEmail: string;
   workspaceId: string;
 };
@@ -34,8 +33,7 @@ export const SecretApprovalRequestAction = ({
   isMergable,
   approvals,
   statusChangeByEmail,
-  workspaceId,
-  canApprove
+  workspaceId
 }: Props) => {
   const { createNotification } = useNotificationContext();
   const { mutateAsync: performSecretApprovalMerge, isLoading: isMerging } =
@@ -85,11 +83,11 @@ export const SecretApprovalRequestAction = ({
 
   if (!hasMerged && status === "open") {
     return (
-      <div className="flex w-full items-center justify-between">
-        <div className="flex items-start space-x-4">
+      <div className="flex justify-between items-center w-full">
+        <div className="flex space-x-4 items-start">
           <FontAwesomeIcon
             icon={isMergable ? faSquareCheck : faSquareXmark}
-            className={twMerge("pt-1 text-2xl", isMergable ? "text-primary" : "text-red-600")}
+            className={twMerge("text-2xl pt-1", isMergable ? "text-primary" : "text-red-600")}
           />
           <span className="flex flex-col">
             {isMergable ? "Good to merge" : "Review required"}
@@ -100,31 +98,25 @@ export const SecretApprovalRequestAction = ({
           </span>
         </div>
         <div className="flex items-center space-x-2">
-          {canApprove ? (
-            <>
-              <Button
-                onClick={() => handleSecretApprovalStatusChange("close")}
-                isLoading={isStatusChanging}
-                variant="outline_bg"
-                colorSchema="secondary"
-                leftIcon={<FontAwesomeIcon icon={faClose} />}
-              >
-                Close request
-              </Button>
-              <Button
-                leftIcon={<FontAwesomeIcon icon={faCheck} />}
-                isDisabled={!isMergable}
-                isLoading={isMerging}
-                onClick={handleSecretApprovalRequestMerge}
-                colorSchema="primary"
-                variant="solid"
-              >
-                Merge
-              </Button>
-            </>
-          ) : (
-            <div>Only approvers can merge</div>
-          )}
+          <Button
+            onClick={() => handleSecretApprovalStatusChange("close")}
+            isLoading={isStatusChanging}
+            variant="outline_bg"
+            colorSchema="secondary"
+            leftIcon={<FontAwesomeIcon icon={faClose} />}
+          >
+            Close request
+          </Button>
+          <Button
+            leftIcon={<FontAwesomeIcon icon={faCheck} />}
+            isDisabled={!isMergable}
+            isLoading={isMerging}
+            onClick={handleSecretApprovalRequestMerge}
+            colorSchema="primary"
+            variant="solid"
+          >
+            Merge
+          </Button>
         </div>
       </div>
     );
@@ -132,9 +124,9 @@ export const SecretApprovalRequestAction = ({
 
   if (hasMerged && status === "close")
     return (
-      <div className="flex w-full items-center justify-between">
-        <div className="flex items-start space-x-4">
-          <FontAwesomeIcon icon={faCheck} className="pt-1 text-2xl text-primary" />
+      <div className="flex justify-between items-center w-full">
+        <div className="flex space-x-4 items-start">
+          <FontAwesomeIcon icon={faCheck} className="text-2xl text-primary pt-1" />
           <span className="flex flex-col">
             Change request merged
             <span className="inline-block text-xs text-bunker-200">
@@ -146,9 +138,9 @@ export const SecretApprovalRequestAction = ({
     );
 
   return (
-    <div className="flex w-full items-center justify-between">
-      <div className="flex items-start space-x-4">
-        <FontAwesomeIcon icon={faUserLock} className="pt-1 text-2xl text-primary" />
+    <div className="flex justify-between items-center w-full">
+      <div className="flex space-x-4 items-start">
+        <FontAwesomeIcon icon={faUserLock} className="text-2xl text-primary pt-1" />
         <span className="flex flex-col">
           Change request has been closed
           <span className="inline-block text-xs text-bunker-200">

frontend/src/views/SecretApprovalPage/components/SecretApprovalRequest/components/SecretApprovalRequestChanges.tsx

@@ -108,7 +108,6 @@ export const SecretApprovalRequestChanges = ({
     ({ user: membershipUser }) => membershipUser.email === user.email
   );
   const myMembershipId = myMembership?._id || "";
-  const canApprove = secretApprovalRequestDetails?.policy?.approvers?.includes(myMembershipId);
   const reviewedMembers = secretApprovalRequestDetails?.reviewers?.reduce<
     Record<string, ApprovalStatus>
   >(
@@ -165,30 +164,30 @@ export const SecretApprovalRequestChanges = ({
   return (
     <div className="flex space-x-6">
       <div className="flex-grow">
-        <div className="sticky top-0 z-20 flex items-center space-x-4 bg-bunker-800 pt-2 pb-6">
+        <div className="flex items-center space-x-4 pt-2 pb-6 sticky top-0 z-20 bg-bunker-800">
           <IconButton variant="outline_bg" ariaLabel="go-back" onClick={onGoBack}>
             <FontAwesomeIcon icon={faArrowLeft} />
           </IconButton>
-          <div className="flex items-center space-x-2 rounded-3xl bg-red-600 px-4 py-2 text-white">
+          <div className="bg-red-600 text-white flex items-center space-x-2 px-4 py-2 rounded-3xl">
             <FontAwesomeIcon icon={faCodeBranch} size="sm" />
             <span>{secretApprovalRequestDetails.status}</span>
           </div>
-          <div className="flex flex-grow flex-col">
-            <div className="mb-1 text-lg">
+          <div className="flex flex-col flex-grow">
+            <div className="text-lg mb-1">
               {generateCommitText(secretApprovalRequestDetails.commits)}
             </div>
-            <div className="flex items-center text-sm text-bunker-300">
+            <div className="text-sm text-bunker-300 flex items-center">
               {committer?.user?.firstName}
               {committer?.user?.lastName} ({committer?.user?.email}) wants to change{" "}
               {secretApprovalRequestDetails.commits.length} secret values in
-              <span className="mx-1 rounded bg-primary-600/60 px-1 text-primary-300">
+              <span className="text-primary-300 bg-primary-600/60 px-1 mx-1 rounded">
                 {secretApprovalRequestDetails.environment}
               </span>
-              <div className="flex w-min items-center rounded border border-mineshaft-500 pl-1 pr-2">
+              <div className="flex items-center border border-mineshaft-500 pl-1 pr-2 rounded w-min">
                 <div className="border-r border-mineshaft-500 pr-1">
                   <FontAwesomeIcon icon={faFolder} className="text-primary" size="sm" />
                 </div>
-                <div className="pl-2 pb-0.5 text-sm">{secretApprovalRequestDetails.secretPath}</div>
+                <div className="text-sm pl-2 pb-0.5">{secretApprovalRequestDetails.secretPath}</div>
               </div>
             </div>
           </div>
@@ -199,7 +198,7 @@ export const SecretApprovalRequestChanges = ({
                 leftIcon={hasApproved && <FontAwesomeIcon icon={faCheck} />}
                 onClick={() => handleSecretApprovalStatusUpdate(ApprovalStatus.APPROVED)}
                 isLoading={isApproving}
-                isDisabled={isApproving || hasApproved || !canApprove}
+                isDisabled={isApproving || hasApproved}
               >
                 {hasApproved ? "Approved" : "Approve"}
               </Button>
@@ -209,7 +208,7 @@ export const SecretApprovalRequestChanges = ({
                 leftIcon={hasRejected && <FontAwesomeIcon icon={faCheck} />}
                 onClick={() => handleSecretApprovalStatusUpdate(ApprovalStatus.REJECTED)}
                 isLoading={isRejecting}
-                isDisabled={isRejecting || hasRejected || !canApprove}
+                isDisabled={isRejecting || hasRejected}
               >
                 {hasRejected ? "Rejected" : "Reject"}
               </Button>
@@ -231,9 +230,8 @@ export const SecretApprovalRequestChanges = ({
             )
           )}
         </div>
-        <div className="mt-8 flex items-center space-x-6 rounded-lg bg-mineshaft-800 px-5 py-6">
+        <div className="flex items-center px-5 py-6 rounded-lg space-x-6 bg-mineshaft-800 mt-8">
           <SecretApprovalRequestAction
-            canApprove={canApprove}
             approvalRequestId={secretApprovalRequestDetails._id}
             hasMerged={hasMerged}
             approvals={secretApprovalRequestDetails.policy.approvals || 0}
@@ -246,7 +244,7 @@ export const SecretApprovalRequestChanges = ({
           />
         </div>
       </div>
-      <div className="sticky top-0 w-1/5 pt-4" style={{ minWidth: "240px" }}>
+      <div className="w-1/5 pt-4 sticky top-0" style={{ minWidth: "240px" }}>
         <div className="text-sm text-bunker-300">Reviewers</div>
         <div className="mt-2 flex flex-col space-y-2 text-sm">
           {secretApprovalRequestDetails?.policy?.approvers.map((requiredApproverId) => {
@@ -254,7 +252,7 @@ export const SecretApprovalRequestChanges = ({
             const status = reviewedMembers?.[requiredApproverId];
             return (
               <div
-                className="flex flex-nowrap items-center space-x-2 rounded bg-mineshaft-800 px-2 py-1"
+                className="flex items-center space-x-2 flex-nowrap bg-mineshaft-800 px-2 py-1 rounded"
                 key={`required-approver-${requiredApproverId}`}
               >
                 <div className="flex-grow text-sm">
@@ -280,7 +278,7 @@ export const SecretApprovalRequestChanges = ({
               const status = reviewedMembers?.[reviewer.status];
               return (
                 <div
-                  className="flex flex-nowrap items-center space-x-2 rounded bg-mineshaft-800 px-2 py-1"
+                  className="flex items-center space-x-2 flex-nowrap bg-mineshaft-800 px-2 py-1 rounded"
                   key={`required-approver-${reviewer.member}`}
                 >
                   <div className="flex-grow text-sm">