Sure, no problem. - Create an account in Google Cloud https://cloud.google.com/ . using your Google user. It has a free trial, unfortunately it asks for a credit card, but they never charge you, only if you upgrade to a charged plan, which is charged by the minute and only for those active minutes. Free trial gives you a $300 credit to use in anything you want. - Create a project. Make sure you name it "Apache ISIS rocks and it is an absolute cool app amplifier!"
- Go to the Google Cloud console. (starting point actually). - In the upper left side hamburger menu, open it and find "Development". - Once you are in the development section, it prompts you for some options to create your repository. I used the one that connects to github and clones the repo. Once it clones it, you can edit the code in a Google Cloud environment very similar to github (did they licensed it from github? Who knows!). - On the upper right section of the blue bar, find an icon like a linux shell >_ prompt. It opens a terminal window. Your source code is under src/ directory. - Move to the app, and do the regular mvn clean install. Before this, you might want to set an HSQLDB on file configuration to avoid creating and configuring MySQL or PostgreSQL database instance within Google Cloud at this time. Google Cloud uses java 7 by default, but it has Java 8 installed to. If you wish to use Java 8, switch to it as default and restart the terminal window. - Move to the webapp directory, and do the regular mvn jetty:run. - How do I connect to the app server from the browser? What is the URL? In the upper left corner of the google app terminal, open the web preview icon, and click on the option "preview on port 8080" - Your Wicket viewer app is running in your local browser connected to Google Cloud. - Try using a map, or a button within a collection header bar, issues those errors. Otherwise everything else seems to be working fine. Cesar. -----Original Message----- From: Dan Haywood [mailto:[email protected]] Sent: Friday, April 1, 2016 10:32 AM To: users Subject: Re: ISIS app on Google Cloud App Engine On 31 March 2016 at 21:19, Cesar Lugo <[email protected]> wrote: > Hello, I have installed our application using Apache Isis on a Google > Cloud App Engine instance. It is working for the most part J, only > with some issues. On the browser's console, I get which seems to be > due to the fact that google maps is called via http instead of https > protocol, : > > I imagine it should be possible to configure this component to use either http or https; it certainly ought to support that. Only trouble is I can imagine it'll take a while to reproduce. Do you have any setup notes that you could share that would help a GAE noob like me get to the same point that you are at? > > > JQMIGRATE: Logging is active > > simple.Business:0:1 Mixed Content: The page at ' > https://8080-dot-2049980-dot-devshell.appspot.com/wicket/entity/simple > .Busi ness:0' was loaded over HTTPS, but requested an insecure script > 'http://maps.google.com/maps/api/js?v=3&sensor=false'. This request > has been blocked; the content must be served over HTTPS. > > jquery-migrate-1.2.1-ver-1459440935000.js:41 JQMIGRATE: > jQuery.fn.attr('checked') may use property instead of attribute > > jquery-migrate-1.2.1-ver-1459440935000.js:43 > console.trace()migrateWarn @ > jquery-migrate-1.2.1-ver-1459440935000.js:43 > > wicket-gmap-ver-1459440935000.js:76 Uncaught ReferenceError: google is > not defined > > > > The second issue is that whenever I try to click on an action button > that is displayed within a collection's header, it does not work. > Other action buttons work fine, but most or all the ones that are > within the collection header do not work, just don't do anything, and > do not send any error to the browser's console, and there is no > activity on the network monitor of the browser when I click the action > button. > > > > Any Ideas? > > This one sounds rather odd, but I wonder if this is only for collections that also have a gmap3 representation? If so, it might be that the aforementioned broken gmap rendering is also messing up the requests in the header. My recollection is that the buttons in the header will be in some form, and it's possible that the form extends to and includes the gmap component (even if hidden). So, the question is: if you remove gmap3 completely from the app, are the buttons still broken? Thx Dan > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
