| #!/usr/bin/bash -xe | |
| cat <<EOF > "${HOME}/.config/systemd/user/zoom.slice" | |
| [Slice] | |
| AllowedCPUs=0-4 | |
| MemoryHigh=6G | |
| EOF | |
| cat /usr/share/applications/Zoom.desktop | sed -E 's#^(Exec=).*$#Exec=/usr/bin/systemd-run --user --slice=zoom.slice /opt/zoom/ZoomLauncher#' > "${HOME}/.local/share/applications/Zoom.desktop" |
| #!/bin/bash | |
| #source .bashrc | |
| cd /turnkey/fab/products/$1 | |
| echo In products/$1 | |
| echo Current Build $2 | |
| export FAB_PATH=/turnkey/fab | |
| export FAB_APT_PROXY=http://127.0.0.1:8124 |
This guide/log is based off my experience attempting to build and install LibreOffice Online and it's dependencies on my system.
The end goal is to get LibreOffice Online integrated with Karoshi Server.
LibreOffice Online is still in development (17/06/16).
I’ll assume you are on Linux or Mac OSX. For Windows, replace ~/.vim/ with $HOME\vimfiles\ and forward slashes with backward slashes.
Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your ~/.vim/ directory. Syntax scripts go into ~/.vim/syntax/, plugin scripts go into ~/.vim/plugin, documentation goes into ~/.vim/doc/ and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.
This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under ~/.vim/bundle/, where each directory simulates the standard structure of your ~/.vim/ directory.
| Options +FollowSymLinks +ExecCGI | |
| <IfModule mod_rewrite.c> | |
| RewriteEngine On | |
| RewriteRule (.*)\.(?:md|markdown)$ /utilities/md2html.php?file=%{REQUEST_FILENAME} [QSA,L] | |
| RewriteRule (.*)\.(?:rst)$ /utilities/rst2html.php?file=%{REQUEST_FILENAME} [QSA,L] | |
| </IfModule> |
