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

Deploy Yaydoc master to FOSSASIA's Google Cloud #344

Open
imujjwal96 opened this Issue Aug 1, 2017 · 3 comments

Comments

2 participants
@imujjwal96
Contributor

imujjwal96 commented Aug 1, 2017

This is a

  • Bug report
  • Feature request

Description

The master branch of Yaydoc is currently deployed at Heroku (https://yaydoc.herokuapp.com). However, we cannot rely much on a free tier Heroku app to host Yaydoc due to various limitations.
Hence, there is a need to deploy Yaydoc to FOSSASIA's Google Cloud.

@niranjan94

This comment has been minimized.

Show comment
Hide comment
@niranjan94

niranjan94 Aug 1, 2017

Member

@fossasia/yaydoc-dev-team

This will be a deployment on the Google Container Engine (with Kubernetes) to be specific.

Example configuration for a node.js project available here.

The basic requirements for it would be:

We'll do the above as the first step.

The next phase would involve,

Lemme know if you face any issue with regards to any of the above.

Member

niranjan94 commented Aug 1, 2017

@fossasia/yaydoc-dev-team

This will be a deployment on the Google Container Engine (with Kubernetes) to be specific.

Example configuration for a node.js project available here.

The basic requirements for it would be:

We'll do the above as the first step.

The next phase would involve,

Lemme know if you face any issue with regards to any of the above.

@niranjan94

This comment has been minimized.

Show comment
Hide comment
@niranjan94

niranjan94 Aug 1, 2017

Member

And @imujjwal96 don't you think this is a duplicate of #300 ?

Member

niranjan94 commented Aug 1, 2017

And @imujjwal96 don't you think this is a duplicate of #300 ?

@niranjan94 niranjan94 marked this as a duplicate of #300 Aug 1, 2017

@imujjwal96

This comment has been minimized.

Show comment
Hide comment
@imujjwal96

imujjwal96 Aug 1, 2017

Contributor

I thought that issue was for a generic one click deployment like that with Heroku. I guess i'll have to research more on it 😄

Contributor

imujjwal96 commented Aug 1, 2017

I thought that issue was for a generic one click deployment like that with Heroku. I guess i'll have to research more on it 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment