Skip to content
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

Is this a clumsy setup? #44

Open
tobefound opened this issue Sep 23, 2015 · 7 comments
Open

Is this a clumsy setup? #44

tobefound opened this issue Sep 23, 2015 · 7 comments

Comments

@tobefound
Copy link

Hey,

So, node, angular, couchdb is not really my cup of tea (not linux either...), but here's what I did:

  1. At Cast dev console I created application id and registered my chrome cast devices.
  2. Started a virtual Ubuntu Unicorn.
  3. Copied gscreen content to ~/gscreen, cd gscreen
  4. sudo apt-get install npm
  5. sudo apt-get install nodejs-legacy
  6. sudo apt-get install couchdb -y
  7. sudo npm install (in the gscreen folder)
  8. sudo npm run create-config
  9. sudo nano public/js/gscreen-config.js
  10. Add my chromecastApplicationId
  11. sudo nano /etc/couchdb/default.ini (set to 5985 because couchdb has 5984 in use already)
  12. sudo nano config.json (set to 5984).
  13. sudo couchdb &
  14. ctrl-c
  15. sudo npm start
  16. Ready for testing the gscreen app!

I'm not really happy about step 10-14, not sure how to do this properly (I want couchdb and npm to run as a service/in the background somehow).

It works, but figuring out how the cromecasts, the cast console, the sender and the receiver are working together was a pain...

Anyone knows how to make this setup a more production like setup?

/T

@tobefound tobefound changed the title Is this a clumpsy setup? Is this a clumsy setup? Sep 23, 2015
@shreyaskarnik
Copy link

I have dockerized greenscreen and couchdb in my fork of greenscreen which makes setting up easy. If the project maintainers are open to the idea might as well submit a PR here for review.
For time being check this out: https://github.com/shreyu86/greenscreen

@tobefound
Copy link
Author

Sweet! I think...? :)

How does this affect the setup procedure? Could you add some setup
instructions for those not familiar with this docker thing, thx!
Den 23 sep 2015 18:29 skrev "Shreyas Karnik" [email protected]:

I have dockerized greenscreen and couchdb in my fork of greenscreen which
makes setting up easy. If the project maintainers are open to the idea
might as well submit a PR here for review.
For time being check this out: https://github.com/shreyu86/greenscreen


Reply to this email directly or view it on GitHub
#44 (comment).

@shreyaskarnik
Copy link

@tobefound I will write a tutorial for setting up greenscreen with docker.

@tobefound
Copy link
Author

Can't wait!! Thx!
Den 23 sep 2015 20:20 skrev "Shreyas Karnik" [email protected]:

@tobefound https://github.com/tobefound I will write a tutorial for
setting up greenscreen with docker.


Reply to this email directly or view it on GitHub
#44 (comment).

@tobefound
Copy link
Author

As I said, my setup works but only for a limited time... then something shuts everything down and I have to set the configuration to a different couchdb port.

I want to try out the docker thing or if there's another way to secure a stable running environment.

@loa
Copy link

loa commented Oct 13, 2015

@tobefound We use greenscreen in docker with hosted couchdb at https://cloudant.com/. It's for free as long as your usage of couchdb is less than $50, which we never reached.

https://github.com/tomologic/docker-greenscreen

@anant1811
Copy link

Has anybody tried setting it up on c9.io?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants