-
Notifications
You must be signed in to change notification settings - Fork 149
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
Comments
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. |
Sweet! I think...? :) How does this affect the setup procedure? Could you add some setup
|
@tobefound I will write a tutorial for setting up greenscreen with docker. |
Can't wait!! Thx!
|
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. |
@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. |
Has anybody tried setting it up on c9.io? |
Hey,
So, node, angular, couchdb is not really my cup of tea (not linux either...), but here's what I did:
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
The text was updated successfully, but these errors were encountered: