JHipster has support to scaffold docker compose configuration YAML file. It creates /src/main/docker/prod.yml and sonar.yml files.
I opted for PostgresSQL with ElasticSearch. I scaffolded an entity called book. Then followed the instructions on JHipster Docker Compose. The main docker command were
$ docker-machine start default
Starting “default”…
(default) Check network to re-create if needed…
(default) Waiting for an IP…
Machine “default” was started.
Waiting for SSH to be available…
Detecting the provisioner…
Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
$ docker-machine env
export DOCKER_TLS_VERIFY=“1”
export DOCKER_HOST=“tcp://192.168.99.100:2376”
export DOCKER_CERT_PATH=“/Users/vineetb/.docker/machine/machines/default”
export DOCKER_MACHINE_NAME=“default”
# Run this command to configure your shell:
# eval $(docker-machine env)
$ eval $(docker-machine env)
$ docker-compose -f src/main/docker/prod.yml up
Starting jhipdock-elasticsearch
Starting jhipdock-postgresql
…
Change the application-prod.yml change the datasource:url and data:elasticsearch:data with the IP of the docker container
datasource:
driver-class-name: org.postgresql.ds.PGSimpleDataSource
url: jdbc:postgresql://192.168.99.100:5432/jhipdock
name:
username: jhipdock
password:
jpa:
database-platform: com.vineetb.jhipdock.domain.util.FixedPostgreSQL82Dialect
database: POSTGRESQL
show_sql: false
properties:
hibernate.cache.use_second_level_cache: true
hibernate.cache.use_query_cache: false
hibernate.generate_statistics: false
hibernate.cache.region.factory_class: org.hibernate.cache.ehcache.SingletonEhCacheRegionFactory
data:
elasticsearch:
cluster-name:
cluster-nodes: 192.168.99.100:9300
Start the JHipster application
./mvnw -Pprod
Neat customization of Bootstrap. Would love to try and change the colors using SAAS.
Created by: CollegeAtHome.com
I was invited to Mulesoft Summit in Boston. I took the T (Red line) into Boston and met my friend at Charles MGH. We walked from Charles MGH to Museum of Science. Nice weather. The walk along the river was pleasant but took us a while as we ended up crossing the bridge.
I attended the morning sessions
Networking with attendees was the best part. Met some folks already using Mule ESB, some who just started using Mule, some who were evaluating ESB’s. Overall people were pretty excited about Mule ESB. Some people had found issues with MuleStudio 3.3 beta IDE where it would not preserve content when they switched from code view to design view. Some were getting false compile errors. Some were running into limitations of the IDE but the ESB itself was quite feature rich. Lots of folks thought that using event based integration for loosely coupled systems was the right architectural approach to integrate systems.
Mule expression language was new and people were not familiar with its java like syntax. Why did they introduce yet another language? Apparently this language unifies xpath along with the EL syntax.
Some people were concerned with the pace at which product was changing and not being able to keep up with the new features for enterprise applications.
Some people were looking at migrating from Websphere/Weblogic ESB to Mule ESB - take big bang or incremental migration approach. Burden of maintaining both for extended period of time.
Mule Foundations lets companies establish conventions and best practices to make the best use while adopting Mule ESB.
I attended 2 lab track sessions on Developing with Mule Studio. Unfortunately they made use of MuleStudio 3.3 beta and people didn’t have the software installed. The session was quite informative and fast paced. The demo application was an integration between salesforce, get satisfaction, jira, twilio sms. The second session was demo of Mule ESB high availability, failover, monitoring capabilities. The demo was done using a custom application with lots of charts and Mule ESB Admin Console found in Enterprise Edition.
I missed the sessions upstairs on Major IT trends, Measuring effectiveness of ESB initiative.