metlos

public class PythonScriptEngineProvider implements ScriptEngineProvider {

    @Override
    public String getSupportedLanguage() {
        return "python";
    }

    @Override
    public ScriptEngineInitializer getInitializer() {
        return new PythonScriptEngineInitializer();

metlos

public class PythonScriptEngineInitializer implements ScriptEngineInitializer {

    private static final Log LOG = LogFactory.getLog(PythonScriptEngineInitializer.class);

    static {
        Properties props = new Properties();
        props.put("python.packages.paths", "java.class.path,sun.boot.class.path");
        props.put("python.packages.directories", "java.ext.dirs");
        props.put("python.cachedir.skip", false);
        PythonInterpreter.initialize(System.getProperties(), props, null);

metlos

import sys

sys.path.append("__rhq__:rhq://repositories/my_repo/")

import my_script as foo

...

metlos

   Example:
   <bundle-target>
      <destination-base-dir name="Deploy Directory" description="The deployment directory for a standalone server">
         <value-context>measurementTrait</value-context>
         <value-name>deployDir</value-name>
      </destination-base-dir>
      <special-destination name="Patch Installer" description="Accepts JBoss AS patches and installs them to a standalone server" bundle-type="JBoss AS Patch Bundle">
         <value-reference reference-name="host" context="pluginConfiguration" name="hostname"/>
         <value-reference context="pluginConfiguration" name="port"/>
         <value-reference context="pluginConfiguration" name="user"/>

metlos

[alias]

    tracking-branch = !git for-each-ref --format='%(upstream:short)' $(git symbolic-ref -q HEAD)
    
    current-branch = !git rev-parse --abbrev-ref HEAD
    
    #last commit
    last = log -1
   
    #assumes the upstream repo is called origin

metlos

/*-------------------------------------------------------------------------
*
* Copyright (c) 2004-2014, PostgreSQL Global Development Group
*
*
*-------------------------------------------------------------------------
*/
package org.postgresql.test.leaks;

import java.lang.ref.WeakReference;

metlos

cpath of entity - enCpath
cpath of element - elCpath

general element
---------------
RUD -> /path/{elCpath}   (or /element/{elCpath}? because this isn't consistent with the rest of the REST are we asking for the path of a {elCpath} ?)

relationships
-------------
CRUD -> /relationships/{enCpath}

metlos

#!/usr/bin/sh
# 
# An example hook script to check the commit log message.
# Called by "git commit" with one argument, the name of the file
# that has the commit message.  The hook should exit with non-zero
# status after issuing an appropriate message if it wants to stop the
# commit.  The hook is allowed to edit the commit message file.
#
# To enable this hook, rename this file to "commit-msg".

metlos

This expects a datasource called "Che" in grafana.

To do that, simply create a new datasource in grafana UI with the type "Prometheus" and the URL pointing to the Prometheus server, e.g. http://prometheus:9090.

metlos

Import this into your Che installation to gain monitoring and visualization capabilities.

All you need to do is to create a route exposing your grafana service. Also make sure that Prometheus is configured to scrape your Che server correctly - look at the prometheus-config config map and make sure that the targets lists the correct hostname of the Che server within your project.

Also make sure that your Che server is configured to expose the metrics. The CHE_METRICS_ENABLED environment variable of the che deployment needs to be set to true.

To access the Grafana dashboard, use the username admin with password admin. Once in Grafana, you will see a preconfigured dashboard called "Che Server" containing some basic stats about the Che installation.