Dagger Hackathon - Flask App

[Schiiss]

As a hackathon host, I want to create a basic Flask application folks can run locally on their machine. The Flask app should be basic and should be developed to show off some of Daggers functionality.

The goal is to simulate a simple inventory management system for a small online store. The Flask app will allow the store manager to view and add products to the store’s inventory. Products have basic details such as a name, description, and price, stored in a CSV file that acts as the “database.”

Acceptance Criteria:

• Develop a Flask API that interacts with a CSV file that acts as the 'database'
• The CSV should contain the columns, ID, Name, Description, and Price (sample below)
• Create the API Routes mentioned below
• Build a few unit tests for these routes

API Routes

View Inventory (GET /items)

• The store manager can view all available products in the inventory.

---

Add New Product (POST /add_item)

• The store manager can add a new product to the inventory.

---

Sample CSV:

ID,Name,Description,Price
1,Wireless Mouse,Ergonomic design with wireless connectivity,25.99
2,Laptop Stand,Adjustable height stand for laptops,35.00
3,Bluetooth Headphones,Noise-canceling headphones with Bluetooth,59.99

[david-hurley]

@Schiiss love this. I'll propose a bit extra. I was watching this video about using Dagger llm function to ask questions overtop a postgres DB. I am spinning this up locally to try it out.

Could be cool to:

1. spinup a devcontainer that has python, postgres, flask (devcontainer is just to unify setup, nothing really to do with the dagger)
2. populate postgres db with some fake data (we can seed via script which would inject CSV)
3. flask app would actually interact with the agent and answer questions over locally running postgres db

Still do all the unit tests.

Could try to actually deploy, showcasing dagger's ability to containerize development????

Fee free to object to this, i'm going to toy with the postgres agent thing anyhow haha

[Schiiss]

@david-hurley, totally game for this, especially getting a postgres instance spun up instead of just using a CSV to mimic the database.

However, I think having folks build one dagger function to run the unit tests will be a lot since it will be a new concept for lots of people. However, lets still spin up a postgres instance regardless. I just dont know if building out the agent function will be too much?

Why dont we build out both the unit test function and the dagger ai agent and take it from there?

Let me know how that Dagger AI agent you found goes.

[david-hurley]

@david-hurley, totally game for this, especially getting a postgres instance spun up instead of just using a CSV to mimic the database.

However, I think having folks build one dagger function to run the unit tests will be a lot since it will be a new concept for lots of people. However, lets still spin up a postgres instance regardless. I just dont know if building out the agent function will be too much?

Why dont we build out both the unit test function and the dagger ai agent and take it from there?

Let me know how that Dagger AI agent you found goes.

makes sense! First step is if I can containerize the setup of dagger, postgres, etc. Otherwise, we probably should avoid postgres ha