-
Notifications
You must be signed in to change notification settings - Fork 181
Integrated Terminal #133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From https://basarat.gitbooks.io/alm/content/config/command-line.html
There is stuff in there for https + auth. Which should allow you to host publicly if you want to 🌹 Let me know if I've missed the point though :) |
I've seen that, but maybe I didn't understand it. My point is - when it's running online - how do I access the bash on that docker container or VM or wherever it's running, without having SSH. Cloud 9 and other online editors expose a terminal window of sorts where you basically have a bash which is executed against a VM bash |
Got it. You want an integrated terminal. That's not present at the moment. |
Is that something we could send a PR for? Just discovered this project, it's spectacular. |
Awww 💯 x🌹.
Adding a single terminal will not be that hard (best to register it as a The main thing that's holding me back is that my current priority is to allow people to @stubailo Currently are you using remotely or on the same machine? |
I'm using it remotely and from a Chromebook, so the electron thing doesn't help at all. I'm trying out a cloud dev environment with this and terminal.com, just for special cases when I'm away from my main computer. Right now I can just open two windows, one with the terminal and one with the editor. But it would be cool to just have one window. |
Awesome. Then I'll prioritize it over the other thing. |
Hit a blocker. I'm very cautious about adding anything that might force people to have a working node-gyp toolchain as I just want them to have The way xterm.js talks to the backend right now is through
|
Other terminal emulators (all electron apps) out there are black-screen (also uses pty.js just with nan updated https://github.com/shockone/black-screen/blob/bc4548769ace3c3256c46b7490f550ed24a1f675/package.json#L38) and the new kid on the block So I'll try https://www.npmjs.com/package/child_pty 🌹 Unblocked ❤️ |
Also node-gyp :-/ https://github.com/Gottox/child_pty/blob/master/binding.gyp . Blocked again. |
What's wrong with gyp? Can't we use something like node pre gyp to distribute builds? Or perhaps we just don't want to take on the burden of compiling things for people, which I would totally understand. |
That too. Also we want the contribution curve to be just as light as the end user usage curve. If someone can use the IDE, they should find it intuitive to contribute to the IDE. Hence all the love we put here : https://basarat.gitbooks.io/alm/content/contributing/ 🌹 Fresh ResearchIntelliJ https://github.com/JetBrains/jediterm/blob/master/README.md uses pty4j https://github.com/traff/pty4j |
Closing till a non node-gyp solution for |
Quick question: Is alm server running on the chromebook too? If so, is this the only IDE for TypeScript on a chromebook? |
No - I am running the server remotely and typing into the editor on a chromebook :] |
The answer to your question is still yes, though! |
Hi, I assume at the moment alm works great locally or if you have SSH access to the server where you run it.
Did you think about making it available via docker or similar? In that case it would be harder for people to get SSH access and instead they could use some shell window in the browser UI.
I understand that there are many more points which need to be addressed if people would want to use alm that way. But from my point of view, this is a blocker before deploying on a server where users could access it just via http.
I was even thinking about making a sandstorm package out of this, but I'm not yet sure how straight forward it's going to be due to the network limitations in sandstorm applications.
What do you think? Cheers, Peter
The text was updated successfully, but these errors were encountered: