A connection pool will cache your database connections and keep them open for future requests

Configure ProxySQL

• CC_MYSQL_PROXYSQL_USE_TLS: A boolean (true or false) to enable TLS between ProxySQL and your MySQL add-on. Defaults to true.
• CC_MYSQL_PROXYSQL_MAX_CONNECTIONS: An integer which defines how many maximum connections ProxySQL will open to your MySQL add-on. Defaults to 10. You can refer to our ProxySQL documentation to learn more about how you should compute the maximum connection value when auto scalability is involved.

Examples

PHP using PDO

<?php
// This variable is injected during the deployment
$socket = getenv("CC_MYSQL_PROXYSQL_SOCKET_PATH");
// Get the database name from the environment
$db = getenv("MYSQL_ADDON_DB");
// Get the database user from the environment
$user = getenv("MYSQL_ADDON_USER");
// Get the database password from the environment
$pass = getenv("MYSQL_ADDON_PASSWORD");
$dsn = "mysql:unix_socket=$socket;dbname=$db";
try {
  $pdo = new PDO($dsn, $user, $pass);
} catch (PDOException $e) {
  throw new PDOException($e->getMessage(), (int)$e->getCode());
}

Wordpress

// To connect using a unix socket, the syntax is: `localhost:/path/to/socket`
define('DB_HOST', "localhost:" . getenv("CC_MYSQL_PROXYSQL_SOCKET_PATH") );
// Get the database user from the environment
define('DB_USER', getenv("MYSQL_ADDON_USER"));
// Get the database password from the environment
define('DB_PASSWORD', getenv("MYSQL_ADDON_PASSWORD"));
// Get the database name from the environment
define('DB_NAME', getenv("MYSQL_ADDON_DB"));

Node.js

const mysql      = require('mysql');
const connection = mysql.createConnection({
  // Get ProxySQL unix domain socket path from the environment
  socketPath : process.env["CC_MYSQL_PROXYSQL_SOCKET_PATH"],
  // Get the database user from the environment
  user       : process.env["MYSQL_ADDON_USER"],
  // Get the database password from the environment
  password   : process.env["MYSQL_ADDON_PASSWORD"],
  // Get the database name from the environment
  database   : process.env["MYSQL_ADDON_DB"]
});
connection.connect(function(err) {
  if (err) {
    console.error('error connecting: ' + err.stack);
    return;
  }

  console.log('connected as id ' + connection.threadId);
});

Metrics

Documentation

Conclusion

A fully open source, adaptable platform for building and running a modern online publication. We power blogs, magazines and journalists from Zappos to Sky News.

Your local blog installation

mkdir myblog
cd myblog
ghost install local

[ldoguin@caolila:~/myblog]$ ls
content/  current@  versions/  config.development.json

rm content/themes/casper/
cp -r current/content/themes/casper/ content/themes/
git init
cd content/themes/
git submodule add https://github.com/curiositry/mnml-ghost-theme
git submodule add https://github.com/zutrinken/attila/

Your blog on Clever Cloud

clever create --type node myblog # create a node application
clever addon create mysql-addon --plan s_sml myblogsql # create a MySQL database
clever service link-addon myblogsql # Link the database to the application
clever env set NODE_ENV production # setup environment variable for production
clever env set CC_PRE_RUN_HOOK ./clevercloud.sh # run a specific script before the build phase
clever domain add mysuperblog.cleverapps.io # Add a test domain name

Installing Ghost for your Clever Cloud Application

#!/bin/sh
npm install -g ghost-cli # install ghost-cli on Clever Cloud
mkdir ghost # create a folder for a new local instance of Ghost
cd ghost
ghost install local
ghost stop
cp ../config.production.json . # copy the production configuration

Configure Ghost for Production

{
  "server": {
    "port": 8080,
    "host": "0.0.0.0"
  },
  "database": {
    "client": "mysql"
  },
  "mail": {
    "transport": "Direct"
  },
  "process": "local",
  "logging": {
    "level": "debug",
    "transports": [
      "stdout"
    ]
  },
  "paths": {
    "contentPath": "../../../content/"
  }
}

clever env set database__connection__host btxgsb7xrhkuydlmb3zr-mysql.services.clever-cloud.com
clever env set database__connection__user ukf6bzfjgd2eg0iw
clever env set database__connection__password 87xRmGJljF3aSgGullm
clever env set database__connection__database btxgsb7xrhkuydlmb3zr
clever env set database__connection__port 20222
clever env set url https://mysuperblog.cleverapps.io/

Run Ghost

{
    "name": "ghost",
    "version": "0.1.0",
    "description": "",
    "scripts": {
        "start": "ghost run --dir ghost"
    },
    "devDependencies": {
    },
    "dependencies": {
    }
}

Ignoring local development files

.ghost-cli
config.development.json
current
versions

Git push to Production

git add clevercloud.sh package.json config.production.json content
git commit -m "Initial commit"
clever deploy

Welcome to this new edition of One Framework a Day keeps the Boredom Away. In this series I will show you how to deploy a particular framework on Clever Cloud every day until I want to go back to boredom. Today it's about JHipster.

In each post of this series we'll see how to deploy a particular framework on Clever Cloud. Today we are taking a look at JHipster.

If you want to tag along, make sure you have git, a Clever Cloud account and that you have installed our CLI Clever-Tools.

What is JHipster?

