Difference between revisions of "User talk:Mmccarn"

From SME Server
Jump to navigationJump to search
m (update time stamp)
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
==Install mariadb 'alongside' mysql==
+
=[[User:Mmccarn|Mmccarn]] ([[User talk:Mmccarn|talk]]) [[User:Mmccarn|Mmccarn]] ([[User talk:Mmccarn|talk]]) 13:10, 22 January 2018 (CET) =
−
===Draft notes on mariadb installation===
+
==Wazuh==
−
  <nowiki>
+
===Repo===
−
#####################################################################################
+
  <nowiki>/sbin/e-smith/db yum_repositories set wazuh repository \
−
# BEGIN
+
Name 'Wazuh repository' \
−
#####################################################################################
+
BaseURL 'https://packages.wazuh.com/3.x/yum/' \
−
# yum repos aren't useful; use the side-by-side install
+
EnableGroups no \
−
# Install mariadb side-by-side with mysql on SME Server v8
+
GPGCheck yes \
−
# From: https://mariadb.com/kb/en/installing-mariadb-alongside-mysql/
+
GPGKey https://packages.wazuh.com/key/GPG-KEY-WAZUH \
−
#
+
Visible no \
−
# create user 'mariadb' in server-manager
+
status disabled</nowiki>
−
#
+
 
