Works by Paulo Viteri

Stack: Bun, TypeScript Express, ElysiaJS, Mongoose, DevOps, CI/CD, HTTP-requests, Redis (Node Cache), Discord API, Nix, Prettier, Docker, OnRender, Git and GitHub.

Description: A well-done rest API to get image of plushies, that is deployed with CI/CD on «OnRender» hosting at the same time a Gateway-only chatbot of Discord. Avaliable on one only repository.

How it works: Work In Progress (In development)

Stack: Lua, Shell, Git, Codeberg and Forgejo.

Description: It's literally the configuration of my system.

How it works: It just does.

Stack: NodeJS, TypeScript, SWC, NCC, Octokit, GitHub Actions, Git and GitHub.

Description: Display on your README your last activity on GitHub.

How it works: It takes your public events from GitHub's API, formats the events and writes them on your README and then pushes it to the original repository. You can configure it with a lot of parameters like what events you want to display or ignore some repositories.

Stack: NodeJS, TypeScript, SWC, VSCode Language Server, GitHub Actions, Language Embedding, Discord RPC, NPM Publish, Yarn, Git and Github.

Description: A Node Binary to be used like a Language Server Protocol and connect by IPC (Internal Process Call) to Discord and deploy a Rich Presence to the user's profile and show what's he/she doing on Lapce code editor. It can detect Git repostiories, supports scrippting and custom configuration.

How it works: It's like a service in the background while you are using Lapce Editor, but it starts when the plugin call it. It can detect languages, git repositories, scrippting, buttons, events, etc.

Stack: Rust, WASI, Git and GitHub.

Description: A simple plugin compiled to WASI (Web Assembly) that calls lapcord-server binaries and send plugin configuration.

How it works: It just get initialized when you open any file and lapcord-server do the rest.