-
Notifications
You must be signed in to change notification settings - Fork 276
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
Bundle Chrome for local development #3
Comments
Pi isn't really powerful enough for that |
well @danielchatfield Chromium is built and works without too many problems on RPi in ArchLinux. It won't probably work in a reasonable way due to hard caching with the browser based IDE but Raspberry Pi can run Chrome like browsers without issues. That said, @nmec apparently this system is built to be handled remotely so you won't be able to reach current.local via your own PI. There is another "bug" opened about this. |
@WebReflection I know it works, I've run hexxeh's build on it but everything is very slow, and thus I do not think it should be bundled with this as it isn't really useable. |
I was rather hoping that some work could be done to optimise Chrome for the Pi's limited processor and memory. |
Chromium ( |
I bought my Pi couple of days back and I was really keen on a use case where it can be used as a Web development tool. Even if we use Chromium browser as just a single tab, just for running Coder, it would be a great-to-have. My use case is a classroom of students learning web development, each of them equipped with only a Ra-Pi. I think that is a lovely use case to support, given that Coder is perfectly equipped for just that. It could be very cost-effective, if not anything else. |
For those of you who have installed chromium yourself but are still having trouble accessing coder through it, @oschettler found that you need to browse to https://coder.local:8081/. There's a bit more info over in issue #55 |
I imagine that Coder will work pretty well on a Raspberry Pi 2 and Epiphany. With regards to the hostname issue, couldn't you just do https://127.0.0.1:8081/? |
It would be great if there was a version of Chrome or perhaps Chrome OS bundled with this so development could be done directly on the Pi, without the need for an additional computer.
I understand that porting Chrome is no small feat, but right now support for HTML5 on the Pi is pretty poor.
The text was updated successfully, but these errors were encountered: