All geek questions in one place

How to speed up the deployment of Java Google App Engine?

I am developing a test application with GWT + Java-AppEngine, and deployments are so heavy and slow.

I read about minimizing permutations or compiling GWT in parallel, but my internet connection is not so good, and I think I'm uploading heavy files to the App Engine Server.

How can I optimize this? Can I check where this bottleneck is?

The reason I need multiple deployments is because I use the Google API through OAuth and I cannot set localhost as a callback (am I doing?).

+6
source share
1 answer

I'm not quite sure about your scenario, so I’ll try to guess your intentions.

For development purposes, you really have to work on a local server, it comes with all the APIs and stubs for things like logging in and what not. It is instant. Once you are satisfied with your local application and it is time to download it, then if the AppEngine administrator decides to take the time because of the AppSize / Slow Connection / Service outage / random act of diety, little can be done.

Given that every hour is not deployed, I think that your time would be better spent on the application, and not on setting the download time.

I assume you are already following http://code.google.com/appengine/docs/java/gettingstarted/uploading.html

I personally worked on appengine, but the python version, and this may take a few minutes, but as soon as the download is complete, you will go well.

Perhaps you could get the local hostname machine dyndns and make it accessible from the Internet? -

I think Bastian had in mind the following (assuming that the Dev server can indeed serve domains - I'm not sure about that)

  • If your domain host (example.com) supports an “A” entry that points to your IP address of your development computer [therefore, when you do example.com, your development computer responds as a server]
  • This means that if you configure DNS records on ghs.google.com or something else, you will have to change them (DNS records take some time to propagate depending on the host)
  • After you are happy and you want to test on google, you still need to “download” before you can try it on appspot.com and, of course, change the DNS records again, so example.com works with google servers .

Too much work in my opinion. It is better to use the dev server on the local machine.

Take a break at boot time. Ask KitKat to kill time :)

+3
source

Source: https://habr.com/ru/post/888836/

More articles:


All Articles