diff --git a/README.md b/README.md
index 7941c14828dab1b49e7b4629d8a8ed587362517b..9cbf50bf749b79c8a9df6e9f44c5f05acb820fa5 100644
--- a/README.md
+++ b/README.md
@@ -1,71 +1,23 @@
# Archi Back
+Back-end part for the Archi project.
+## Installation
-## Getting started
+First, download this repository and unzip it to the folder of your choice.
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+You will have to download Python [here](https://www.python.org/downloads) and install it on your computer.
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+**Note: if the installer asks you to install pip package manager, say yes or check the box.**
-## Add your files
+Then, use the included scripts to install Archi Back:
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+- On Windows, launch `setup.bat`.
+- On Linux/macOS, open a terminal inside the directory of the project then write
+```bash
+chmod +x ./setup.sh && ./setup.sh
```
-cd existing_repo
-git remote add origin https://gitlab.imt-atlantique.fr/FIL-A3-2024/ue-proj/archi-back.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.imt-atlantique.fr/FIL-A3-2024/ue-proj/archi-back/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
diff --git a/src/controllers/glb_controller.py b/src/controllers/glb_controller.py
index 84e859ba7fed5ff744e54cb4c3f83ecfa9390730..f4d34cca5790ca5c77c767f710c36749639cafe1 100644
--- a/src/controllers/glb_controller.py
+++ b/src/controllers/glb_controller.py
@@ -1,3 +1,4 @@
+import base64
import os
from gradio_client import Client, handle_file
from flask import jsonify, Response
@@ -27,7 +28,7 @@ class GlbController:
api_name="/get_seed"
)
- client.predict(
+ image_to_3d = client.predict(
image=handle_file(preprocess_image_result),
multiimages=[],
seed=get_seed_result,
@@ -45,4 +46,17 @@ class GlbController:
api_name="/extract_glb"
)
- return jsonify({"path": extract_glb})
+ extracted_glb_path = extract_glb[0]
+ preview_path = image_to_3d["video"]
+
+ glb = ''
+ with open(extracted_glb_path, "rb") as glb_file:
+ encoded_string = base64.b64encode(glb_file.read()).decode('utf-8')
+ glb = encoded_string
+
+ preview = ''
+ with open(preview_path, "rb") as preview_file:
+ encoded_string = base64.b64encode(preview_file.read()).decode('utf-8')
+ preview = encoded_string
+
+ return jsonify({"glb": glb, "glb_path": extracted_glb_path, "preview": preview, "preview_path": preview_path})