S3samuel-file-updated

Dockerfile

@@ -0,0 +1,17 @@
+# Use an official Python runtime as the base image
+FROM python:3.9-slim
+
+# Set the working directory inside the container
+WORKDIR /app
+
+# Copy the current directory contents into the container at /app
+COPY . /app
+
+# Install the required dependencies
+RUN pip install --no-cache-dir Flask
+
+# Expose port 5000 (the default Flask port)
+EXPOSE 5000
+
+# Set the command to run the application when the container starts
+CMD ["python", "app.py"]

README.md

@@ -1,3 +1,4 @@
 # S4-projects
 
 ![del](https://user-images.githubusercontent.com/96950933/216551396-58ffa498-0148-4a61-97ac-74aaeb0bd115.png)
+Hello ! I'm learning devops to be on my way of getting 6 figures income.

espresso-shop/README.md

@@ -1 +1 @@
-# S3 Project 01
+# S3 for all sd bsfdbdffefefed student Project 01 cnadxchhy kjx;cvdsavdgvf

restaurant-app/yelb-appserver/README.md

@@ -1,3 +1,3 @@
 This is the application server. It's a Ruby/Sinatra application that exposes a number of APIs that are consumed by the UI (or via curl if you fancy that). 
 
-Originally this application was included in a single file (`yelb-appserver.rb`). This has been since refactored by extracting the single API definition in their separate adapters and modules. This made the transition to Lambda/Serverless easier (one lambda per API definition). This hasn't changed the other deployment models (containers and instances) because those models still launch the `yelb-appserver.rb` main application which imports the modules instead of having everything in a single file (as it was conceived originally).
+Originally this application was included \er (one lambda per API definition). This hasn't changed the other deployment models (containers and instances) because those models still launch the `yelb-appserver.rb` main application which imports the modules instead of having everything in a single file (as it was conceived originally). vn  nvn m fhbmn