−
cd ~
+
===Agent Configuration===
−
mkdir -p addons
+
[https://documentation.wazuh.com/current/installation-guide/installing-wazuh-agent/wazuh_agent_rpm.html Wazuh Client Installation Instructions]
−
cd addons
+
 
−
RELEASE=5.5.34
+
Wazuh 3.x installs correctly from the yum repository:
−
wget https://downloads.mariadb.org/interstitial/mariadb-$RELEASE/kvm-bintar-hardy-x86/mariadb-$RELEASE-linux-i686.tar.gz/from/http://mirror.jmu.edu/pub/mariadb
+
yum --enablerepo=wazuh install wazuh-agent
−
cd /opt
+
 
−
tar zxvf ~/addons/mariadb-$RELEASE-linux-i686.tar.gz
+
Create the client account on the wazuh manager:
−
ln -s mariadb-$RELEASE-linux-i686 mariadb
+
/var/ossec/bin/agent-auth -m [ip.of.wazuh.server]
−
mkdir mariadb-data
+
 
−
cp mariadb/support-files/my-medium.cnf mariadb-data/my.cnf
+
Replace "MANAGER_IP" with the IP address of the wazuh manager in this section of /var/ossec/etc/ossec.conf:
−
#
+
  <nowiki>...
−
# edit my.cnf as described on the mariadb-alongside-mysql howto (link above)
+
<client>
−
chown -R mariadb:mariadb mariadb-data mariadb mariadb-$RELEASE-linux-i686
+
    <server>
−
#
+
      <address>MANAGER_IP</address>
−
cp mariadb/support-files/mysql.server /etc/init.d/mariadb
+
    </server>
−
chmod +x /etc/init.d/mariadb
+
    <config-profile>rhel, rhel6</config-profile>
−
#
+
</client>
−
# edit /etc/init.d/mariadb as described in the howto
+
...
−
#
 
−
cd /opt/mariadb
 
−
scripts/mysql_install_db --defaults-file=/opt/mariadb-data/my.cnf
 
−
cd /etc/init.d
 
−
chkconfig --add mariadb
 
−
chkconfig --levels 3 mariadb on
 
−
# SME Server uses runlevel 7...
 
−
mv /etc/rc3.d/S64mariadb /etc/rc7.d
 
−
#
 
−
# customizations not mentioned in the howto:
 
−
mkdir /var/run/mariadb
 
−
chown mariadb:maridb /var/run/mariadb
 
−
#
 
−
# customize the execution line in /etc/init.d/mariadb
 
−
#
 
−
# version from howto:
 
−
# $bindir/mysqld_safe --defaults-file=/opt/mariadb-data/my.cnf --datadir="$datadir" --pid-file="$mysqld_pid_file_path" $other_args >/dev/null 2>&1 &
 
−
#
 
−
# version I'm using:
 
−
# $bindir/mysqld_safe --defaults-file=/opt/mariadb-data/my.cnf --datadir="/opt/mariadb-data" --pid-file="/var/run/mariadb/mariadb.pid" $other_args >/dev/null 2>&1 &
 
−
#
 
−
# Finally, testing access requires asking for a password, then entering an empty password (SME feeds the 'root'@'localhost' password to mysql by default:
 
−
# mysql -e "SELECT VERSION();" --port=3307 --protocol=TCP -p
 
−
#
 
−
# set root password in mariadb same as root password in mysql
 
−
mysql --port=3307 --protocol=TCP -p < /var/service/mysqld/set.password
 
−
#
 
−
# Now the example version check from the howto works:   
 
−
mysql -e "SELECT VERSION();" --socket=/opt/mariadb-data/mariadb.sock
 
 
</nowiki>
 
</nowiki>
  
−
===Backup & Restore===
+
Start the agent
−
* (RequestedDeletion) Nice notes. Would it be worth it to look at the pre-backup and pre-restore events (And config db settings) so MariaDB databases are being backup up ?
+
/etc/init.d/wazuh-agent start
−
====/etc/e-smith/events/actions/mariadb-dump-tables====
 
−
* Based on /etc/e-smith/events/actions/mysql-dump-tables
 
−
* "CONNECT" options separated out for easy modification and potential movement into db variables
 
−
* "-x" option added to the mysqldump command line to avoid an error about locking log files
 
−
<nowiki>#!/bin/sh
 
−
#CONNECT=--socket=/opt/mariadb-data/mariadb.sock
 
−
CONNECT="--protocol=TCP --port=3307"
 
  
−
if ! $(mysqladmin $CONNECT ping >/dev/null 2>&1)
+
===SME Customizations===
−
then
+
I added these instructions to /var/ossec/etc/ossec.conf:
−
     echo "mariadb is not running - no tables dumped" >&2
+
<nowiki>  <localfile>
−
     exit 0
+
    <log_format>djb-multilog</log_format>
−
fi
+
    <location>/var/log/dovecot/current</location>
 +
  </localfile>
 +
 
 +
  <localfile>
 +
    <log_format>djb-multilog</log_format>
 +
    <location>/var/log/tinydns/current</location>
 +
  </localfile>
 +
  <localfile>
 +
    <log_format>djb-multilog</log_format>
 +
    <location>/var/log/dnscache/current</location>
 +
  </localfile>
 +
 
 +
  <localfile>
 +
     <log_format>command</log_format>
 +
    <command>grep -h logterse /var/log/*qpsmtpd/current</command>
 +
    <alias>s/qpsmtpd</alias>
 +
     <frequency>360</frequency>
 +
  </localfile>
 +
</nowiki>
  
−
mkdir -p /home/e-smith/db/mariadb
+
And this instruction to /var/ossec/etc/local_internal_options.conf:
−
for db in $(mysql $CONNECT -BNre "show databases;")
+
  <nowiki># from https://documentation.wazuh.com/2.0/user-manual/reference/ossec-conf/localfile.html
−
do
+
# 'it may not be permissible in all environments to allow the Wazuh manager to run
−
    mysqldump $CONNECT -x --add-drop-table  -QB "$db" -r /home/e-smith/db/mariadb/"$db".dump  || exit 1
+
# arbitrary commands on agents in their root security context.'
−
done</nowiki>
+
logcollector.remote_commands=1
−
====/etc/e-smith/events/actions/mariadb-load-tables====
+
</nowiki>
−
* based on /etc/e-smith/events/actions/mysql-load-tables
 
−
* doesn't actually load the dbs
 
−
* NEEDS EXAMINATION!
 
−
  <nowiki>#!/bin/sh
 
−
#CONNECT=--socket=/opt/mariadb-data/mariadb.sock
 
−
CONNECT="--protocol=TCP --port=3307"
 
−
MARIADATA=/opt/mariadb-data
 
  
−
if ! $(mysqladmin $CONNECT ping >/dev/null 2>&1)
+
And restarted the agent using
−
then   
+
/etc/init.d/wazuh-agent restart
−
    echo "mariadb is not running - no tables restored" >&2
 
−
    exit 0
 
−
fi
 
  
−
if [ ! -f $MARIADATA/mysql/user.frm ]
+
=Older=
−
then
+
Mariadb notes moved to [[MariaDB_alongside_MySQL]]
−
    mkdir -p /etc/e-smith/mariadb/init
 
−
    for db in $(ls /home/e-smith/db/mariadb/*.dump 2> /dev/null | grep -v '/mysql.dump')
 
−
    do
 
−
        mv $db /etc/e-smith/mariadb/init/01_$(basename $db .dump).sql
 
−
    done
 
−
fi</nowiki>
 
−
====Automation====
 
−
=====Backup=====
 
−
* Link mariadb-dump-tables into the pre-backup event
 
−
* Dumped tables should be included in backups as they are stored under /home/e-smith
 
−
<nowiki>cd /etc/e-smith/events/pre-backup
 
−
ln -s ../actions/mariadb-dump-tables S20mariadb-dump-tables</nowiki>
 
−
=====Restore - NEEDS WORK=====
 
−
The SME Server mysql restore is complicated by various factors that may not apply to a mariadb "alongside" installation.
 
−
Here's what would need to be done to restore all mariadb databases:
 
−
* Reinstall mariadb, including setting the password to match the mysql root password
 
−
* Restore the 'dump' files created during pre-backup individually using:
 
−
<nowiki>cd /home/e-smith/db/mariadb
 
−
CONNECT=--socket=/opt/mariadb-data/mariadb.sock
 
−
mysql $CONNECT < <dbname>.dump</nowiki>
 
−
 
 
==Install Moodle 2.6 using git==
 
==Install Moodle 2.6 using git==
 
===Requirements===
 
===Requirements===
Line 258: Line 209:
 
* Shibboleth
 
* Shibboleth
 
* Web services authentication
 
* Web services authentication
 +
 +
=====Create Additional Administrators=====
 +
http://docs.moodle.org/26/en/Assign_admins
 +
 +
==TiddlyWiki5 Using Node.js==
 +
[http://tiddlywiki.com/ TiddlyWiki] is "a complete interactive wiki in JavaScript."
 +
 +
{{Warning box|The install and update routines shown here are based on notes from a working installation.<br>The removal routines are untested.}}
 +
 +
===Prerequisites===
 +
# node.js > 8.x (note: I was unable to find a binary installer for curent node releases; I use 'gcc' and compile locally)
 +
# [https://npmjs.org/package/npm npm]
 +
 +
===Assumptions===
 +
# wiki content will be stored in /opt/tiddlywiki/tiddlers
 +
# tiddlywiki code will be stored in /opt/tiddlywiki/node_modules
 +
# tiddlywiki will run as user 'www'
 +
# tiddlywiki logs will be run as 'smelog'
 +
# tiddlywiki will be daemonized using daemontools
 +
 +
===Installation===
 +
<nowiki>mkdir /opt/tiddlywiki
 +
cd /opt/tiddlywiki
 +
npm install tiddlywiki
 +
chown -R www:www /opt/tiddlywiki/.</nowiki>
 +
 +
====Create daemontools scripts, folders, etc====
 +
The code below is designed to be run by copy/paste into a server console prompt.
 +
 +
<nowiki>mkdir -p /var/service/tiddlywiki/log
 +
mkdir -p /var/log/tiddlywiki
 +
chown -R smelog:smelog /var/log/tiddlywiki
 +
cd /service
 +
ln -s /var/service/tiddlywiki .
 +
cd /var/service/tiddlywiki
 +
touch down
 +
    #
 +
    # create the service 'run' file
 +
    #
 +
echo '#!/bin/sh
 +
#
 +
# setup node environment
 +
#
 +
exec 2>&1
 +
#
 +
APP_DIR=/opt/tiddlywiki
 +
USER=www
 +
#
 +
NODE_EXEC=/usr/local/bin/node
 +
NODE_ENV=production
 +
NODE_CONFIG_DIR=$APP_DIR
 +
NODE_APP=node_modules/tiddlywiki/tiddlywiki.js
 +
NODE_ARGS=--server
 +
echo "Starting $NODE_EXEC $APP_DIR/$NODE_APP $NODE_ARGS"
 +
  cd $APP_DIR
 +
  exec                            \
 +
  setuidgid $USER                  \
 +
  $NODE_EXEC $NODE_APP $NODE_ARGS
 +
' > /var/service/tiddlywiki/run
 +
 +
    #
 +
    # Create log/run
 +
    #
 +
echo '#!/bin/sh
 +
#
 +
exec                                    \
 +
    /usr/local/bin/setuidgid smelog    \
 +
    /usr/local/bin/multilog t s5000000  \
 +
    /var/log/tiddlywiki' > /var/service/tiddlywiki/log/run </nowiki>
 +
 +
====start the service====
 +
sv u tiddlywiki
 +
 +
====check the log files to see if it worked====
 +
tail /var/log/tiddlywiki/current
 +
 +
====Create init.d script and startup.shutdown scripts====
 +
This segment of code will create the scripts needed to start the service at boot and to stop the service at shutdown.
 +
 +
<nowiki>SERVICE=tiddlywiki
 +
#
 +
cd /etc/rc.d/init.d
 +
ln -s daemontools $SERVICE
 +
cd /etc/rc.d/rc0.d
 +
ln -s /etc/rc.d/init.d/e-smith-service K01$SERVICE
 +
cd /etc/rc.d/rc1.d
 +
ln -s /etc/rc.d/init.d/e-smith-service K01$SERVICE
 +
cd /etc/rc.d/rc6.d
 +
ln -s /etc/rc.d/init.d/e-smith-service K01$SERVICE
 +
cd /etc/rc.d/rc7.d
 +
ln -s /etc/rc.d/init.d/e-smith/service S99$SERVICE</nowiki>
 +
 +
====Create config db entry====
 +
/etc/rc.d/init.d/e-smith-service will start a service whose status is ''enabled'', and will not start it otherwise.
 +
 +
<nowiki>SERVICE=tiddlywiki
 +
config set $SERVICE service access public status enabled</nowiki>
 +
 +
====Proxypass Domain for WAN access====
 +
I found that I needed to [http://wiki.contribs.org/SME_Server:Documentation:ProxyPass#ProxyPass_a_domain proxypass a domain].  An [http://wiki.contribs.org/SME_Server:Documentation:ProxyPass#ProxyPass_a_alias.2Fdirectory.2Flocation alias/directory/location] proxypass generated errors and prevented edits from saving correctly.
 +
 +
<nowiki>DOMAIN=tiddlywiki.domain.tld
 +
db domains set $DOMAIN domain Nameservers internet ProxyPassTarget http://localhost:8080/ TemplatePath ProxyPassVirtualHosts
 +
#
 +
# Several TiddlyWiki 5 Plugins require AllowEncodedSlashes On in httpd.conf
 +
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/ProxyPassVirtualHosts
 +
echo '#
 +
# AllowEncodedSlashes On from custom template in ProxyPassVirtualHosts
 +
AllowEncodedSlashes On ' > /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/ProxyPassVirtualHosts/04ProxyPassVirtualHosts
 +
signal-event domain-create $DOMAIN</nowiki>
 +
 +
===Update to the latest tiddlywiki code===
 +
<nowiki>cd /opt/tiddlywiki && setuidgid www npm update tiddlywiki && sv t tiddlywiki</nowiki>
 +
 +
===COMPLETE Removal===
 +
<nowiki>DOMAIN=tiddlywiki.domain.tld
 +
signal-event domain-delete $DOMAIN
 +
db domains delete $DOMAIN
 +
#
 +
SERVICE=tiddlywiki
 +
config delete $SERVICE
 +
find /etc/rc.d -name "*$SERVICE*" -exec 'rm' -f "{}" \;
 +
'rm' -rf /service/$SERVICE
 +
'rm' -rf /var/service/$SERVICE
 +
'rm' -rf /var/log/$SERVICE
 +
#
 +
cd /opt/$SERVICE
 +
npm remove $SERVICE
 +
cd /opt
 +
'rm' -rf /opt/$SERVICE </nowiki>
  
 
==Notes on check_earlytalker==
 
==Notes on check_earlytalker==

Latest revision as of 13:11, 22 January 2018

Mmccarn (talk) Mmccarn (talk) 13:10, 22 January 2018 (CET)

Wazuh

Repo

/sbin/e-smith/db yum_repositories set wazuh repository \
Name 'Wazuh repository' \
BaseURL 'https://packages.wazuh.com/3.x/yum/' \
EnableGroups no \
GPGCheck yes \
GPGKey https://packages.wazuh.com/key/GPG-KEY-WAZUH \
Visible no \
status disabled

Agent Configuration

Wazuh Client Installation Instructions

Wazuh 3.x installs correctly from the yum repository: 

yum --enablerepo=wazuh install wazuh-agent

Create the client account on the wazuh manager: 

/var/ossec/bin/agent-auth -m [ip.of.wazuh.server]

Replace "MANAGER_IP" with the IP address of the wazuh manager in this section of /var/ossec/etc/ossec.conf: 

...
<client>
    <server>
      <address>MANAGER_IP</address>
    </server>
    <config-profile>rhel, rhel6</config-profile>
</client>
...

Start the agent 

/etc/init.d/wazuh-agent start

SME Customizations

I added these instructions to /var/ossec/etc/ossec.conf: 

  <localfile>
    <log_format>djb-multilog</log_format>
    <location>/var/log/dovecot/current</location>
  </localfile>

  <localfile>
    <log_format>djb-multilog</log_format>
    <location>/var/log/tinydns/current</location>
  </localfile>
  <localfile>
    <log_format>djb-multilog</log_format>
    <location>/var/log/dnscache/current</location>
  </localfile>

  <localfile>
    <log_format>command</log_format>
    <command>grep -h logterse /var/log/*qpsmtpd/current</command>
    <alias>s/qpsmtpd</alias>
    <frequency>360</frequency>
  </localfile>

And this instruction to /var/ossec/etc/local_internal_options.conf: 

# from https://documentation.wazuh.com/2.0/user-manual/reference/ossec-conf/localfile.html
# 'it may not be permissible in all environments to allow the Wazuh manager to run
#  arbitrary commands on agents in their root security context.'
logcollector.remote_commands=1

And restarted the agent using 

/etc/init.d/wazuh-agent restart

Older

Mariadb notes moved to MariaDB_alongside_MySQL

Install Moodle 2.6 using git

Requirements

  • Recommended minimum browser: recent Google Chrome, recent Mozilla Firefox, Safari 6, Internet Explorer 9 (IE 10 required for drag and drop of files from outside the browser into Moodle)
  • Moodle upgrade: Moodle 2.2 or later (if upgrading from earlier versions, you must upgrade to 2.2.11 as a first step)
  • Minimum DB versions: PostgreSQL 8.3, MySQL 5.1.33, MariaDB 5.3.5, MSSQL 2005 or Oracle 10.2
  • Minimum PHP version: PHP 5.3.3 (always use latest PHP 5.4.x or 5.5.x on Windows - http://windows.php.net/download/)
  • New recommended PHP extensions: zlib, OPcache

DB Version

SME Server 8.x comes with MySQL v5.0.95. In order to install Moodle without risking destabilizing a SME server by changing the MySQL version, you can install MariaDB 5.3.54 alongside MySql.

OPcache

Zend OPcache is built-in to PHP 5.5, and can be compiled to work with PHP 5.3.3.

I have not been able to find a source online for an RPM for OPcache.

I believe this will make Moodle run more slowly than it would *with* OPcache.

Installation

Prepare your server

Install useful php modules
  • During installation, Moodle will request php-soap, php-xmlrpc and php-intl. These are all available from the 'smeaddons' repository, and can be installed using:
yum install php-soap php-xmlrpc php-intl
Create an ibay
  • Create an ibay named 'moodle' in server-manager
  • Customize some of the settings on the new moodle ibay
IBAY=moodle
/sbin/e-smith/db accounts setprop $IBAY \
FollowSymLinks enabled \
CgiBin enabled \
AllowOverride All \
Group www \
PublicAccess global \
PHPBaseDir "/home/e-smith/files/ibays/$IBAY/:/tmp/" \
UserAccess wr-group-rd-everyone
/sbin/e-smith/signal-event remoteaccess-update
#
mkdir /home/e-smith/files/ibays/$IBAY/moodledata
chown www:www /home/e-smith/files/ibays/$IBAY/moodledata
#
Create a database
  • Install Mariadb alongside mysql
  • create a mariadb database for moodle
# Generate a random 23 character password
DBPASS=`< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c23`
DBNAME=moodle
DBUSER=moodle
CONNECT=--socket=/opt/mariadb-data/mariadb.sock
#
echo ;\
echo ;\
echo Creating Database using: ;\
echo DBNAME=$DBNAME ;\
echo DBUSER=$DBUSER ;\
echo DBPASS=$DBPASS ;\
echo ;\
echo Save this information!  You will need it later during initial application setup! \(press \<enter\> when ready\) ;\
read
#
mysql $CONNECT -e "create database $DBNAME; 
grant all privileges on $DBNAME.* to $DBUSER@localhost identified by \"$DBPASS\" with grant option;
quit"

Install Moodle

Download & Checkout using git
    #
    # Download moodle using git
    # http://docs.moodle.org/26/en/Git_for_Administrators#Obtaining_the_code_from_Git
    #
IBAY=moodle
cd /home/e-smith/files/ibays/$IBAY
mv html html.`date +%F-%H%M%S`
git clone git://git.moodle.org/moodle.git html
cd html
git branch -a
git branch --track MOODLE_26_STABLE origin/MOODLE_26_STABLE
git checkout MOODLE_26_STABLE
#
# correct ownership
signal-event ibay-modify $IBAY
Run the moodle installer
#
# run the moodle command line installer
# if prompted, set:
    # mysql port: 3307
    # mysql socket: /opt/mariadb-data/mariadb.sock
    #
cd /home/e-smith/files/ibays/$IBAY/html/admin/cli
sudo -u www /usr/bin/php install.php
Correct database settings if necessary

If you were not prompted for database socket, port, or other connection settings during the command line setup, you will need to correct the settings manually.

The database connection settings are stored in this file: 

/home/e-smith/files/ibays/moodle/html/config.php

If you have just run the above database connection commands in the same putty session, you can correct your moodle settings using: 

IBAY=moodle
sed -i  s/dbname.*/dbname\ \ \ \ \=\ \'$DBNAME\'\;/  /home/e-smith/files/ibays/$IBAY/html/config.php
sed -i  s/dbuser.*/dbuser\ \ \ \ \=\ \'$DBUSER\'\;/  /home/e-smith/files/ibays/$IBAY/html/config.php
sed -i  s/dbpass.*/dbpass\ \ \ \ \=\ \'$DBPASS\'\;/  /home/e-smith/files/ibays/$IBAY/html/config.php

Optional Settings

Scan Uploads using ClamAV

Moodle can be configured to scan all user files when uploaded. 

mysql $CONNECT  -e "use moodle;
update mdl_config set value=1 where name='runclamonupload';
update mdl_config set value='/usr/bin/clamscan' where name='pathtoclam';
quit"
Authentication Settings

To configure authentication mechanisms:

  • Login to Moodle using an account with administrative rights
  • Select 'Site Administration'
    • Select 'Plugins'
      • Select 'Authentication'

Moodle can be configured to authenticate users using any of the methods listed below:

  • Manual accounts
  • No login
  • CAS server (SSO)
  • Email-based self-registration
  • External database
  • FirstClass server
  • IMAP server
    • Select 'imapcert' if your IMAP server uses a self-signed certificate
  • LDAP server
  • MNet authentication
  • NNTP server
  • No authentication
  • PAM (Pluggable Authentication Modules)
  • POP3 server
  • RADIUS server
  • Shibboleth
  • Web services authentication
Create Additional Administrators

http://docs.moodle.org/26/en/Assign_admins

TiddlyWiki5 Using Node.js

TiddlyWiki is "a complete interactive wiki in JavaScript."


Warning.png Warning:
The install and update routines shown here are based on notes from a working installation.
The removal routines are untested.


Prerequisites

  1. node.js > 8.x (note: I was unable to find a binary installer for curent node releases; I use 'gcc' and compile locally)
  2. npm

Assumptions

  1. wiki content will be stored in /opt/tiddlywiki/tiddlers
  2. tiddlywiki code will be stored in /opt/tiddlywiki/node_modules
  3. tiddlywiki will run as user 'www'
  4. tiddlywiki logs will be run as 'smelog'
  5. tiddlywiki will be daemonized using daemontools

Installation

mkdir /opt/tiddlywiki
cd /opt/tiddlywiki
npm install tiddlywiki
chown -R www:www /opt/tiddlywiki/.

Create daemontools scripts, folders, etc

The code below is designed to be run by copy/paste into a server console prompt. 

mkdir -p /var/service/tiddlywiki/log
mkdir -p /var/log/tiddlywiki
chown -R smelog:smelog /var/log/tiddlywiki
cd /service
ln -s /var/service/tiddlywiki .
cd /var/service/tiddlywiki
touch down
    #
    # create the service 'run' file
    #
echo '#!/bin/sh
#
# setup node environment
#
exec 2>&1
#
APP_DIR=/opt/tiddlywiki
USER=www
#
NODE_EXEC=/usr/local/bin/node
NODE_ENV=production
NODE_CONFIG_DIR=$APP_DIR
NODE_APP=node_modules/tiddlywiki/tiddlywiki.js
NODE_ARGS=--server
echo "Starting $NODE_EXEC $APP_DIR/$NODE_APP $NODE_ARGS"
  cd $APP_DIR
  exec                             \
  setuidgid $USER                  \
  $NODE_EXEC $NODE_APP $NODE_ARGS
' > /var/service/tiddlywiki/run

    #
    # Create log/run
    #
echo '#!/bin/sh
#
exec                                    \
    /usr/local/bin/setuidgid smelog     \
    /usr/local/bin/multilog t s5000000  \
    /var/log/tiddlywiki' > /var/service/tiddlywiki/log/run

start the service

sv u tiddlywiki

check the log files to see if it worked

tail /var/log/tiddlywiki/current

Create init.d script and startup.shutdown scripts

This segment of code will create the scripts needed to start the service at boot and to stop the service at shutdown. 

SERVICE=tiddlywiki
#
cd /etc/rc.d/init.d
ln -s daemontools $SERVICE
cd /etc/rc.d/rc0.d
ln -s /etc/rc.d/init.d/e-smith-service K01$SERVICE
cd /etc/rc.d/rc1.d
ln -s /etc/rc.d/init.d/e-smith-service K01$SERVICE
cd /etc/rc.d/rc6.d
ln -s /etc/rc.d/init.d/e-smith-service K01$SERVICE
cd /etc/rc.d/rc7.d
ln -s /etc/rc.d/init.d/e-smith/service S99$SERVICE

Create config db entry

/etc/rc.d/init.d/e-smith-service will start a service whose status is enabled, and will not start it otherwise. 

SERVICE=tiddlywiki
config set $SERVICE service access public status enabled

Proxypass Domain for WAN access

I found that I needed to proxypass a domain. An alias/directory/location proxypass generated errors and prevented edits from saving correctly. 

DOMAIN=tiddlywiki.domain.tld
db domains set $DOMAIN domain Nameservers internet ProxyPassTarget http://localhost:8080/ TemplatePath ProxyPassVirtualHosts
#
# Several TiddlyWiki 5 Plugins require AllowEncodedSlashes On in httpd.conf
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/ProxyPassVirtualHosts
echo '# 
# AllowEncodedSlashes On from custom template in ProxyPassVirtualHosts
AllowEncodedSlashes On ' > /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/ProxyPassVirtualHosts/04ProxyPassVirtualHosts
signal-event domain-create $DOMAIN

Update to the latest tiddlywiki code

cd /opt/tiddlywiki && setuidgid www npm update tiddlywiki && sv t tiddlywiki

COMPLETE Removal

DOMAIN=tiddlywiki.domain.tld
signal-event domain-delete $DOMAIN
db domains delete $DOMAIN
#
SERVICE=tiddlywiki
config delete $SERVICE
find /etc/rc.d -name "*$SERVICE*" -exec 'rm' -f "{}" \;
'rm' -rf /service/$SERVICE
'rm' -rf /var/service/$SERVICE
'rm' -rf /var/log/$SERVICE
#
cd /opt/$SERVICE
npm remove $SERVICE
cd /opt
'rm' -rf /opt/$SERVICE

Notes on check_earlytalker

Why did you remove the Request_for_deletion template on the check_earlytalker page? AFAIK it is obsolete and should be deleted according to http://forums.contribs.org/index.php/topic,46234.msg226418.html#msg226418 - — Cactus (talk | contribs)  07:05, 16 February 2012 (MST)

Here's my understanding of the Request_for_deletion addition to this page:

1) Piran posted a link to this page in a thread with the text "Install the check_earlytalker plugin": http://forums.contribs.org/index.php/topic,46229.msg226377.html#msg226377

2) Charlie noticed Piran's post, and assumed the wiki page described how to install check_earlytalker, so he made his post that the page is obsolete: http://forums.contribs.org/index.php/topic,46234.msg226418.html#msg226418

3) The page was updated with the 'Request_for_deletion' template

4) I added the reasoning to the 'talk' page outlining why the page is NOT obsolete (see below)

5) Over a year later, I removed the 'Request_for_deletion' template, assuming everyone had read and agreed with the reasoning I outlined on the 'talk' page.


Copied from http://wiki.contribs.org/Talk:Qpsmtpd_check_earlytalker - Unless there is more information elsewhere, I don't feel that this page is obsolete.

Despite the language used by piran in his mention of this page at http://forums.contribs.org/index.php/topic,46229.msg226377.html#msg226377, this page is not about adding check_earlytalker - which is included by default as mentioned by Charlie in the forum post referenced above.

This page is about: 

   Documenting the functionality of check_earlytalker (what it does and why it does it)
   Documenting how to change the timeout value applied by check_earlytalker
   Documenting how to monitor check_earlytalker to see if it is being used to deny email
Retrieved from "https://wiki.koozali.org/index.php?title=User_talk:Mmccarn&oldid=34369"