688
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 1:
Line 1: − + − + − + − #####################################################################################+ − # BEGIN+ − #####################################################################################+ − # yum repos aren't useful; use the side-by-side install+ − # Install mariadb side-by-side with mysql on SME Server v8+ − # From: https://mariadb.com/kb/en/installing-mariadb-alongside-mysql/+ − #+ − # create user 'mariadb' in server-manager+ − #+ − cd ~+ − mkdir -p addons+ − cd addons+ − RELEASE=5.5.34+ − 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+ − cd /opt+ − tar zxvf ~/addons/mariadb-$RELEASE-linux-i686.tar.gz+ − ln -s mariadb-$RELEASE-linux-i686 mariadb+ − mkdir mariadb-data+ − cp mariadb/support-files/my-medium.cnf mariadb-data/my.cnf+ − #+ − # edit my.cnf as described on the mariadb-alongside-mysql howto (link above)+ − chown -R mariadb:mariadb mariadb-data mariadb mariadb-$RELEASE-linux-i686+ − #+ − cp mariadb/support-files/mysql.server /etc/init.d/mariadb+ − chmod +x /etc/init.d/mariadb+ − #+ − # 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 − ====Backup & Restore====+ − * (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 ?+ − + − * 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)+ − then+ − echo "mariadb is not running - no tables dumped" >&2 + − exit 0+ − fi+ + + − mkdir -p /home/e-smith/db/mariadb+ − for db in $(mysql $CONNECT -BNre "show databases;")+ − do+ − mysqldump $CONNECT -x --add-drop-table -QB "$db" -r /home/e-smith/db/mariadb/"$db".dump || exit 1+ − done</nowiki>+ − =====/etc/e-smith/events/actions/mariadb-load-tables=====+ − * 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)+ − then + − echo "mariadb is not running - no tables restored" >&2 − exit 0 − fi − if [ ! -f $MARIADATA/mysql/user.frm ]+ − then+ − 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=== − ====Requirements==== Line 127:
Line 78: − =====DB Version=====+ − =====OPcache=====+ Line 137:
Line 88: − ====Installation====+ − =====Prepare your server=====+ − ======Create an ibay======+ Line 161:
Line 112: − ======Create a database======+ − + − + − + + + − + Line 182:
Line 135: − =====Install Moodle=====+ − ======Download & Checkout using git======+ Line 191:
Line 144: − + Line 201:
Line 154: − ======Run the installer======+ + − + Line 211:
Line 165: − ======Correct database settings if necessary======+ + Line 218:
Line 173: − + − + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − ===Notes on check_earlytalker===+
update time stamp
===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 \
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</nowiki>
===Agent Configuration===
[https://documentation.wazuh.com/current/installation-guide/installing-wazuh-agent/wazuh_agent_rpm.html 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:
<nowiki>...
<client>
<server>
<address>MANAGER_IP</address>
</server>
<config-profile>rhel, rhel6</config-profile>
</client>
...
</nowiki>
</nowiki>
Start the agent
/etc/init.d/wazuh-agent start
=====/etc/e-smith/events/actions/mariadb-dump-tables=====
===SME Customizations===
I added these instructions to /var/ossec/etc/ossec.conf:
<nowiki> <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>
</nowiki>
And this instruction to /var/ossec/etc/local_internal_options.conf:
<nowiki># 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
</nowiki>
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)
* 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)
* Moodle upgrade: Moodle 2.2 or later (if upgrading from earlier versions, you must upgrade to 2.2.11 as a first step)
* New recommended PHP extensions: <span style="color:green">zlib</span>, <span style="color:red;">OPcache</span>
* New recommended PHP extensions: <span style="color:green">zlib</span>, <span style="color:red;">OPcache</span>
====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.
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.
Zend OPcache is built-in to PHP 5.5, and can be compiled to work with PHP 5.3.3.
I believe this will make Moodle run more slowly than it would *with* OPcache.
I believe this will make Moodle run more slowly than it would *with* OPcache.
===Installation===
====Prepare your server====
======Install useful php modules======
======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:
* 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
yum install php-soap php-xmlrpc php-intl
=====Create an ibay=====
* Create an ibay named 'moodle' in server-manager
* Create an ibay named 'moodle' in server-manager
* Customize some of the settings on the new moodle ibay
* Customize some of the settings on the new moodle ibay
#</nowiki>
#</nowiki>
=====Create a database=====
* Install Mariadb ''alongside'' mysql
* Install Mariadb ''alongside'' mysql
* create a mariadb database for moodle
* create a mariadb database for moodle
<nowiki># Generate a random 23 character password
<nowiki># Generate a random 23 character password
DBPASS=`< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c23`
DBPASS=`< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c23`
DBNAME=xmoodle
DBNAME=moodle
DBUSER=xmoodle
DBUSER=moodle
CONNECT=--socket=/opt/mariadb-data/mariadb.sock
CONNECT=--socket=/opt/mariadb-data/mariadb.sock
#
#
echo Creating Database using: ; \
echo ;\
echo ;\
echo Creating Database using: ;\
echo DBNAME=$DBNAME ;\
echo DBNAME=$DBNAME ;\
echo DBUSER=$DBUSER ;\
echo DBUSER=$DBUSER ;\
echo DBPASS=$DBPASS ;\
echo DBPASS=$DBPASS ;\
echo ;\
echo ;\
echo Save this information. You will need it later during initial application setup! (press \<enter\> when done) ;\
echo Save this information! You will need it later during initial application setup! \(press \<enter\> when ready\) ;\
read
read
#
#
quit"</nowiki>
quit"</nowiki>
====Install Moodle====
=====Download & Checkout using git=====
<nowiki>
<nowiki>
#
#
IBAY=moodle
IBAY=moodle
cd /home/e-smith/files/ibays/$IBAY
cd /home/e-smith/files/ibays/$IBAY
mv html html.org
mv html html.`date +%F-%H%M%S`
git clone git://git.moodle.org/moodle.git html
git clone git://git.moodle.org/moodle.git html
cd html
cd html
signal-event ibay-modify $IBAY
signal-event ibay-modify $IBAY
</nowiki>
</nowiki>
=====Run the moodle installer=====
<nowiki>#
<nowiki>#
# run the command line installer
# run the moodle command line installer
# if prompted, set:
# if prompted, set:
# mysql port: 3307
# mysql port: 3307
sudo -u www /usr/bin/php install.php
sudo -u www /usr/bin/php install.php
</nowiki>
</nowiki>
=====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.
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.
If you have just run the above database connection commands in the same putty session, you can correct your moodle settings using:
If you have just run the above database connection commands in the same putty session, you can correct your moodle settings using:
<nowiki>sed -i s/dbname.*/dbname\ \ \ \ \=\ \'$DBNAME\'\;/ /home/e-smith/files/ibays/moodle/html/config.php
<nowiki>IBAY=moodle
sed -i s/dbuser.*/dbuser\ \ \ \ \=\ \'$DBUSER\'\;/ /home/e-smith/files/ibays/moodle/html/config.php
sed -i s/dbname.*/dbname\ \ \ \ \=\ \'$DBNAME\'\;/ /home/e-smith/files/ibays/$IBAY/html/config.php
sed -i s/dbpass.*/dbpass\ \ \ \ \=\ \'$DBPASS\'\;/ /home/e-smith/files/ibays/moodle/html/config.php</nowiki>
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</nowiki>
====Optional Settings====
=====Scan Uploads using ClamAV=====
Moodle can be configured to scan all user files when uploaded.
<nowiki>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"</nowiki>
=====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==
[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==
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 - <small>— [[User:Cactus|Cactus]] ([[User talk:Cactus|talk]] | [[Special:Contributions/Cactus|contribs]]) </small> 07:05, 16 February 2012 (MST)
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 - <small>— [[User:Cactus|Cactus]] ([[User talk:Cactus|talk]] | [[Special:Contributions/Cactus|contribs]]) </small> 07:05, 16 February 2012 (MST)
