vohoanglong0107 / pbl4

A web-based English problems solver for the self-taught

Hi 👋, I'm Long

A Vietnamese Vim enjoyer write code for a living in Japan

• 🔭 I’m currently working on adding GraphQL to Biome and rewriting Bors

• 🌱 I’m currently learning Rust, and maybe Go or Japanese

• 📫 How to reach me [email protected]

• ⚡ Fun fact 39 in Japanese is slang for "Thank you"

Connect with me:

Languages and Tools:

GitHub status

pbl4's Issues

Add NLP reading comprehensive model

Adding NLP reading comprehensive model

Join both backend and torchserve on a cluster

Right now backend is deployed manually on digital ocean droplet, and torchserve is deployed separately on a cluster of 3 nodes also on Digital Ocean, which wasted a loss of resources. Should bring both of them on a same kubernetes cluster

• #6
• Bring backend and db to the same kubernetes
• change current load balance to ingress and nginx or traefik

Unified frontend and backend to the same repo

At the start, I divided this project to 4 smaller project for easier management and, however it make this project scatter around many repos, which is not really good to look at when some one might want to look at this project. So this issues is to attempt to unified all the smaller repos into one giant black thick repo. Might start writing my first blog on from torch model to deploy using kubernetes and torch serve, to hone my communications skill.

• Join frontend and backend repo
• Join frontend to the same cluster
• (? May or may not) Write a blog about.

Find a way to deploy both rook / ceph and torchsever on a same helm release

Add support for database to save history