Is there any way, we can update the instance class from appengine-web.xml, without redeploying the app.
I would like to change my app instance from F1 to F4_1G.
Unfortunately the only way to change the instance class is currently by means of your configuration file (appengine-web.xml, app.yaml). In order to apply your changes, you have to redeploy the app.
Earlier it was also possible to change instance class in App Engine Console, however, since the introduction of modules and the new Google Cloud Console, no such an option is available.
Related
I have changed the name of my two apps and I would like to change the name of the package in the Google Play Console (I have already changed it in the programming app that I use) since, in production, when putting the App Bundle it tells me that it has to have the same package name.
I have tried to contact Google and they have told me to do it for this site.
The package name is the identifier of the app, so changing package name effectively means creating a new app in the Play Console. That is the only way to "change" the package name. If you have users, that also means you'd need to ask them to install the new app. As to migrating the user data, there are some ways to do it by having the old app and the new app communicate with each other.
I am trying to create a couple of resident instances on a google app engine app hosted on appspot.com. I moved the idle instances slider from Auto down to 2. My understanding is that this will then create two "resident" instances and I should see those marked as Resident instead of Dynamic in the instances screen. But it isn't working, I am still only seeing 1 dynamic instance (this is a test with no traffic).
When I made and saved the idle instances change, I noticed what to me was a new option underneath that section, as follow :
Performance Settings Migration for Modules
Before you can modify performance settings across Modules, your
settings must be migrated. After the migration, performance settings
will be managed at the Module level, and changes must be made through
your app.yaml (Python) or appengine-web.xml (Java). Copy the settings
clause below to the appropriate file to preserve your performance
settings during the next update.
There is a button under this new section called Migrate Settings. When I click this the main screen just blanks, with the admin console menu options still available on the side. All very peculiar!
It also gives some setting for python and java to do the idle instances down to 2 change at the module config level. I stuck this into my appengine-web.xml and re-deployed but I am still only getting one dynamic instance.
Has anyone any experience of this "migrate settings" option?
I was unable to access my Backend Instance at custom domain.
For example, I have an app and I access the Normal Instance sucessfully at:
http://www.[my_app_id].appspot.com or http://[my_app_id].appspot.com
And I have a backend config name=test and I accessed Backend Instance successfully at:
http://test.[my_app_id].appspot.com
In admin interface, the "Instances" link show the instances of Backend and Normal Instance separately. The content show is the same, but is easy to see when a request go to the Backend Instance and when go to Normal Instance.
Then I configured the wildcard "test" in Google Apps to access my Backend Instance at a custom URL:
I continue access the Normal Instance sucessfully at:
http://www.[my_domain].com or http://[my_domain].com
But request at
http://test.[my_domain].com
redicted to the Normal Instance instead of Backend Instance.
The doc's said it should work but I cann't at this moment and I need uses custom domain because my app is multitenancy.
What I do wrong?
Your backed is really supposed to be accessed by the front end, as I understand it.
So when your application front end makes a request to it's back end (e.g. via a URL), it'll work as it's all done internally.
Have you set your back end to be publicly accessible?
https://developers.google.com/appengine/docs/python/backends/overview#Public_and_Private_Backends
Backends are private by default, since they typically function as a component inside an application, rather than acting as its public face. Private backends can be accessed by application administrators, instances of the application, and by App Engine APIs and services (such as Task Queue tasks and Cron jobs) without any special configuration. Backends are not primarily intended for user-facing traffic, but you can make a backend public for testing or for interacting with an external system.
I don't know why the redirection is not working, but perhaps you should modify your question to show what problem it is you are trying to solve here and get an answer to that instead?
There are many cases in which we run into a need to update only static content of a production GAE app.
Examples:
CSS changes, and other related resources, such as images
New HTML pages, API of the app stays the same (RESTful web services)
Client side flow changes (only JS)
Each of the above changes requires a full deployment.
I read the documentation (Java) and searched this forum (and others), and I'm pretty sure there's no such method exists.
Partial updates of the app in GAE is possible, like updating indexes, update cron jobs, backend management (deploy, start, stop, etc.), but nothing about update static content.
Does anyone know a way for just deploying / updating the static part of a GAE app?
Is this something that folks using GAE would need / use?
Cant be done. File a feature requets!
I am working on Restful Web application. I am maintaining different project for web client code and Google app engine server code.
When ever i made changes in the client code, i rebuilt the client code and places inside the war folder of server project through build scripts.
Here i dont want to place all files directly to war folder and i wanted to put them under folder called 'Publish' for better maintainence. How can do it?
Is there any better way to maintaining client code and Google app engine server code?
The structure also works well for Mobile application in future.
I am still new to this too, but there is versioning. If you change the version number in your project manifest file, it does not become the default (i.e., visible to your original public URL). It is public and accessible for you to test. When you are ready to "publish" just switch the new version to be the default. Use the Manage section of the Dashboard and set the Version to be the default when you are ready.
To test any of the earlier versions, you access through the Manage and click on the specific version. I don't know if the persistent storage is versioned with this same mechanism -- I can image problems if you have a huge DB.