I'm going thru the Jhipster and can't select some option. How could I have it selectable? Why I can't select the 'API first development using swagger-codegen' option?
These are the console steps after running jhipster command:
Check your Internet connection.
If you are using an HTTP proxy, try this command: git config --global url."https://".insteadOf git://
? Which type of application would you like to create? Microservice application
? What is the base name of your application? service1
? As you are running in a microservice architecture, on which port would like your server to run? It should be unique to avoid port conflicts. 8086
? What is your default Java package name? com.comp.abc.service1
? Which service discovery server do you want to use? JHipster Registry (uses Eureka, provides Spring Cloud Config support and monitoring dashboards)
? Which type of authentication would you like to use? JWT authentication (stateless, with a token)
? Which type of database would you like to use? No database
? Would you like to use Maven or Gradle for building the backend? Maven
? Which other technologies would you like to use?
❯◯ API first development using swagger-codegen
◯ Asynchronous messages using Apache Kafka
To select answers on multiple choices questions you need to press the spacebar.
Related
Is there any way to enable a grafana plugin within its configuration files?
I am using grafana v5 or v4
It looks like you have to login and then click then enable button
I found a workaround for my problem running docker with a volume that would map the default sqlite db for grafana in /var/lib/grafana/grafana.db
this would keep any configuration, dashboard, datasource firstly set up in the web interface
You can use the Zabbix Plugin for Grafana.
You need to install and enable the plugin, then configure the Zabbix datasource:
URL: http://yourserver/zabbix/api_jsonrpc.php
access: proxy or direct, depends on the reachability of Zabbix and grafana servers
username: use a dedicated one, with the required read permissions
And you're ready to create dashboards by referencing groups, applications, hosts and items.
Here you can find the getting starded guide, it's quite complete.
The regexp & templating features are really powerful, I advise to read it carefully.
I have used Bitnami VM to deploy Parse Server on Azure but I cannot seem to be able to access Parse Server Dashboard. What URL is it available on? Do I need to open any ports?
Just an update on this. A new version of Parse Server provided by Bitnami is now available in the Azure Marketplace. The new version does include the Dashboard.
Have you been following Bitnami instructions?
It states you can access the dashboard using this URL: http://[server-IP-address]/parse
This means only TCP/80 port needs to be open (on your Network Security Group if you use one or in your VM ACL if you don't).
You have now other (probably easier) options to deploy Parse Server on Azure:
using a dedicated ARM template leveraging Azure services (App Service, DocumentDB, Notification hub, ...).
using Azure App Service with the original Facebook/Parse version with MongoDB.
I've got it. The bitnami guys were kind enough to reply to me for this topic:
You can launch the latest Parse version that ships the Dashboard from https://vmdepot.msopentech.com/Vhd/Show?vhdId=64574&version=66817 It could take some time to be available in the Azure Marketplace
So bottom line, use the image from VM depot and not the one on Azure Marketplace as it is an old one and doesn't include the Dashboard.
I am trying to use the Grails plugin 'directory services' to access LDAP data. I am unable to configure it in GGTS. Can anyone help me with the code or directions to be used in coding a program for LDAP access in GGTS.
Did you check the documentation http://lr.github.io/directory-service/guide/configuration.html to see how to configure the plugin ?
This is a client and this means you have to install / configure also a ldap server. Have a look at the apache directory project https://directory.apache.org to get a ldap client / server . Afterwards you can connect from Grails as client to the Ldap-Server.
I'm still very new to Camunda. Maybe I've missed something obvious. But is there a simple way to configure camunda-webapp-jboss-7.2.0 (admin, cockpit, tasklist) to run on a different host than camunda-engine?
E.g., I have a host "A" with camunda-bpm-wildfly-7.2.0 and want to deploy camunda-webapp-jboss-7.2.0.war on host "B" (vanilla wildfly). Is there a way in webapp to configure the engines hostname or IP or baseURL? I assume, webapp uses REST API?
Thanks.
Such a deployment scenario is not possible at the moment. The webapp always needs at least an embedded process engine that is configured against the correct database. The best you can do is use the standalone webapp.
You can setup the camunda server by using the shared process engine way of deployment by using springboot starters of camunda
I have a simple Grails app that I've written to authenticate against an LDAP server. To develop it, I've installed ApacheDS locally and populated it with an LDIF file. Now I want to deploy it to CloudBees. Is it possible to install an LDAP server on CloudBees?
If not, an alternative seems to be to use the Grails ldap-server plugin. However, it doesn't have any documentation on how to configure it. How do I configure this plugin to load an LDIF on startup?
Unfortunately, running LDAP in a CloudBees app container/stack won't work because in-bound routing to your application port must be over HTTP/HTTPS.
Alternative 1: host the LDAP server outside of CloudBees (like on your own EC2 server)
Alternative 2: [for the highly motivated] you might be able to get a WebSocket gateway of some kind to work, but you'd special code on the client and server side to negotiate the socket stream hand-off outside of the LDAP server and client. [Client -> WS-Client --> CloudBees --> WS-Server --> LDAP Server]
gripe: why can't all protocols support virtual hosting like HTTP? -- that would make them much more Cloud-friendly :(