Termiview
- 4 Devlogs
- 5 Total hours
A focused workspace for the files, shells, and SSH servers that keep your homelab running.
A focused workspace for the files, shells, and SSH servers that keep your homelab running.
I just fixed macOS compatability (to some extent). Because of it’s nature I had to resourt to an alternative to PTY style terminals. I also fixed the settings menu (stale accent color picker) and added new features such as manual update checks, and syncing the terminal path to the file explorer.
I’ve been debugging this theme editor for the past ~20 minutes. It turns out that VSCode live preview is NOT as trustworthy as you think it is. I’ve been testing using live preview and it works perfectly fine. But as soon as I push into production, there’s 404s in the console. So I’ve been trying to fix them, I’ve redeployed too many times but I just fixed it. I also updated my prod.sh to completely handle updating for me. It creates new commits, releases, etc etc based on what kind of update I did. So a site update won’t trigger a new release now like it did before.
I just added a theme editor! This is linked on the main website (termiview.xyz) and it lets you design custom termiview themes so it doesn’t look as bland as it does right now. Termiview instances now have a capability to load these custom themes ofc
Termiview is essentially an ssh client without the ssh designed to make navigating your server easy. It has a file explorer that lets you view, edit, and move your files with a GUI instead of via commands. It also has a terminal so you can actually do stuff on your server. I plan on later adding an AI mode to this which can either use local or cloud models to execute tasks on your server, so basically set things up FOR you when you tell it to. Oh and it also works on macOS. This first devlog gets the basis ready, the site, and the actual termiview instances itself. It’s perfectly usable at this point in time