{"id":24736547,"url":"https://github.com/phukon/guava-term","last_synced_at":"2026-04-09T18:40:06.721Z","repository":{"id":230456478,"uuid":"778495589","full_name":"phukon/guava-term","owner":"phukon","description":"Interact with your Vercel deployment's build container through it's bash terminal.","archived":false,"fork":false,"pushed_at":"2024-03-29T20:28:47.000Z","size":32,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-01-27T21:26:15.808Z","etag":null,"topics":["bash","linux","terminal"],"latest_commit_sha":null,"homepage":"","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/phukon.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2024-03-27T20:29:02.000Z","updated_at":"2024-04-21T17:12:34.000Z","dependencies_parsed_at":"2024-03-29T21:32:24.303Z","dependency_job_id":"38c52a68-c73c-43a8-bf65-d7c5d44d7c48","html_url":"https://github.com/phukon/guava-term","commit_stats":null,"previous_names":["phukon/guava-term"],"tags_count":1,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phukon%2Fguava-term","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phukon%2Fguava-term/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phukon%2Fguava-term/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/phukon%2Fguava-term/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/phukon","download_url":"https://codeload.github.com/phukon/guava-term/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":244992881,"owners_count":20543877,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bash","linux","terminal"],"created_at":"2025-01-27T21:26:12.820Z","updated_at":"2025-10-12T21:42:51.545Z","avatar_url":"https://github.com/phukon.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cimg alt=\" Interact with your Vercel deployment's build container through it's bash terminal.\" src=\"https://github.com/phukon/guava/assets/60285613/e352cda2-5df6-477f-a1b0-5a5a7b9f5eeb\"\u003e\n\n\u003ch3 align=\"center\"\u003eguava-term\u003c/h3\u003e\n\n\u003cp align=\"center\"\u003e\n    Interact with your Vercel deployment's build container through it's bash terminal\n    \u003cbr /\u003e\n    \u003ca href=\"#http-implementation\"\u003e\u003cstrong\u003eHTTP\u003c/strong\u003e\u003c/a\u003e ·\n    \u003ca href=\"#websocket-implementation\"\u003e\u003cstrong\u003eWebSocket\u003c/strong\u003e\u003c/a\u003e ·\n\u003c/p\u003e\n\n\u003cbr/\u003e\n\nThis project enables remote interaction with a Vercel Build container through it's bash terminal using child processes. I initially wrote this to explore the remote environment and use the `/temp` directory of a Vercel Build Docker container. {see more @ [Vercel Builds](https://vercel.com/docs/deployments/builds) }\n\nFor a Next.js implementation, check [guava-next](https://github.com/phukon/guava-next)\n\n## HTTP implementation\n\ndir: `plain-http` + root `index.js`\nEverything is stateless on the `HTTP` implementation. The `child process` is killed after every command or should I say for every new command, a new `child process` is spun up.\n\n## WebSocket implementation\n\ndir: `websocket`\nAll commands are piped to the same `child process`.\n\n## Getting Started\n\nTo set up and run the application, follow these steps:\n\n### HTTP\n\n1.  `pnpm install`\n2.  Set `HOST_NAME` in `.env`\n3.  Then `node index.js` to spin up the server.\n4.  Finally `node plain-http/hclient.js` to start the client.\n\n### Websocket\n\n1. Run `node websocket/index.js` to spin up the server.\n2. Point to your server address in `websocket/client.js`\n3. Then `node websocket/client.js`to use the websocket client.\n\n### Usage\n\n#### Server Side\n\n1.  Run the server:\n\n    `node hclient.js`\n\n    The server will start listening on port 8080.\n\n#### Client Side\n\n1.  Run the client:\n\n    `node client.js`\n\n    This will prompt you to enter a command.\n\n2.  Enter the desired command and press Enter.\n\n    The command will be sent to the server, executed in a bash terminal, and the output will be displayed in the client console.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fphukon%2Fguava-term","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fphukon%2Fguava-term","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fphukon%2Fguava-term/lists"}