gcloud

I have built a Node.js app and what I do to deploy is cd into my project's directory and run gcloud preview app deploy . This works, but in the files I also have a JSON file which acts like the database for my application, which I do not want updated on the site when I deploy. I cannot seem to find any way of doing this. If it's not possible, being able to see the JSON file remotely and copy its data to the local one and then deploy everything would do me too, but I cannot seem to be able to do that either. I believe you will want to use the skip_files directive in your app.yaml to exclude

I need to train a neural net fed by some raw images that I store on the GCloud Storage. To do that I’m using the flow_from_directory method of my Keras image generator to find all the images and their related labels on the storage. training_data_directory = args.train_dir testing_data_directory = args.eval_dir training_gen = datagenerator.flow_from_directory( training_data_directory, target_size = (img_width, img_height), batch_size = 32) validation_gen = basic_datagen.flow_from_directory( testing_data_directory, target_size = (img_width, img_height), batch_size = 32) My GCloud Storage

I currently use gcloud preview app modules delete <module_name> --version <version_to_delete> with a service account to clean up old module versions for managed vms. This has been working great up until last week. I am now getting the error below. ERROR: (gcloud.preview.app.modules.delete) Error Response: [403] Project has not enabled the API. Please use Google Developers Console to activate the API for your project. Details: [[{"@type": "type.googleapis.com/google.rpc.Help", "links": [{"description": "Google developer console API activation", "url": "https://console.developers.google.com

As anyone who has ever had the misfortune of having to interact with the panoply of Google CLI binaries programmatically will have realised, authenticating with the likes of gcloud , gsutil , bq , etc. is far from intuitive or trivial, especially when you need to work across different projects. I am running various cron jobs that interact with Google Cloud Storage and BigQuery for different projects. Since the cron jobs may overlap, renaming config files is clearly not an option, and nor would any sane person take that approach. There must surely be some sort of method of passing a path to a

I'm using the Managed VM functionality to run a WebSocket server that I'd like to expose to the Internet on any port (preferably port 80) through a URL like: mvm.mydomain.com I'm not having much success yet. Here are the relevant parts of various files I'm using to accomplish this: Dockerfile: EXPOSE 8080 8081 At the end of the Dockerfile, a Python app is started: it responds to health checks on port 8080 (I can verify this works) and responds to WebSocket requests on port 8081. app.yaml: module: mvm version: 1 runtime: custom vm: true api_version: 1 network: forwarded_ports: ["8081"] I deploy