Add Google Gemini Component, improvements and bugfixes

.dockerignore

@@ -1 +1,2 @@
-.venv/
+.venv/
+**/aws

.github/workflows/ci.yml

@@ -40,5 +40,5 @@ jobs:
         run: docker compose up --exit-code-from tests tests result_backend broker celeryworker db --build
         continue-on-error: true
 
-      - name: Stop services
-        run: docker compose down
+      # - name: Stop services
+      #   run: docker compose down

.github/workflows/pre-release.yml

@@ -8,6 +8,7 @@ on:
       - dev
     paths:
       - "pyproject.toml"
+  workflow_dispatch:
 
 env:
   POETRY_VERSION: "1.5.1"
@@ -40,7 +41,7 @@ jobs:
           generateReleaseNotes: true
           prerelease: true
           tag: v${{ steps.check-version.outputs.version }}
-          commit: main
+          commit: dev
       - name: Publish to PyPI
         env:
           POETRY_PYPI_TOKEN_PYPI: ${{ secrets.PYPI_API_TOKEN }}

Makefile

@@ -18,9 +18,12 @@ coverage:
 		--cov-report xml \
 		--cov-report term-missing:skip-covered
 
+# allow passing arguments to pytest
 tests:
 	@make install_backend
-	poetry run pytest tests --instafail
+
+	poetry run pytest tests --instafail $(args)
+# Use like:
 
 format:
 	poetry run ruff . --fix

README.md

@@ -115,7 +115,7 @@ Each option is detailed below:
 - `--install-completion [bash|zsh|fish|powershell|pwsh]`: Installs completion for the specified shell.
 - `--show-completion [bash|zsh|fish|powershell|pwsh]`: Shows completion for the specified shell, allowing you to copy it or customize the installation.
 - `--backend-only`: This parameter, with a default value of `False`, allows running only the backend server without the frontend. It can also be set using the `LANGFLOW_BACKEND_ONLY` environment variable.
-- `store`: This parameter, with a default value of `True`, enables the store features, use `--no-store` to deactivate it. It can be configured using the `LANGFLOW_STORE` environment variable.
+- `--store`: This parameter, with a default value of `True`, enables the store features, use `--no-store` to deactivate it. It can be configured using the `LANGFLOW_STORE` environment variable.
 
 These parameters are important for users who need to customize the behavior of Langflow, especially in development or specialized deployment scenarios. You may want to update the documentation to include these parameters for completeness and clarity.
 

cdk.Dockerfile

@@ -0,0 +1,20 @@
+FROM --platform=linux/amd64 python:3.10-slim
+
+WORKDIR /app
+
+# Install Poetry
+RUN apt-get update && apt-get install gcc g++ curl build-essential postgresql-server-dev-all -y
+RUN curl -sSL https://install.python-poetry.org | python3 -
+# # Add Poetry to PATH
+ENV PATH="${PATH}:/root/.local/bin"
+# # Copy the pyproject.toml and poetry.lock files
+COPY poetry.lock pyproject.toml ./
+# Copy the rest of the application codes
+COPY ./ ./
+
+# Install dependencies
+RUN poetry config virtualenvs.create false && poetry install --no-interaction --no-ansi
+
+RUN poetry add pymysql==1.0.2
+
+CMD ["sh", "./container-cmd-cdk.sh"]

container-cmd-cdk.sh

@@ -0,0 +1,3 @@
+export LANGFLOW_DATABASE_URL="mysql+pymysql://${username}:${password}@${host}:3306/${dbname}"
+# echo $LANGFLOW_DATABASE_URL
+uvicorn --factory src.backend.langflow.main:create_app --host 0.0.0.0 --port 7860 --reload --log-level debug

docker-compose.yml

@@ -1,28 +1,35 @@
 version: "3"
+networks:
+  langflow:
 
 services:
   backend:
     build:
       context: ./
       dockerfile: ./dev.Dockerfile
+    env_file:
+      - .env
     ports:
       - "7860:7860"
     volumes:
       - ./:/app
     command: bash -c "uvicorn --factory src.backend.langflow.main:create_app --host 0.0.0.0 --port 7860 --reload"
-
+    networks:
+      - langflow
   frontend:
     build:
       context: ./src/frontend
-      dockerfile: ./dev.Dockerfile
+      dockerfile: ./cdk.Dockerfile
       args:
         - BACKEND_URL=http://backend:7860
     environment:
       - VITE_PROXY_TARGET=http://backend:7860
     ports:
-      - "3000:3000"
+      - "8080:3000"
     volumes:
       - ./src/frontend/public:/home/node/app/public
       - ./src/frontend/src:/home/node/app/src
       - ./src/frontend/package.json:/home/node/app/package.json
     restart: on-failure
+    networks:
+      - langflow

docs/docs/components/custom.mdx

@@ -34,6 +34,7 @@ The CustomComponent class serves as the foundation for creating custom component
   | --------------------------------------------------------- |
   | _`str`_, _`int`_, _`float`_, _`bool`_, _`list`_, _`dict`_ |
   | _`langflow.field_typing.NestedDict`_                      |
+  | _`langflow.field_typing.Prompt`_                         |
   | _`langchain.chains.base.Chain`_                           |
   | _`langchain.PromptTemplate`_                              |
   | _`langchain.llms.base.BaseLLM`_                           |
@@ -48,10 +49,17 @@ The CustomComponent class serves as the foundation for creating custom component
   The difference between _`dict`_ and _`langflow.field_typing.NestedDict`_ is that one adds a simple key-value pair field, while the other opens a more robust dictionary editor.
 
   <Admonition type="info">
-    Unlike Langchain types, base Python types do not add a
+      To use the _`Prompt`_ type, you must also add _`**kwargs`_ to the _`build`_ method. This is because the _`Prompt`_ type passes new arbitrary keyword arguments to it.
+
+      If you want to add the values of the variables to the template you defined, you must format the PromptTemplate inside the CustomComponent class.
+        </Admonition>
+
+
+  <Admonition type="info">
+      Unlike Langchain types, base Python types do not add a
     [handle](../guidelines/components) to the field by default. To add handles,
     use the _`input_types`_ key in the _`build_config`_ method.
-  </Admonition>
+        </Admonition>
 
 - **build_config**: Used to define the configuration fields of the component (if applicable). It should always return a dictionary with specific keys representing the field names and corresponding configurations. This method is called when the code is processed (i.e., when you click _Check and Save_ in the code editor). It must follow the format described below: