Skip to content

Commit

Permalink
testing langchain and ready for v2 release
Browse files Browse the repository at this point in the history
  • Loading branch information
JAlcocerT committed Dec 25, 2024
1 parent f7eb623 commit fb46621
Show file tree
Hide file tree
Showing 11 changed files with 552 additions and 7 deletions.
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
*_venv/
.env
3 changes: 2 additions & 1 deletion Deploy/Docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,5 @@ services:
container_name: tripplanner
ports:
- 8051:8050
restart: unless-stopped
restart: unless-stopped
command: python3 ./app/app.py
9 changes: 7 additions & 2 deletions Deploy/README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,14 @@
# Local Deployment

Deploy me with docker!
[**Deploy**](https://fossengineer.com/understanding-containers-for-selfhosting/) me with docker!


**Container Image** creation:

* [DockerHub - x86,ARM32/64](https://hub.docker.com/repository/docker/fossengineer/trip_planner/general)
* [Build Locally](https://fossengineer.com/building-docker-container-images/#building-images-locally-x86-arm32-arm64)
* Use [Github Actions MultiArch CI/CD](https://jalcocert.github.io/JAlcocerT/github-actions-use-cases/#actions-cicd-for-python-projects)


## Usage

Expand Down Expand Up @@ -33,7 +38,7 @@ docker run -p 8051:8050 --name trip-planner fossengineer/trip-planner:latest

Simply pulling `fossengineer/trip-planner:latest` will retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:
The **architectures supported** by this container image are:

| Architecture | Available | Tag |
| :----: | :----: | ---- |
Expand Down
1 change: 1 addition & 0 deletions Development/readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
> [Post](https://jalcocert.github.io/JAlcocerT/blog/dev-in-docker/)
46 changes: 43 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,50 @@

Using **historical weather data** together with location data in a DASH App to answer your question: **How is the expected weather at a particular period of the year in my destination?**

* [Deployed the App](https://github.com/JAlcocerT/Py_Trip_Planner/tree/main/Deploy)
* [Deploy the App](https://github.com/JAlcocerT/Py_Trip_Planner/tree/main/Deploy)
* Further Description at:
* For V1: Historical Weather, [MeteoStat](https://jalcocert.github.io/JAlcocerT/python-trip-planner/)
* For V2: Historical and [Forecast Weather](https://jalcocert.github.io/JAlcocerT/python-weather-forecast-with-open-meteo-api/)
* For V1: Historical Weather, with [MeteoStat](https://jalcocert.github.io/JAlcocerT/python-trip-planner/)
* For V2: Historical and [Forecasted Weather](https://jalcocert.github.io/JAlcocerT/python-weather-forecast-with-open-meteo-api/)
* For V3: Adding AI capabilities - [Chat with Weather Data DF via LangChain](https://jalcocert.github.io/JAlcocerT/using-langchain-with-pandas-df/)



###$ Quick Setup

> [!IMPORTANT]
> Prepare the API key for v3

<details>
<summary>Using Python Venv...👇</summary>
&nbsp;


```sh
#sudo apt install python3.12-venv
python3 -m venv trip_planner_venv

#Unix
source trip_planner_venv/bin/activate
#.\trip_planner_venv\Scripts\activate #Windows

pip install -r requirements.txt


source .env
#export OPENAI_API_KEY="your-api-key-here"
#set OPENAI_API_KEY=your-api-key-here
#$env:OPENAI_API_KEY="your-api-key-here"
echo $GROQ_API_KEY $OPENAI_API_KEY $ANTHROPIC_API_KEY

streamlit run Z_ST_AIssistant_v2.py

# git add .
# git commit -m "better st offer analyzer"
# git push
```

</details>

## Powered Thanks To ❤️

Expand Down
Loading

0 comments on commit fb46621

Please sign in to comment.