zii/MRCI
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4d47fd187f
MRCI/linux_build.sh

148 lines
5.2 KiB
Bash
Raw Normal View History

Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
#!/bin/sh
qt_dir="$1"
installer_file="$2"
src_dir="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
bin_name="mrci"
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
app_version="2.1.3"
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
app_name="MRCI"
install_dir="/opt/$bin_name"
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
var_dir="/var/opt/$bin_name"
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
bin_dir="/usr/bin"
tmp_dir="$HOME/.cache/mrci_build"
Minor changes to the linux build script $qt_dir in the build script will now default to the hard coded standard directory for Qt binaries '/usr/lib/x86_64-linux-gnu/qt5/bin' if a valid path is not provided by the user. End users that have customized setups of Qt might need to modify this script to make sure $qt_dir points to the correct directory at all times. Moved the LICENSE.md file to the root directory so github can read it.
2019-09-19 13:07:50 -04:00
if [ ! -d "$qt_dir" ]; then
echo "a valid path to Qt was not provided, falling back to the default: /usr/lib/x86_64-linux-gnu/qt5/bin"
qt_dir="/usr/lib/x86_64-linux-gnu/qt5/bin"
else
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
PATH=$qt_dir:$PATH
fi
if [ "$installer_file" = "" ]; then
installer_file="$src_dir/$bin_name-$app_version.run"
fi
if [ -d "$tmp_dir" ]; then
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
rm -rf $tmp_dir
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
fi
Minor changes to the linux build script $qt_dir in the build script will now default to the hard coded standard directory for Qt binaries '/usr/lib/x86_64-linux-gnu/qt5/bin' if a valid path is not provided by the user. End users that have customized setups of Qt might need to modify this script to make sure $qt_dir points to the correct directory at all times. Moved the LICENSE.md file to the root directory so github can read it.
2019-09-19 13:07:50 -04:00
if [ $? -eq 0 -a -d "$qt_dir" ]; then
mkdir -vp $tmp_dir
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
cp -r $src_dir/. $tmp_dir
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
cd $tmp_dir
qmake -config release
if [ $? -eq 0 ]; then
make
if [ $? -eq 0 ]; then
mkdir -v ./build/
mkdir -v ./build/sqldrivers
mkdir -v ./build/lib
Major bug fixes and a few minor changes Fixed a bug that caused the host to not respond to any commands when a module is present. CmdExecutor::loadMods() had a malformed 'for' loop that caused the command executor to infinite loop. Also re-formed the way the external command loaders (modules) are constructed. Instead, the modules are also intialized at the same time as the internal command loader. The CmdExecutor::loadModFile() and CmdExecutor::unloadModFile() functions now load and unload modules via the module name instead of the path to the module main file. The documentation for ASYNC_ENABLE_MOD and ASYNC_DISABLE_MOD updated to reflect this change. Also part of the module contruction re-form, it fixed a bug that caused the command loaders to operate in a thread different from the command executor. CmdExecutor::loadMods() was refactored into cmdExecutor::buildCmdLoaders(), added the internal command loader to it and have it so this function gets called only when the command executor successfully moves to it's own thread. Fixed a bug that caused the session to crash only when a module is present. It turns out the qobject_cast() function used in CmdExecutor::loadModFile() only pulled the surface class ModCommandLoader so any attempt to access the base class functions from CommandLoader caused the session to crash so to fix this, ModCommandLoader was merged into CommandLoader. The Command loader documentation and test module were updated to reflect this change. Fixed a bug that auto removed any modules that were installed when the host is restarted. The issue was in TCPServer::syncModPath() that used the modules's main file without a suffix when the file did indeed have a suffix, causing the function to think the module no longer exists and remove all of it's files from the host file system. The original intent for this function was to keep the module database table in sync with what was actually in the host file system. It was decided that this is not necessary so the function was removed altogether. Also changed up the way the module files are deleted. The TCPSever class will now use the module name instead of the path to the module's main library file and will use a single use ModDeleteTimer for each module that was requested to be deleted instead of a single continuous timer constantly checking for modules to delete. The ls_cmds command will now list the commands in alphabetical order of the command names and fixed a bug with the -find option that would display nothing if an exact match to any text in the table could not be found. Fixed a bug found in the deployed application that would segmentation fault on startup due to certain library files being included in the deployed installation directory. Updated the linux_build.sh script to include only libsqlite, libQT5, libssl and libicu files. It will no longer blindly copy all library files from the dev machine and then remove files the setup script thinks the application might or might not need. Any module built on import rev1 will simply not work and no attempt will be made to make it work so the host new minimum import rev is now rev2. this update is mustly just bug fixes; nothing that would require any client behaviour changes so just the host patch is bumped. 1.0.0 --> 1.0.1
2019-09-12 01:29:46 -04:00
ldd ./$bin_name | grep "libQt" | awk '{print $3}' | xargs -I '{}' cp -v '{}' ./build/lib
ldd ./$bin_name | grep "libicu" | awk '{print $3}' | xargs -I '{}' cp -v '{}' ./build/lib
ldd ./$bin_name | grep "libssl" | awk '{print $3}' | xargs -I '{}' cp -v '{}' ./build/lib
ldd ./$bin_name | grep "libcrypto" | awk '{print $3}' | xargs -I '{}' cp -v '{}' ./build/lib
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
mv -v ./$bin_name ./build/$bin_name
cp -v $qt_dir/../plugins/sqldrivers/libqsqlite.so ./build/sqldrivers
startup_script="./build/$bin_name.sh"
setup_script="./build/setup.sh"
uninstall_script="./build/uninstall.sh"
service_file="./build/$bin_name.service"
echo "#!/bin/sh" > $startup_script
Minor changes to the linux build script $qt_dir in the build script will now default to the hard coded standard directory for Qt binaries '/usr/lib/x86_64-linux-gnu/qt5/bin' if a valid path is not provided by the user. End users that have customized setups of Qt might need to modify this script to make sure $qt_dir points to the correct directory at all times. Moved the LICENSE.md file to the root directory so github can read it.
2019-09-19 13:07:50 -04:00
echo "export QTDIR=$install_dir" >> $startup_script
echo "export QT_PLUGIN_PATH=$install_dir" >> $startup_script
echo "export LD_LIBRARY_PATH=\"$install_dir/lib:\$LD_LIBRARY_PATH\"" >> $startup_script
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
echo "export MRCI_DB_PATH=$var_dir/data.db" >> $startup_script
Minor changes to the linux build script $qt_dir in the build script will now default to the hard coded standard directory for Qt binaries '/usr/lib/x86_64-linux-gnu/qt5/bin' if a valid path is not provided by the user. End users that have customized setups of Qt might need to modify this script to make sure $qt_dir points to the correct directory at all times. Moved the LICENSE.md file to the root directory so github can read it.
2019-09-19 13:07:50 -04:00
echo "$install_dir/$bin_name \$1 \$2 \$3" >> $startup_script
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
echo "#!/bin/sh" > $setup_script
echo "if [ -f \"$install_dir/uninstall.sh\" ]; then" >> $setup_script
echo " sh $install_dir/uninstall.sh" >> $setup_script
echo "fi" >> $setup_script
echo "if [ ! -d \"$install_dir\" ]; then" >> $setup_script
echo " sudo mkdir -p $install_dir" >> $setup_script
echo "fi" >> $setup_script
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
echo "if [ ! -d \"$var_dir\" ]; then" >> $setup_script
echo " sudo mkdir -p $var_dir" >> $setup_script
echo "fi" >> $setup_script
echo "cp -rfv ./lib $install_dir" >> $setup_script
echo "cp -rfv ./sqldrivers $install_dir" >> $setup_script
echo "cp -fv ./$bin_name $install_dir" >> $setup_script
echo "cp -fv ./$bin_name.sh $install_dir" >> $setup_script
echo "cp -fv ./uninstall.sh $install_dir" >> $setup_script
echo "cp -fv ./$bin_name.service /etc/systemd/system/$bin_name.service" >> $setup_script
echo "useradd -r $bin_name" >> $setup_script
echo "chmod 755 $install_dir/$bin_name" >> $setup_script
echo "chmod 755 $install_dir/$bin_name.sh" >> $setup_script
echo "chmod 755 $install_dir/uninstall.sh" >> $setup_script
echo "chmod 755 $install_dir" >> $setup_script
echo "chmod -R 755 $install_dir/lib" >> $setup_script
echo "chmod -R 755 $install_dir/sqldrivers" >> $setup_script
echo "chmod 755 /etc/systemd/system/$bin_name.service" >> $setup_script
echo "chown -R $bin_name:$bin_name $var_dir" >> $setup_script
echo "chmod -R 755 $var_dir" >> $setup_script
echo "ln -sf $install_dir/$bin_name.sh $bin_dir/$bin_name" >> $setup_script
echo "systemctl start $bin_name" >> $setup_script
echo "systemctl enable $bin_name" >> $setup_script
echo "if [ \$? -eq 0 ]; then" >> $setup_script
echo " echo \"\nInstallation finished. If you ever need to uninstall this application, run this command:\n\"" >> $setup_script
echo " echo \" $install_dir/uninstall.sh\n\"" >> $setup_script
echo "fi" >> $setup_script
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
echo "[Unit]" > $service_file
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
echo "Description=$app_name Host Daemon" >> $service_file
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
echo "After=network.target" >> $service_file
echo "" >> $service_file
echo "[Service]" >> $service_file
echo "Type=simple" >> $service_file
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
echo "User=$bin_name" >> $service_file
echo "Restart=on-failure" >> $service_file
echo "RestartSec=5" >> $service_file
echo "TimeoutStopSec=infinity" >> $service_file
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
echo "ExecStart=/usr/bin/env $bin_name -host" >> $service_file
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
echo "ExecStop=/usr/bin/env $bin_name -stop" >> $service_file
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
echo "" >> $service_file
echo "[Install]" >> $service_file
echo "WantedBy=multi-user.target" >> $service_file
echo "#!/bin/sh" > $uninstall_script
Installation structor updates changed the default installattion used in the linux_build.sh script to create an installer that deauly installs the application data files in the /var fold folder instead of the user specific folder in /home. also made it so it will now create a system user named after the name of the application and use that user to run the systemd service instead of the currently logged in user. doing this harded system security by having the application run as an under privileged user. this also opens up the possibility to lock down direct writing access to the host database to just the internal module (in a future update). removed the -start command line argument and have just the -host option to start new host instances. the -start option would start the host as the current user so i decided to remove it as a way to encourage end users to start/stop the host via systemd.
2019-12-24 15:51:10 -05:00
echo "systemctl -q stop $bin_name" >> $uninstall_script
echo "systemctl -q disable $bin_name" >> $uninstall_script
echo "rm -v /etc/systemd/system/$bin_name.service" >> $uninstall_script
echo "rm -v $bin_dir/$bin_name" >> $uninstall_script
echo "rm -rv $install_dir" >> $uninstall_script
echo "chown -R root:root $var_dir" >> $uninstall_script
echo "deluser $bin_name" >> $uninstall_script
Initial commit for the MRCI project.
2019-09-06 23:43:07 -04:00
chmod +x $setup_script
makeself ./build $installer_file "$app_name Installation" ./setup.sh
fi
fi
fi
if [ -d "$tmp_dir" ]; then
rm -rf $tmp_dir
fi
Reference in New Issue Copy Permalink