-
Notifications
You must be signed in to change notification settings - Fork 16
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
Run meteor on Android (Termux) #36
Comments
Hi Joe ( @trusktr ) I like the idea and will start a thread on that. I do not like to run a special fork, currently I get everything in this ARM fork and make some system depend changes. So I will check how it could be possible to provide Termux as well. Cheers |
Sounds great!! It will be so nice to be able to develop on a phone while on the go! |
Joseph, on what device and Android release are you running Termux? |
@trusktr Joseph - I just mentioned you here to be sure you get my comments |
@trusktr does termux-fix-shebang of termux help to make it work? |
From Joe ( @trusktr ) at: forums.meteor.com
Hello Tom, I'm using Termux for Android2 which provides a sandboxed linux environment (as in it runs everything in it's app-specific filesystem, not on the user's sdcard and not in root (my phone isn't rooted)) with Debian's apt-get for package management (I've installed NeoVim, which works great in the terminal!). I was trying to get your universal Meteor fork (that you mentioned on GitHub) running inside this environment but came across a small problem: the beginning of the (JavaScript) Meteor scripts all start with
but /usr doesn't exist on the phone, which errors out. As a workaround, I can start to fix the problem by editing each file so it has
and same for bash scripts, etc. What might be a good way to solve this so that we don't have to manually change the beginning of these files (without needing to root a phone)? Maybe a script that converts all
#!/usr/bin/env
to#!/data/data/com.termux/files/usr/bin/env
would do the trick, and we can host a branch for Termux users to clone?The text was updated successfully, but these errors were encountered: