pebble / cloudpebble-composed

Local development setup for CloudPebble
21 stars 36 forks source link

CloudPebble does not work as-is #4

Open hbh7 opened 6 years ago

hbh7 commented 6 years ago

Hi all. I did some further poking around and discovered a few things, and even got it running after a while.

(Please see my post here https://www.reddit.com/r/pebble/comments/9fs3ob/looking_to_set_up_a_local_instance_of_cloudpebble/) Findings below

I cannot really say for sure what did it but here's everything I did (I think)

cloudpebble/requirements.txt

Changed "amqp==1.4.4" to "amqp==1.4.9"

cloudpebble-qemu-controller/requirements.txt

Changed "greenlet==0.4.5" to "greenlet==0.4.14"

Rebuilt both with "docker build ." in each folder

Copied output container IDs into docker-compose.yml

Commented out build line in web, replaced with "image: IDHERE"

Looking now though, I don't see it there. Maybe I imagined it. Probably an indicator that changing the amqp line wasn't the issue.

Commented out the build line in qemu, replaced it with "image: IDHERE"

Changed all the "./cloudpebble(stuff)" paths to be absolute paths. (ex: ./ changed to /home/hbh7/cloudpebble-composed/etc)

Changed all the IPs to match my VM IP

Entered the web container with docker exec -it CONTAINERID /bin/bash

Somehow passed "Error response from daemon: Cannot link to a non running container: /f9c5e80b594f_cloudpebblecomposed_qemu_1 AS /cloudpebblecomposed_web_1/cloudpebblecomposed_qemu_1"

I think it was simply running docker-compose down and then docker-compose up -d

Did something (output lost for a lot of this section :( sorry) with bower similar to this.

RUN rm -rf bower_components && cd /tmp && python /code/manage.py bower install && mv bower_components /code/

Manually moved files into place

mv /tmp/bower-components /code/

Copied the backbone folder a few places: (oh I guess Reddit doesn't indent farther)

./root/static/common/backbone (I think this one is the right one)

./root/static/root/js/bower_components/backbone

./root/static/root/backbone

Then ran python manage.py collectstatic

Had to restart django then I thought, so I ended up running "pkill -9 python" since that seemed to be running the show

Container then died, had to run docker-compose up -d again, but

Seemed to work after that :D

I probably missed something and did a bunch of things horribly wrong, but it seems pretty functional now.

Few other broken things still though:

No emulator despite the container seeming to work fine now (doesn't immediately exit anymore)

Some fonts are missing

Cloudpebble to phone connection doesn't work

Can't always import projects it seems, got an error that I now lost

Am now locked out or something, its rejecting my login now after I changed/did something or another during the writeup

ltpitt commented 5 years ago

Hi @hbh7 !

In the end were you able to make it work?

I encounter endless issues :(

hbh7 commented 5 years ago

I think it works right now but I gave up and shut the VM down since I don't have time to use it anyways. Seems like there's still no updates so hopefully you're able to eventually make it halfway work :(