personalStuff

Personal Stuff Pages

Some sub-pages/guides

I started to document in some MarkDown pages my knowledge so it can go fast to what I learned before:

1. ReactJs
2. Grafana
3. Kapacitor
4. Salt
5. Kubernetes
6. Apache2
7. GIT
8. VirtualBox
9. Jenkins
10. SonarQube
11. Debian LVM and RAID
12. Jira
13. SpringBatch
14. GitHub
15. ShellScripting

Thansk to GitHub pages this is now accessible from https://nicolasard.github.io/personalStuff/, There are some icons and tables don’t look as the markdown in the GitHub repo. I hope this is something I can fix, and not something GitHub didn’t considered before.

Initial guide for developers

This pretends to be a personal guide about how to set up a new development environment. I think that for these things it’s cool to don’t use auto-installers.

Profile of the developer: A guy running windows 7/10, who wants to deploy in Java for backend using Maven or Gradle. And for frontend wants to use Node with NPM.

Don’t use installers if you can. (This it’s going to help you if you don’t have admin/root privileges on your computer. )

Brief of the software I use:

| Application/Tool | Description | | — | — | | Java JDK | Lastly i’m developing in java 1.8 but this guide could apply to whatever version. | | Maven | Package manager for java | | Gradle | A new package manager for java | | MobaXTerm | A very good tool for windows local console, and ssh client |

Download the tools and setup the environment.

I use to download all the software in *C:\E\tools* but you can download the binaries wherever you want.

The setenv.bat script

This script to set a the environment.

@ECHO OFF
echo SETTING UP ENVIRONMENT VARIABLES

SET JAVA_HOME=E:\tools\java\jdk1.7.0_67
SET JRE_HOME=E:\tools\java\jdk1.7.0_67

SET PATH=%MAVEN_HOME%\bin;%ANT_HOME%\bin;%JAVA_HOME%\bin;%CATALINA_HOME%;%CATALINA_BASE%;%PATH%

Additional: Linux env

This setEnv.sh script

JDK_HOME=/path/to/jre/jre6

export PATH=$JDK_HOME/bin:$PATH

Puting some service/application in production

Making a Debian Linux init.d service script

I used this fabolous this fabulous guide from Debian. In my example I’m putting the jenkins stand alone war to run at server startup.

IMPORTANT ACLARATION: If we don’t put the BEGIN/END INIT INFO the command update-rc.d will not update the symbolic link to our /etc/init.d/jenkins file, and also will don’t trigger any error (I hate for some seconds the developers of the command )

#!/bin/sh
### BEGIN INIT INFO
# Provides:  Jenkins
# Required-Start:    $local_fs $remote_fs $network $syslog $named
# Required-Stop:     $local_fs $remote_fs $network $syslog $named
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts Jenkins
# Description:       starts Jenkins using start-stop-daemon
### END INIT INFO

# Jenkins init.d start script

SERVICE_NAME=Jenkins
JDK_HOME=/home/nardison/base/jdk1.8.0_144

export PATH=$JDK_HOME/bin:$PATH

case "$1" in
start)
                log_daemon_msg "Starting Jenkins"
                nohup java -jar /home/nardison/base/jenkins.war &> /home/nardison/base/jenkins.log
        ;;
stop)
                log_daemon_msg "Stoping Jenkins"
        ;;
esac

exit 0