Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] TT-39 - Connect with Google Cloud storage #1

Merged
merged 15 commits into from
Jun 18, 2024

Conversation

Appli-chic
Copy link
Contributor

📝 Description

Create routes to download, upload and get all the images.
Make the connection with Google Cloud.
Setup the system of environment variables.

To Improve:
The management of the storage and to get the blob.

🖼️ Media

Download

image

Upload

image

Get all images

image

https://cheerz0.atlassian.net/browse/TT-39

@Appli-chic Appli-chic self-assigned this May 31, 2024
embeddedServer(Netty, port = 8080, host = "0.0.0.0", module = Application::module)
.start(wait = true)
}
val storage = StorageOptions.getDefaultInstance().service
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 Il faudra qu'on regarde pour bien gérer le storage.

@Appli-chic Appli-chic changed the title [Feat ] TT-39 - Connect with Google Cloud storage [Feat] TT-39 - Connect with Google Cloud storage May 31, 2024
val id: String,
val type: MediaType
@SerialName("id") val id: String,
@SerialName("type") val type: MediaType,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🕐 Il faudrait ajouter l'uri pour la renvoyer dans la réponse API

@Appli-chic Appli-chic merged commit 388b855 into main Jun 18, 2024
1 check passed
@Appli-chic Appli-chic deleted the TT-39-config-gcloud branch June 18, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants