#POSTGRES APP MAC OS X#
#POSTGRES APP INSTALL#

Should display something like this: /Applications/Postgres.app/Contents/MacOS/bin/pg_configĢ. ?Run this command from a terminal window:

#POSTGRES APP INSTALL#

I already mentioned the problem is the gem install not finding pg_config during installation. Make sure that `gem install pg -v ?0.17.0'` succeeds before bundling. Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extensionĪn error occurred while installing pg (0.17.0), and Bundler cannot continue. The resulting error may look something like this: Installing pg (0.17.0) with native extensions The error can come up when running a bundle install or just a straight gem install pg from the command line.

?The error occurred on Rails 3.2 but 4.0 may show the same behavior. I ran into a situation where the pg gem would not install because it could not find pg_config in a known location on my Mac. I use PostgreSQL with my Ruby on Rails projects and combine that with the pg ruby gem. ?There are many ways that work, this just happens to be really simple. ?If you don?t know what it is, it?s a drop in app bundle for the PostgreSQL database.

#POSTGRES APP MAC OS X#

A thank you for the Blog post, Helm, Spring Actuator, Kubernetes probes, and the container support of the Jvms.I?ve been using the PostgreSQL Mac OS X app from Mattt Thompson and Heroku for quite some time now. With Helm and the blog post, it was easy to create a flexible script to setup the MovieManager project in Kubernetes. That simplifies the configuration in Kubernetes with resource limits. Spring Boot with Actuator and Kubernetes work together very well and are easy to setup. To get the port for the MovieManager, execute:įor example: 'moviemanagerservice NodePort 10.107.170.112 8080: 30197/TCP' To check if the pods have started, execute: To deploy the setup for the MovieManager in Minikube, start an empty Minikube cluster and execute this command in the helm directory of the project: The livenessProbe is activated after a successful start. After that the container gets started again. It checks every 5 seconds for at most 60 times. In lines 50-55, the startupProbe of Kubernetes setup to check if the image has started. In lines 44-49, the livenessProbe of Kubernetes is setup to check the Spring Actuator endpoint every 5 seconds after an initial delay of 5 seconds. In lines 40-41, the function 'list-envApp-variables' is used to set the environment variables the image needs. The Java 16 Jvm supports the container limits. In lines 33-39, the initial requested and max amounts of memory and cpu are defined. In lines 30-32, the image to be deployed is defined based on the values of the values.yaml. In lines 1-9, an opaque key/value map is created with the secrets of the MovieManager image. This shows only the part of the setup of the MovieManager. The added scripts are based on this blog post. In the templates directory is the _helpers.tpl file that contains scripts that are used to set values in the kubTemplate.yaml. The base name is important is used in a script.

In lines 26-34, the public and opaque variables of the MovieManager image are defined. The base name 'envDb' is important and is used in a script In lines 18-24, the public and opaque variables of the Postgresql image are defined. In lines 14-16, the secret names for the MovieManager and the Postgresql DB are defined. In the top 12 lines, the variables for the kubTemplate.yaml are defined. JWTTOKEN_SECRET: secret-key1234567890abcdefghijklmnopqrstuvwxyz POSTGRES_URL: 'jdbc:postgresql://postgresservice:5432/movies' JwtTokenSecrect: secret-key1234567890abcdefghijklmnopqrstuvpxyz #for production use replace the jwtTokenSecrect value with a random alphanumeric string of the same length or longer

Postgres app