I did use them as well and now it is working great. Thanks for this help for starting up, it is invaluable for a noob like me ;-)
Have a great day, ab > Great news. Looks like you did not need my changes. > /Andy > > > On 9 May 2014 09:24, Andy Bunce <bunce.a...@gmail.com> wrote: > >> Hi Aurelien, >> >> Sorry you could not get it to work. If you want to try one more time,I >> have slightly changed the install instructions for >> https://github.com/Quodatum/openshift-basex-quick-start which should >> hopefully reduce the potential for running into some issues. >> Previously the github repo was accessed via the git protocol, now https >> is >> used. This should remove the requirement for a github account and >> github >> ssh key and also work better through proxies. >> >> Regards >> /Andy >> >> >> On 8 May 2014 18:56, Dirk Kirsten <d...@basex.org> wrote: >> >>> Hi Aurelien, >>> >>> seems like your ssh authentication is not working. Based on the error >>> message I would say there are two possible options: Either your client >>> does not support the authentication protocol (highly unlikely if you >>> use >>> putty; I guess they support everything which is at least common) or >>> (much more likely) there is something wrong with your public/private >>> key. >>> Did you also read the comments under the blog article Andy provided? >>> Some people seem to have the same problem as you have. >>> >>> However, I can assure you that this error is not related to BaseX, >>> neither is the problem you are facing with deploying WAR files specific >>> to BaseX. There is really nothing we can do about that, as actually >>> serving the files is part of the containers jobs - And if they are >>> doing >>> it complicated, we can't do much about it. In general I agree that it >>> is >>> quite complicated to deploy a simple WAR file to a container (but this >>> also depends on the container, Tomcat and Jetty are actually quite >>> simple... I remember deploying something on a Websphere Application >>> Server once, which was unbelievably complicated. I still sometimes have >>> nightmares about that.... ;-) >>> >>> Cheers, >>> Dirk >>> >>> >>> On 08/05/14 18:59, a.bouc...@no-log.org wrote: >>> > Well, I followed step by step the provided guide with Putty, but it >>> ended >>> > up with: >>> > >>> > "Server refused our key" and still the message "Disconnected: No >>> supported >>> > authentification methods available " etc. >>> > >>> > Still no luck with Openshift. It looked like a nice hosting solution >>> > though... >>> > >>> > >>> > >>> >> I use windows8. Getting all the ssh keys right can be challenging. >>> Are >>> >> you >>> >> able to create just a simple DIY app? >>> >> and then ssh into it. see >>> >> >>> https://www.openshift.com/blogs/access-your-application-gear-using-ssh-with-putty >>> >> . >>> >> Beyond that which of approaches above are you trying? >>> >> If it is >>> https://github.com/Quodatum/openshift-basex-quick-start.Which >>> >> step fails? >>> >> >>> >> /Andy >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> On 8 May 2014 17:08, <a.bouc...@no-log.org> wrote: >>> >> >>> >>> Andy, Dirk, Christian, many thanks for the indications. >>> >>> >>> >>> However I still have no luck with openshift as whatever I'm doing, >>> the >>> >>> ssh >>> >>> connection does not want to work. >>> >>> >>> >>> I tried everything including switching from windows 8 to a windows >>> 7 >>> >>> machine, using git BASH, etc, and even using SFTP via filezilla as >>> >>> explained here: >>> >>> >>> >>> ( >>> >>> >>> https://www.openshift.com/blogs/using-filezilla-and-sftp-on-windows-with-openshift >>> >>> ) >>> >>> >>> >>> as well as following this advices for windows OS: >>> >>> >>> >>> >>> https://www.openshift.com/blogs/tips-for-creating-openshift-apps-with-windows >>> >>> >>> >>> but each time, it says "Permission Denied" or "No supported >>> >>> authentication >>> >>> methods available (server sent: >>> >>> publickey,gssapi-keyex,gssapi-with-mic)". >>> >>> >>> >>> So it does not want to "git clone" the application to the local >>> machine >>> >>> via ssh... >>> >>> >>> >>> Rather frustrating, but well, I'm patient and open to any >>> suggestion. >>> >>> >>> >>> >>> >>> >>> >>>> Andy, >>> >>>> >>> >>>> thanks for the interesting link! >>> >>>> >>> >>>> Christian >>> >>>> >>> >>>> >>> >>>> >>> >>>> On Thu, May 8, 2014 at 2:10 PM, Andy Bunce <bunce.a...@gmail.com> >>> >>> wrote: >>> >>>>> Hi Aurelien, >>> >>>>> >>> >>>>> If you do try the BaseXHTTP server route on OpenShift, rather >>> than >>> >>> the >>> >>>>> WAR >>> >>>>> packaging, this repo may help >>> >>>>> https://github.com/Quodatum/openshift-basex-quick-start. By >>> default >>> >>> just >>> >>>>> RESTXQ is enabled but it is easy to re-able REST and or Webdav. >>> >>>>> This uses the OpenShift data directory to provide persistence >>> across >>> >>>>> restarts. >>> >>>>> >>> >>>>> /Andy >>> >>>>> >>> >>>>> >>> >>>>> On 8 May 2014 12:25, Dirk Kirsten <d...@basex.org> wrote: >>> >>>>>> >>> >>>>>> Hello Aurelien, >>> >>>>>> >>> >>>>>> how to deploy a WAR file heavily depends on the container you >>> are >>> >>>>>> using, >>> >>>>>> so there is no general guidance from us. It might be more >>> advisable >>> >>> to >>> >>>>>> ask on the actual container mailing list (i.e. tomcat, jetty, >>> >>> whatever) >>> >>>>>> or consult their documentation. >>> >>>>>> >>> >>>>>> Having said that, some time ago I testes BaseX on OpenShift >>> using >>> >>>>>> JBosAS. This documentation actually helped me: >>> >>>>>> >>> >>> >>> https://openshift.github.io/documentation/oo_cartridge_guide.html#jbossas >>> >>>>>> >>> >>>>>> I just pushed the repository to github: >>> >>>>>> https://github.com/dirkk/openshift-basex >>> >>>>>> >>> >>>>>> Now, when modifying the RestXQ files I simply edit the files in >>> >>>>>> src/main/webapp, commit (git commit) them and by using git push >>> push >>> >>>>>> them to openshift. Using maven, OpenShift compiles the WAR file >>> and >>> >>>>>> deploys it automatically at http://jbossas-dirkk.rhcloud.com/ >>> >>>>>> >>> >>>>>> Be ware, that when you use OpenShift, everything is subject to >>> your >>> >>> git >>> >>>>>> repository, i.e. they might spawn a new process by cloning your >>> >>>>>> repository. This means, everything you store on the file system >>> >>> which >>> >>>>>> is >>> >>>>>> not in git is actually not safely stored (you can use S3 or >>> similar >>> >>> to >>> >>>>>> do so). So this also applies to BaseX when it stores its >>> database >>> >>>>>> files. >>> >>>>>> >>> >>>>>> Also, you might want to take a look at the BaseXHTTP version. In >>> >>> this >>> >>>>>> case, BaseX runs within a Jetty servlet container and this is as >>> >>> simple >>> >>>>>> as starting basexhttp. So if you want to be up and running in no >>> >>> time, >>> >>>>>> this might be your safest bet (if you have a web server were you >>> can >>> >>>>>> run >>> >>>>>> java). >>> >>>>>> >>> >>>>>> Cheers, >>> >>>>>> Dirk >>> >>>>>> >>> >>>>>> On 08/05/14 12:41, a.bouc...@no-log.org wrote: >>> >>>>>>> Hello, >>> >>>>>>> >>> >>>>>>> Thanks to the developers for the excellent database software. I >>> >>> love >>> >>>>>>> basex having used it on windows desktop for some little >>> >>>>>> database-driven >>> >>>>>>> projects, but now, I'd like to deploy it in the context of a >>> web >>> >>>>>>> application, if possible. >>> >>>>>>> >>> >>>>>>> So I read everything I could find about the topic but didn't >>> find >>> >>> a >>> >>>>>>> step-by-step guide of how to accomplish it. >>> >>>>>>> >>> >>>>>>> I'm not familiar with java, but I tried to deploy the >>> downloadable >>> >>>>>> BaseX >>> >>>>>>> war application on Appfog services, and also using Openshift >>> with >>> >>>>>> Tomcat >>> >>>>>>> 7. >>> >>>>>>> >>> >>>>>>> On Appfog, the process of installing the war file (which seemed >>> to >>> >>> be >>> >>>>>>> straightforward) didn't complete and generated a java console >>> >>> error. >>> >>>>>>> >>> >>>>>>> (cf >>> >>>>>>> >>> >>>>>>> >>> >>> >>> http://stackoverflow.com/questions/12283448/deploy-simple-java-web-application-on-appfog >>> >>> ) >>> >>>>>>> >>> >>>>>>> And on OpenShift, the process of uploading the war file >>> succeeded, >>> >>>>>> the >>> >>>>>>> console stating that the build was successful, but when going >>> to >>> >>> the >>> >>>>>> URL >>> >>>>>>> of the application, the server generates an internal error HTTP >>> >>>>>> status >>> >>>>>>> 500... >>> >>>>>>> >>> >>>>>>> (cf >>> >>>>>>> >>> >>>>>>> >>> >>> >>> https://www.openshift.com/kb/kb-e1088-how-to-deploy-pre-compiled-java-applications-war-and-ear-files-onto-your-openshift-gear >>> >>> ) >>> >>>>>>> >>> >>>>>>> From there, I don't know what to do next, but would really like >>> to >>> >>>>>> get a >>> >>>>>>> basex web app up and running and interacting with it through >>> the >>> >>> HTTP >>> >>>>>>> REST API. >>> >>>>>>> >>> >>>>>>> Thanks for any help in this regards. >>> >>>>>>> Aurelien >>> >>>>>>> >>> >>>>>>> >>> >>>>>> >>> >>>>>> -- >>> >>>>>> Dirk Kirsten, BaseX GmbH, http://basex.org >>> >>>>>> |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz >>> >>>>>> |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: >>> >>>>>> | Dr. Christian Grün, Dr. Alexander Holupirek, Michael >>> Seiferle >>> >>>>>> `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22 >>> >>>>> >>> >>>>> >>> >>>> >>> >>> >>> >> >>> > >>> >>> -- >>> Dirk Kirsten, BaseX GmbH, http://basex.org >>> |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz >>> |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: >>> | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle >>> `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22 >>> >> >> >
