-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Blog posts about parse-server running on google container engine #3829
Comments
Sounds like a great idea to put in the wiki! |
Hi @natanrolnik. Anyway, I am about to write part 3 and 4 and I will let you know as soon as it will be ready ... Ran. |
Oops, sorry, haha! Fixed. Sure, ping me here when you do so and I'll update it. |
Thanks a lot. Good to see that you are from Israel as well ! ;) |
🇮🇱 |
Is part 3 of from Zero to hero published yet? |
Thanks. Awesome tutorial!
I got stuck temporarily because I put a different name for the disk, as is in step 3
Filling the following details in the Create a disk form under name the article says to use
“my-parse-db-disk” instead of “my-parse-app-db-disk.”
I am glad that happen as that forced me to check every step carefully to grasp better what you were showing.
Thank you so much.
I am just waiting now with the message under mongo-deployment “pods are pending”
Again, thank you!
…Sent from my iPhone
On May 6, 2018, at 2:54 AM, Ran Hassid ***@***.***> wrote:
Hi @scdi yes it was... here you go:
https://medium.com/google-cloud/from-zero-to-hero-run-parse-server-on-google-cloud-platform-part-3-automatically-obtain-lets-d7db8994000a
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi Ran:
I am getting this error message (see attached .png file) would you know how
to fix that when I access. This happens when I access
http://localhost:8001/ui .
On Sun, May 6, 2018 at 10:51 AM, Jude Jonassaint <jude@sicklesoft.com>
wrote:
… Thanks. Awesome tutorial!
I got stuck temporarily because I put a different name for the disk, as is
in step 3
Filling the following details in the Create a disk form under name the
article says to use
“my-parse-db-disk” instead of “my-parse-app-db-disk.”
I am glad that happen as that forced me to check every step carefully to
grasp better what you were showing.
Thank you so much.
I am just waiting now with the message under mongo-deployment “pods are
pending”
Again, thank you!
Sent from my iPhone
On May 6, 2018, at 2:54 AM, Ran Hassid ***@***.***> wrote:
Hi @scdi <https://github.com/scdi> yes it was... here you go:
https://medium.com/google-cloud/from-zero-to-hero-run-
parse-server-on-google-cloud-platform-part-3-automatically-
obtain-lets-d7db8994000a
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3829 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AM6vr9LIbi0gx46H_9-kUSoIPk_pEWPNks5tvp4rgaJpZM4Nfqtx>
.
|
Hi, I started to write a series of blogs in medium.com on how to run deploy parse-server to google container engine. In this series i cover the following topics:
The name of the series is From Zero to Hero because i assume that you start from scratch without having any idea about parse-server or google container engine.
Currently only part 1 and 2 are ready and part 3 will be ready soon. (i assume on next week).
@flovilmart - What do you think about adding it to the docs/wiki?
So if you are running on GCP or thinking about moving to GCP and specifically running on container engine go ahead and read the following blogs:
From Zero to Hero — run parse-server on Google Cloud Platform Part 0 — Introduction
From Zero to Hero — run parse-server on Google Cloud Platform Part 1— Run parse-server and MongoDB locally with docker-compose
From Zero to Hero — Run parse-server on google cloud platform part 2 — Deploy and run parse-server on Google Container Engine
Thanks,
Ran.
The text was updated successfully, but these errors were encountered: