[GH-ISSUE #316] Deployment/production guide? #81

New issue

Open

opened 2026-03-02 23:44:23 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 23:44:23 +03:00

Owner

Originally created by @tommerty on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/316

Hi there,

I know this is not recommended for production use yet, however we were wanting to test out publishing for internal testing. While I could likely brute force and figure out how to handle this, following provided documentation/recommendations is always preferred.

Is there any possibility of a basic deployment guidelines? Simulating/replicating ssh terminal.shop for example

Originally created by @tommerty on GitHub (Nov 14, 2025). Original GitHub issue: https://github.com/anomalyco/opentui/issues/316 Hi there, I know this is not recommended for production use yet, however we were wanting to test out publishing for internal testing. While I could likely brute force and figure out how to handle this, following provided documentation/recommendations is always preferred. Is there any possibility of a basic deployment guidelines? Simulating/replicating `ssh terminal.shop` for example

kerem added the

core

question

labels

2026-03-02 23:44:23 +03:00

kerem commented

2026-03-02 23:44:24 +03:00

Author

Owner

@kommander commented on GitHub (Nov 14, 2025):

So terminal.shop is just getting started with the migration and there are some essentials missing like #238 and #302. Additionally some things are not renderer scoped yet and would make it impossible to handle multiple user sessions in the same process, which is a blocker imo. I would love to have a layer on top that makes ssh user session handling simple.

It's quite some stretch to go still to a production guide I am afraid.

That said, for standalone executables the example build in the pipeline and opencode releases are a good source on how that can be done at least.

@kommander commented on GitHub (Nov 14, 2025): So terminal.shop is just getting started with the migration and there are some essentials missing like #238 and #302. Additionally some things are not renderer scoped yet and would make it impossible to handle multiple user sessions in the same process, which is a blocker imo. I would love to have a layer on top that makes ssh user session handling simple. It's quite some stretch to go still to a production guide I am afraid. That said, for standalone executables the example build in the pipeline and opencode releases are a good source on how that can be done at least.

kerem referenced this issue

2026-03-02 23:45:43 +03:00

[PR #81] [MERGED] Feat: vue renderer #273

kerem referenced this issue

2026-03-02 23:45:47 +03:00

[PR #99] [CLOSED] feat(core): add title change method #285

kerem referenced this issue

2026-03-14 09:15:55 +03:00

[PR #81] [MERGED] Feat: vue renderer #1052

kerem referenced this issue

2026-03-14 09:16:28 +03:00

[PR #99] [CLOSED] feat(core): add title change method #1066