I have a grandfathered Google Apps for Work account since I had my appengine app running since before they started the whole Apps for Work thing and don't have to pay anything.
I haven't touched the actual app since long before the Apps for Work thing came around, and though I got the emails about it and opened the console once or twice, I haven't opened the app engine console forever.
I also have a google cloud platform account that I use for the VMs(not GAE).
The problem came when I went to actually update my app. I found that while the app is most definitely still running and accessible, and while my Apps for Work console still lists it, when I try to manage it, it redirects me to my cloud platform account, which has no GAE apps. I haven't even touched GAE on my cloud platform account, and there were no apps listed, just the docs.
So how do I access my app and edit it?
I have built an app using Google Apps Script (GAS). It displays a form. When the user submits the form, the submitted data is written to a Google docs spreadsheet. I have deployed the app using the built in Deploy as web app option in the GAS script builder page
What I can't seem to find out is whether it is free to build and deploy web apps using Google Apps Script, or is it the case that one needs to pay?
I did come across a paid service called Google App Engine, but I am not sure if this is relevant to Google Apps Script.
Thanks.
Google Apps Script is a javascript cloud scripting language and it is free to use as long as you do not need higher quotas than defined here: https://developers.google.com/apps-script/guides/services/quotas
If you need higher quotas than listed there - I would suggest you take into consideration to build your own Google Appengine Application for your service.
However if you did not hear about that since now you should first do some examples listed here https://cloud.google.com/appengine/docs - and get familiar with the Platform as a Service Google offers. It is also free of any charge as long as your application applies to the free quotas.
Important fact: Every Google Apps Script has it's own Developers Console Project assigned to it - however it is not neccessary to configure anything on the Console for App Script to work properly. You can review your assigned Appengine Project by
using the Menu: Resources - Developers Console Project... and click on the link that looks similar to this -
https://console.developers.google.com/project/project-id-YOUR_PROJECT_ID
I am getting very confused with the whole cloud console api console thing.
I just created a new Cloud Console project in order to setup some GCE instances. It seems to have auto-created an App Engine app. That is fine, but when I go to enable billing, it tells me that it cannot enable billing for app engine apps and that I need to do that in App Engine Console.
Earlier this week, I tried to setup a project to include both an existing App Engine app and Compute Engine. I was asked to got through the request access process like before GCE was available.
I created a project in the Cloud Console by starting in the App Engine console and choosing Cloud Integration. I said there was an error creating the project, but it seems like it created it. However, when I go to that project in Cloud Console, there is no option to even add Compute Engine.
Two questions:
(1) Is there something outlining the differences between Cloud Console and API Console and when it is most appropriate to use one over the other?
(2) How do I get a project (in either one I suppose) that includes an existing App Engine app and Compute Engine resources that I want to create in this project?
Thanks for your help.
-- Jay
Cloud Console is essentially a planned replacement for the API console,
however it may not have all functionality yet
Try going to appengine admin console application settings, and at the bottom of
the page cloud integration. Click on create project. Once it succeeds go to the cloud
console and enable billing for Compute Engine
I'm trying to read a sqlite db from the server side code in my gwt project. It throws AccessControlException. I looked a lot on the web and all solutions seems to be disabling Google App Engine, but when I do this, I can't run my project. I'm new to GWT and I have no idea where it runs when Google App Engine is shut down. I look for possibly this two solutions: Any setting that Google App Engine is set to be able to read any file, or other engine that I run my application on. Thanks
The problem is that Google App Engine (GAE) does not support sqlite (I assume you are reading it using JDBC).
If your intention is to make a GWT project that will not be deployed on GAE, you should create the project disabling this feature from the very beginning, because afterwards its a nightmare as you are experiencing right now.
If your intention is to deploy in GAE, you must use the google's persistence mechanisms (JDO) to store your data. SqlLite is off the table here.
Google created the V8 JavaScript engine: V8 compiles JavaScript source code directly into machine code when it is first executed.
Node.js is built on V8 - why is Google not offering any Node.js servers like Microsoft Azure?
Google App Engine would be a natural place to put Node.js.
Do you know why Google is not doing just that?
Node.js is maintained by Joyent, who is in a way a competitor of Google.
Node.js has no link what so ever with Google but is in fact built on top of an open source project started by Google.
Google might jumped into this business just like Azure did, but there are already so many PaaS doing it, it might not be worth it. I have never used GAE, but my understanding is that it is quite different that other PaaS and you have to use GAE libraries to make your code run.
Which, this is my personal feeling, is not really what the Node.js community is looking for.
Node.js is used to quickly make a fast lightweight app, a big share for APIs for Phone apps for example.
Nevertheless if you are looking for a PaaS for Node.js, the are quite a few out there:
Joyent (nodejitsu)
dotCloud which has WebSockets support.
Windows Azure
Nodester (bought by App Fog recently)
Any Cloud Foundry host should support Node.js too.
and many more...
Those are just some names off the top of my head. There quite a few but those are the major ones.
Oh there is Heroku too, but they don't have support for WebSocket which is a bummer for any Socket.IO based app.
As of June 2014, Google had a limited preview for custom languages on Google App Engine (which is different from Google Compute Engine).
Watch Building Node.js applications with App Engine and Custom Runtimes and check out https://cloud.google.com/appengine/docs/managed-vms/:
App Engine now offers a second hosting option: Managed VMs. The Managed VM hosting environment lets you run App Engine applications on configurable Compute Engine Virtual Machines (VMs).
You can also use Managed VMs to deploy user-configurable custom runtimes, such as for Node.js and other runtimes.
The procedure to get into the beta is:
Sign up and create a Managed VM project
Managed VMs are in Limited Preview, you must sign up for access to this feature, create a billing-enabled project, and tell us about your project so we can whitelist it to run in a Managed VM. Follow these steps:
Sign up for access to Managed VMs.
Join the app-engine-managed-vms Google Group to participate in discussions about Managed VMs.
Projects (or apps - they are the same thing) must be in a U.S. data center. If you're planning to use an existing project, skip to the next step. Otherwise, create a new app in a U.S. data center. Navigate to https://preview.appengine.google.com and create a new app.
Enable billing for the project. Visit the page https://cloud.google.com/console/project/apps~, where is the ID of your project. Click on Settings in the left menu and then enable billing. If your app is billed under a Premier account, email us at app-engine-managed-vm-tt-id#google.com to have your new Cloud project billed under the same account.
Send an email to app-engine-managed-vm-tt-id#google.com with the application ID in the subject line.
When we receive your email, we’ll configure some resources behind the scenes and notify you via email when your project is ready to go. The email includes final instructions for setup. If you encounter an error while following these instructions, contact us at app-engine-managed-vm-tt-id#google.com.
You can easily install node on Google Compute Engine (which basically is a virtual computer). Here is a link:
https://developers.google.com/datastore/docs/getstarted/start_nodejs/
Regards
Lars
after years of experiences in google appengine, i switch to other cloud services now.
i think google appengine is actually an old fashion service in cloud computing industry. which is slow to new technology, difficult to deploy, time wasting to learn the apis and lacking of a lot of features you need in languages you use.
regardless of google's large community, i would not suggest anyone to use google appengine.
[newer paas]
i strongly recommend you to use openshift, appfog, heroku .etc's new paas cloud computing technologies, which are far more extensible, less change needing, more migrable from one platform to another, more freely coding in the beauty of the natural lanuage and its standard libraries without ugly platform specific apis.
[iaas]
if you want more control over the running os environment, you may give linode, digital ocean, amazon, google cloud engine, microsoft azure etc. iaas providers a try.
Because App Engine is a platform-as-a-service, and in order to add a new language/stack to GAE, Google need to create mid-level libraries that interface with the plethora of App Engine's services.
Moreover, all App Engine apps is sandboxed and has several functionalities restricted from inside their sandbox environment. This means that beside the need to create service libraries, Google also need to create a secured sandbox environment for any language/stack that they try to introduce into GAE.
I personally think the second reason is why Google does not introduce support for new language/stack as aggressive as Azure did. App Engine is, in a way, more 'managed' than Azure, and has a larger initial development cost for new language/stack.
It has been released as of March 2016.
https://cloudplatform.googleblog.com/2016/03/Node.js-on-Google-App-Engine-goes-beta.html
Node.js has recently enabled support for Google Cloud users. The main document pages are:
Node.js on Google Cloud Platform
Google Cloud Datastore — Google Developers
It seems to require at the moment a Compute Engine instance.
Background: App Engine Standard vs App Engine Flexible
There seems to be some confusion on this topic because there are two versions of App Engine: Standard and Flexible. NodeJS is supported on App Engine Flexible but NOT on App Engine Standard. (See here for a more complete explanation of the differences).
App Engine Standard scales in seconds (as opposed to minutes for the Flexible environment), and has a free tier, so you can develop and demo without spending a dime. These benefits come at the cost of flexibility. App Engine Standard only supports certain languages and libraries, doesn't allow writing to disk nor SSH. In other words, the environment is standardized.
Answer: NodeJS Support on App Engine Standard
If you are interested in NodeJS support on App Engine Standard, please star this issue: https://issuetracker.google.com/issues/67711509.
Google addresses features that get attention from the community (see here). The best way to give your attention to this feature, is to star it on the Google Issue tracker linked to above.
Google announced on March, 21st 2016 that Node.js on Google App Engine was going beta: https://cloudplatform.googleblog.com/2016/03/Node.js-on-Google-App-Engine-goes-beta.html?m=1
This was expected as Google also joined the Node.js Foundation and Google develops the V8 JavaScript engine which powers Chrome and Node.js: https://nodejs.org/en/blog/announcements/welcome-google/
Google announced a partnership with NodeSource at the same time.
Google has just announced support for Node.js on App Engine.
See: https://cloud.google.com/nodejs/
Here's an example of how to deploy Node.js app on App Engine.
Google is a software-conservative company. Programming a backend in JavaScript would be absolutely unimaginable for Google's managers. Creating infrastructure Google itself won't be using is not a good investment. Reference: Notes from the Mystery Machine Bus
(Jun 2021) This question is almost a decade old, and many things have changed since the OP. TL;DR: JavaScript and/or Node.js are supported in 6 different serverless compute platforms from Google: 4 on GCP and one each from Google Workspace and Firebase plus release dates:
Google App Engine - Standard (Jun 2018) - announcement, docs (Node.js 10, 12, 14; 8 is deprecated)
Google App Engine - Flexible (Mar 2016) - announcement (general release), docs (Most Node.js versions)
Google Cloud Functions (Mar 2017) - announcement (general release), docs (Node.js 10, 12, 14; 8 is deprecated)
Cloud Functions for Firebase (Mar 2017) - announcement, docs (same versions as Google Cloud Functions)
Google Cloud Run (Apr 2019) - announcement (general release), docs (Any Node.js version you can put in a container)
Google Apps Script (Aug 2009) - announcement, docs (JS-only, not Node; Rhino ES3/ES5 + extensions originally; now v8 & ES6+ [Mar 2020])
Also see Google Cloud's overall support of/for Node.js.