Learning how to use the Google Cloud Platform

As an exercise in learning the #GCP i am going to create a simple 1 or 2 page website. 

I think i will use the Cloud Shell … no sense of struggeling with  my local #sdk.


Cool. Of course there are no good page editors in the cloud shell, just vi and nano.

But what you can easily do is git push local web page files that you make in your favorite editor and then pull them to your cloud shell for deployment.  Using git is independent from gcloud activities and not part of the sdk … and knowing how to use git is crucial in todays common programming workflow.

#sethhmmm re git vs ftp in the cloud

i still don’t see why a thinking domains’s thought cannot be mirror of a web page … when i is ready to be deployed, just click the publish to web button and there it goes … both the background and the foreground … ending up there, probably in the cloud,  as just a static HTML page.

There is no, or very very little, ftp in the cloud. I havn’t used, or seen used, FTP in probably 10 years or more. It doesn’t hold up under modern demands for file management and in fact, ftp is not even installed in the gcp cloud shell … you would have to install your own server … and I seem to remember seeing a bunch of ports that were disabled for the shell, perhaps the ftp one.

p.s. If you want your own nice subdomain, such as seth.thinking.domains or something like that, you will have to deploy a new dispatch.yaml file for our entire app. To do that, you will have to get the one out of our prime origin git repo, modify, and deploy it … or else you will crash the mappings of all our existing domains.

But you can always use the temp-domain-name assigned to any app instance (website). That works no matter what.

your way ahead of me