After ensuring the following modules are loaded in the httpd.conf
|
1 2 |
LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so |
The following was added as virtual host:
|
1 2 3 4 5 |
<VirtualHost *:80> ServerName subdomain.myserver.com:80 ProxyPass / http://192.168.0.123:8080/ ProxyPassReverse / http://192.168.0.123:8080/ </VirtualHost> |
Job Done!
After a bit of research I found a product called GateOne that would enable me to use a web browser to connect to ssh using standard https – cool!
|
1 2 3 4 5 6 7 |
sudo apt-get install python-setuptools git clone https://github.com/liftoff/GateOne.git cd GateOne sudo python setup.py install cd .. sudo rm -rf GateOne sudo gateone |
Then ctrl+c so we can edit the config
|
1 |
sudo vi /etc/gateone/conf.d/10server.conf |
at the end of the line with origins, add the IP of the Pi, i.e. , “192.168.0.123” then restart the daemon:
|
1 |
sudo /etc/init.d/gateone restart |
to check it out browse to https://192.168.0.123/
All that remains is to ensure it starts automatically on reboot – I think the update-rc.d script must be a bit buggy on the Pi. I ended up doing all of this as I was having some trial and error fun:
|
1 2 3 4 |
sudo update-rc.d gateone defaults sudo update-rc.d gateone start 20 2 3 4 5 . stop 80 0 1 6 . cd /etc/rc2.d/ sudo mv K01gateone S01gateone |
Next up – some authentication …
within /etc/gateone/conf.d/20authentication.conf the authenication type was changed to google
|
1 |
"auth": "google", |
and the terminal configuration (/etc/gateone/conf.d/50terminal.conf) was modified to turn off the terminal for all users (allow: false) and then add it back on just for me:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
// This is Gate One's Terminal application settings file. { // "*" means "apply to all users" or "default" "*": { "terminal": { // These settings apply to the "terminal" application "commands": {"SSH": {"command": "/usr/local/lib/python2.7/dist-packages/gateone-1.2.0-py2.7.egg/gateone/applications/terminal/plugins/ssh/scripts/ssh_connect.py -S '%SESSION_DIR%/%SESSION%/%SHORT_SOCKET%' --sshfp -a 'oUserKnownHostsFile=\\\"%USERDIR%/%USER%/.ssh/known_hosts\\\"'", "description": "Connect to hosts via SSH."}}, "default_command": "SSH", "dtach": true, "enabled_filetypes": "all", "environment_vars": {"TERM": "xterm-256color"}, "session_logging": true, "syslog_session_logging": false, "allow": false } }, // "*" means "apply to all users" or "default" "user.upn=(my.email@gmail.com)": { "terminal": { // These settings apply to the "terminal" application "commands": {"SSH": {"command": "/usr/local/lib/python2.7/dist-packages/gateone-1.2.0-py2.7.egg/gateone/applications/terminal/plugins/ssh/scripts/ssh_connect.py -S '%SESSION_DIR%/%SESSION%/%SHORT_SOCKET%' --sshfp", "description": "Connect to hosts via SSH."}}, "default_command": "SSH", "dtach": true, "enabled_filetypes": "all", "environment_vars": {"TERM": "xterm-256color"}, "session_logging": true, "syslog_session_logging": false, "allow": true } } } |
Back in /etc/gateone/conf.d/10server.conf I added my external dns to the list of allowed origins and forwarded port 443 on my router to my Pi
Job done!
After downloading the latest wheezy image from the raspberry pi site and flashing it onto the SD card using Win 32 Disk Imager I transferred the card into the Pi and powered it on. To use my approach it must have both the WiFi usb adaptor and an ethernet cable plugged in.
I then go to my router’s admin page and take a look to see what IP address has been allocated to the Pi’s ethernet link.
Then, using Putty, connect to the ssh using the credentials username: pi password: raspberry (all lowercase).
Once on, the following command were run:
|
1 2 3 |
sudo apt-get update sudo apt-get install wicd-curses sudo wicd-curses |
Then navigate down (using the arrow keys) to my home network, then use the right arrow key to go and configure it. The only thing I put in the configuration was the setting to “Automatically connect” and the key to the network – then pressed F10 to save the config, the Q to quit.
Having done all that I shutdown the pi, unplug the ethernet cable and power it back on.
|
1 |
sudo shutdown -h now |
Back in my router’s admin page I can find out the new IP address of the Pi (and reserve it for future if I want).
Job done!
In one of my C# Windows Forms Applications I had a problem whereby a third-party component was throwing an exception in another thread. The exception wasn’t causing any problems but it wasn’t being handled by anything.
Basically I wanted to catch the exception, log it for reference and possible future investigation, and then ignore it and carry on.
I started by adding event handlers to the exception events:
|
1 2 3 |
Application.ThreadException += Application_ThreadException; Application.SetUnhandledExceptionMode(UnhandledExceptionMode.CatchException); AppDomain.CurrentDomain.UnhandledException += CurrentDomain_UnhandledException; |
And then I added log4net to simply log the error and move on (added via NuGet Package Manager)
So my app.config had the following added:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
<configSections> <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler,Log4net"/> </configSections> <log4net> <root> <level value="DEBUG" /> <appender-ref ref="LogFileAppender" /> </root> <appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender" > <param name="File" value="C:\WebRotator\log.txt" /> <param name="AppendToFile" value="true" /> <rollingStyle value="Size" /> <maxSizeRollBackups value="10" /> <maximumFileSize value="1MB" /> <staticLogFileName value="true" /> <layout type="log4net.Layout.PatternLayout"> <param name="ConversionPattern" value="%d{yyyy-MM-dd hh:mm:ss} - %-5p - %m%n" /> </layout> </appender> </log4net> |
And my main Program.cs ended up looking like this:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 |
static class Program { public static readonly ILog Logger = LogManager.GetLogger(typeof(Program)); [STAThread] static void Main() { XmlConfigurator.Configure(); Application.ThreadException += Application_ThreadException; Application.SetUnhandledExceptionMode(UnhandledExceptionMode.CatchException); AppDomain.CurrentDomain.UnhandledException += CurrentDomain_UnhandledException; Application.EnableVisualStyles(); Application.SetCompatibleTextRenderingDefault(false); Application.Run(new frmRotator()); } static void CurrentDomain_UnhandledException(object sender, UnhandledExceptionEventArgs e) { LogException("CurrentDomain_UnhandledException", (Exception)e.ExceptionObject); } static void Application_ThreadException(object sender, ThreadExceptionEventArgs e) { LogException("Application_ThreadException", e.Exception); } private static void LogException(string exceptionArea, Exception e) { Logger.ErrorFormat("{0}: {1}", exceptionArea, e); } } |
Job done!
So I needed to ensure that all sites in my farm were formatting dates in the British format …
Powershell, once again, to the rescue! This is what I ended up with …
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
Add-PSSnapin Microsoft.SharePoint.PowerShell foreach ($app in Get-SPWebApplication) { foreach ($site in $app.Sites) { foreach($web in $site.AllWebs) { Write-Host processing $web in site $site in app $app If ($web.locale -ne 2057) { $web.Locale = 2057; $web.Update(); Write-Host UPDATED $web in site $site in app $app } } } } |
So I had a need to get a csv that could tell me who was in which groups in which sites.
Powershell to the rescue! This is what I ended up with …
There may be a better way to do this but the main thing is that it works and it was quick!
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 |
Add-PSSnapin Microsoft.SharePoint.PowerShell function OutputRow($url, $group, $member) { $out = new-object psobject $out | add-member noteproperty url $url $out | add-member noteproperty group $group $out | add-member noteproperty member $member write-output $out } foreach ($app in Get-SPWebApplication) { foreach ($site in $app.Sites) { OutputRow $site.Url "primary site owner" $site.owner OutputRow $site.Url "secondary site owner" $site.SecondaryContact foreach($web in $site.AllWebs) { if (!$web.HasUniqueRoleDefinitions) { OutputRow $web.Url "Everything Inherited from parent" "" } else { if ($web.RequestAccessEnabled) { OutputRow $web.Url "request access email" $web.RequestAccessEmail } foreach($group in $web.sitegroups) { if ($group.users.Count -eq 0) { OutputRow $web.Url $group.name "Empty Group" } foreach ($user in $group.users) { OutputRow $web.Url $group.name $user.name } } } } } } |
Quite often things break – sometimes I’m able to fix them.
The way I see it is that if it’s broken and is going in the bin then I’ve got nothing to lose by taking it apart and trying to see if it can be fixed.
Most recently I had the external thermometer of a wireless weather station stop working. I was pretty sure some water had got into it so I dried it in the airing cupboard but it still wasn’t responsive. With nothing to lose I took it apart, saw that there was a fair amount of corrosion on the circuit board and almost gave up. Just on the off-chance that the components were still ok and the corrosion was causing a short I got an old toothbrush and cleaned it up.
Miraculously this worked and I’ve saved £35 on a replacement. Result!
So because it’s on a server there is no working directory required – as a result we do a bare initialise in the folder that we want the repo to be in:
|
1 |
git init --bare |
After that, to allow pushes to the server over http we need to run the following:
|
1 |
git config --file config http.receivepack true |
This will then work nicely with a virtual host in apache:
|
1 2 3 4 5 6 7 8 9 |
<VirtualHost *:80> ServerName git.server.com DocumentRoot /path/to/my/git/ SetEnv GIT_PROJECT_ROOT /path/to/my/git/ SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias / /usr/libexec/git-core/git-http-backend/ </VirtualHost> |
Also, make sure the user running apache has write permissions to the git repository folders.
Authentication
To add some basic authentication I have used the following 2 techniques:
To make an entire repository private:
|
1 2 3 4 5 6 |
<Location "/private/"> AuthType Basic AuthName "Password Required" AuthUserFile /path/to/my/conf/passwd Require user username </Location> |
To make all repositories public for read and private for write:
|
1 2 3 4 5 6 7 8 |
<LocationMatch "^/.*/git-receive-pack$"> Options +ExecCGI AuthType Basic AuthName "Git Access" AuthName "Password Required" AuthUserFile /path/to/my/conf/passwd Require user username </LocationMatch> |
Web UI
Finally, I have used gitlist to provide a web ui to my repositories – to achieve this I used the standard approach documented here
My final config looks like this:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 |
<VirtualHost *:80> <Location "/private/"> AuthType Basic AuthName "Password Required" AuthUserFile /path/to/my/conf/passwd Require user username </Location> <LocationMatch "^/.*/git-receive-pack$"> Options +ExecCGI AuthType Basic AuthName "Git Access" AuthName "Password Required" AuthUserFile /path/to/my/conf/passwd Require user username </LocationMatch> ServerName git.server.com DocumentRoot /path/to/my/www/gitlist/ SetEnv GIT_PROJECT_ROOT /path/to/my/git/ SetEnv GIT_HTTP_EXPORT_ALL ScriptAliasMatch \ "(?x)^/(.*/(HEAD | \ info/refs | \ objects/(info/[^/]+ | \ [0-9a-f]{2}/[0-9a-f]{38} | \ pack/pack-[0-9a-f]{40}\.(pack|idx)) | \ git-(upload|receive)-pack))$" \ /usr/libexec/git-core/git-http-backend/$1 </VirtualHost> |
So I’m starting a blog – we’ll see how long that lasts!
The main types of article I intend to write are:
The main types of article I intend to avoid writing are:
I contemplated having separate blogs for each of the topics that I end up writing about but then I realised it was just too much overhead – I’m a whole person and this blog is for me. Furthermore, I will be using the categories you will see at the right of every page to vigilantly categorise each post – so if you only want my posts about SharePoint there will be a category that niftily filters the posts and shows you only the ones that you’re interested in.
So, finally, erm … Welcome!