JHipster is a development platform to generate, develop and deploy Spring Boot + Angular Web applications and Spring microservices.

JHipster, not your grandma's Yeoman generator, has been around for quite some time now and seems to be one of the default solution to scafold a modern SpringBoot+Angular stack. It supports many different options for both frontend and backend. Some of these supported by Clever Cloud.

So today we are going to deploy a JHipster stack based on MySQL. We are doing this mostly because our good friends Stephan Janssen and Antonio Goncalves told us they would love to see a JHipster/Clever Cloud integration. Before any convenient integration, I need to know how it works :)

Setup

Here are the steps to create and deploy a JHipster/MySQL application to Clever Cloud:

• First make sure you have installed JHipster: yarn global add generator-jhipster
• Create a folder for your future application: mkdir clever-jhipster && cd clever-jhipster
• Run JHipster and follow instructions on screen jhipster
• Make sure you select MySQL and Maven in the wizard
• Create the MySQL database: clever addon create mysql-addon --plan dev --region eu jhipstersql
• Create the Clever Cloud application: clever create --type maven cleverJHipster
• Link your database to your application: clever service link-addon jhipstersql
• Create a clevercloud folder at the root of your project: mkdir clevercloud
• Create a maven.json file with the following content: vim clevercloud/maven.json

{
  "build": {
    "type": "maven",
    "goal": "-Pprod package -DskipTests"
  },
  "deploy": {
    "jarName": "./target/jhipster-0.0.1-SNAPSHOT.war"
  }
}

This file tells Clever Cloud to run mvn -Pprod package -DskipTests and then java -jar ./target/my-app-0.0.1-SNAPSHOT.war. Don't forget to change the jarName according to the name of your project.

Now to configure the application we will create aclevercloud/application-clever.yml file containing all the specific configuration to run on Clever Cloud.

spring:
    datasource:
        url: jdbc:mysql://${MYSQL_ADDON_HOST}:${MYSQL_ADDON_PORT}/${MYSQL_ADDON_DB}?useUnicode=true&characterEncoding=utf8&useSSL=false
        username: ${MYSQL_ADDON_USER}
        password: ${MYSQL_ADDON_PASSWORD}
        maxActive: 5

Here I am using variable already predefined by CleverCloud with the ${} synthax. To make sure this file is found while running the application, we need to copy it right before running with a hook: clever env set CC_PRE_RUN_HOOK "cp ./clevercloud/application-clever.yml ./application-prod.yml"

Deploy

Select the build dedicated instance because the JHipster build is memory greedy. To do that you have to go on the WebConsole, in your application, in the Information tab and tick the Enable dedicated build instance checkbox.

Now commit your changes and run clever deploy, this will push your code to our remote git branch and deploy it. At the end you can type clever open and it should open your website in your default web browser.

We plan to have a better integration to JHipster through a module. What kind of features would you like to have?

Since the beginning, anyone can use mutual Clever Cloud databases for free because it was in beta.
Actually, this test period is over and databases will be charged from July 1st 2013.

In order to fit high performance needs, we will launch dedicated databases soon

The finesse pricing is daily. It means that once you create a database, you are charged for one day usage, and so on.
For example, a S database will cost 0,23 €/day.

The pricing plans for PostgreSQL and MySQL will be the following:

MySQL pricing plans

	S	M	L
Connexions	15	30	40
Size	1 Go	5 Go	10 Go
Price	7 €/month (0,23 €/day)	35 €/month (1,17 €/day)	70 €/month (2,33 €/day)

PostgreSQL pricing plans

	S	M	L
Connexions	15	30	40
Size	1 Go	5 Go	10 Go
Price	7 €/month (0,23 €/day)	35 €/month (1,17 €/day)	70 €/month (2,33 €/day)

You will be able to configure the number of Scalers dedicated to your database as you can do with apps.

These databases will be more powerful, larger and more scalable than the mutualised databases.

Version française

Depuis le début, tout le monde pouvait utiliser gratuitement les bases de données mutuelles sur Clever Cloud puisqu’elles étaient en beta. Désormais, cette phase de test s’achève et l’utilisation des bases de données sera facturée à partir du 1er juillet 2013.

Les tarifs pour une PostgreSQL et une MySQL seront les suivants:

Tarification PostgreSQL

	S	M	L
Connexions	15	30	40
Taille	1 Go	5 Go	10 Go
Prix (HT)	7 €/mois (0,23 €/jour)	35 €/mois (1,17 €/jour)	70 €/mois (2,33 €/jour)

Tarification MySQL

	S	M	L
Connexions	15	30	40
Taille	1 Go	5 Go	10 Go
Prix (HT)	7 €/mois (0,23 €/jour)	35 €/mois (1,17 €/jour)	70 €/mois (2,33 €/jour)

L’ajustement du pricing est quotidien. Cela signifie qu’une fois que vous avez créé la base de données, vous serez facturé pour une journée d’usage, et ainsi de suite.

À titre d’exemple, une base de données de taille S coûtera 0,23 €/jour.

Pour répondre aux besoins de haute performance, nous lancerons bientôt des bases de données dédiées

Il sera possible de configurer le nombre de Scalers dédiés à la base de données, comme il est déjà possible de le faire avec les applications.

Ces bases de données seront plus puissantes, plus scalables et auront plus de capacité de stockage que les bases de données mutualisées.