-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GAE Generator Enhancements and Corner Cases #10331
Comments
Thinking about 2) further an alternative approach is we could spit back the full error message along with a message saying that
Let me know what you think is better. I vote for 2) so that some users it will auto install it and for other (hopefully few) there's some pointers available. |
/cc @ludoch nice, for |
Wonderful. Thanks for the confirmation @saturnism . I've created a PR which fixes both issues. Please let me know if you see any issues. 😄 |
@saturnism , @PierreBesson : I was wondering adding one more thing to this; we probably should set the |
+1 |
@saturnism : Done 👍 |
While we are at it, could I trouble you to change the run commands that gets displayed at the end?
We may need to do similar thing for Gradle build too. |
actually, a follow up would be fine. i feel this PR is ready to be merged as-is. |
@saturnism : It's a simple fix; I just did it in this pull request itself. For gradle I don't think we need to change that since even in the new version as per documentation |
Hi, Basically, if we could unjar the fatjar in the target/appengine-staging directory (and remove the orginal fatjar), the entrypoint would have to be like: entrypoint: java -agentpath:/opt/cdbg/cdbg_java_agent.so=--log_dir=/var/log -noverify -XX:+AlwaysPreTouch -XX:TieredStopAtLevel=1 -Djava.security.egd=file:/dev/./urandom -cp BOOT-INF/resources/:BOOT-INF/classes/:BOOT-INF/lib/* com.mycompany.myapp.YOUAPPCLASSNAME If this can be done, one extra goodies would be to configure App Engine to use a CDN to access the static resources instead of the JVM itself (from a fatjar which is also not optimal at all)... To configure static resources in the app.yaml with an exploded jHipster fatjar, you would have to add this section in app.yaml: handlers:
With these 2 changes, we are back to the orginal Java GAE design from 2009 with appengine-werb.xml configuration: exploded war for optimal deployement and automatic static file servinf from a CDN. You would see the difference when loading an app where all the static html and images and js scripts are served immediately... Finally, Instance classes of F1 do not work yet with jHipster, but this will be fixed for GA very soon. Thanks again. |
Also, I think for Java11 GAE runtime, |
@ludoch : Thanks much for all the information and ideas. 👍
Just to be clear; I suppose what you mean by exploded fatjar is a thin jar correct?
I have to check this one; if so we can remove the entire check for app-engine-java. @saturnism @ludoch : I'll create two seperate PRs for both of these. 😄 |
@ludoch : Although in the documentation for Java 11 it says to use |
Can we table the significant thin jar changes for the next iteration? lets get the basics committed first :) |
Maybe a bug in the current Maven plugin?
Thanks for the note, I'll follow up...
…On Thu, Sep 5, 2019, 4:16 PM Sudharaka Palamakumbura < ***@***.***> wrote:
Also, I think for Java11 GAE runtime, gcloud components install
app-engine-java is not needed at all. It it needed only for Java8 runtime.
@ludoch <https://github.com/ludoch> : Although in the documentation for
Java 11 it says to use gcloud components install app-engine-java;
https://cloud.google.com/appengine/docs/standard/java11/using-maven
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10331?email_source=notifications&email_token=AAATRTOEZW4VCQB44C2MRK3QIGHMRA5CNFSM4ISYK43KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6BHCIA#issuecomment-528642336>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAATRTNACDQDF5BWNP454Z3QIGHMRANCNFSM4ISYK43A>
.
|
@ludoch : Not sure; Thanks much; of course let us know. 😄 I'll leave that for now until officially it's updated since IMHO why bother removing it and getting into trouble when the official documents says otherwise. 😄
Surely, I was thinking about a separate PR for this one after the current PR is merged? Is that what you mean next iteration? |
yup! |
Overview of the feature request
This is a continuation of #10196 which hopes to discuss and do some refactoring to the GAE App generator. It's my belief that this generator has some remaining issues outlined below.
gcloud components install app-engine-java --quiet
. This has the potential to fail since the Cloud SDK installation can be done in several ways and it is operating system dependant. For example a typical case maybe in an Ubuntu or Debian where the user installs it usingapt-get
. Then he could encounter the following error;https://askubuntu.com/questions/1146879/how-do-i-fix-the-google-cloud-sdk-component-manager-is-disabled-for-this-instal
I think the best way to handle this is to check whether
app-engine-java
component is installed and if not prompt the user to do so; same thing we do for Google Cloud SDK.@saturnism @PierreBesson : If this is in agreement let me know. I'll create the PR. Sorry I mistakenly created this as a feature request. If you could please change it to a bug report instead.
Motivation for or Use Case
More user friendly GAE generator with less confusion.
Related issues or PR
#10196 and #10285
The text was updated successfully, but these errors were encountered: