Here's a quick guide how to run SpaceEngineers Dedicated Server on Ubuntu with Wine
- A copy of Space Engineers
- A Windows box
- A Linux box running Ubuntu 14.04 or 14.10 (It'll probably work on other distros, YMMV)
| "use strict"; | |
| var stackTrace = (new Error()).stack; // Only tested in latest FF and Chrome | |
| var callerName = stackTrace.replace(/^Error\s+/, ''); // Sanitize Chrome | |
| callerName = callerName.split("\n")[1]; // 1st item is this, 2nd item is caller | |
| callerName = callerName.replace(/^\s+at Object./, ''); // Sanitize Chrome | |
| callerName = callerName.replace(/ \(.+\)$/, ''); // Sanitize Chrome | |
| callerName = callerName.replace(/\@.+/, ''); // Sanitize Firefox | |
| console.log(callerName) |
| // Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/ | |
| // See also: http://www.paulund.co.uk/change-url-of-git-repository | |
| $ cd $HOME/Code/repo-directory | |
| $ git remote rename origin bitbucket | |
| $ git remote add origin https://github.com/mandiwise/awesome-new-repo.git | |
| $ git push origin master | |
| $ git remote rm bitbucket |
Here's a quick guide how to run SpaceEngineers Dedicated Server on Ubuntu with Wine
You can trigger a GitHub Pages (Jekyll) rebuild with a single API call. This is pretty useful for auto-publishing blog posts from a bot like Zapier in conjunction with future: false in your Jekyll config.yml. Just future-date your posts, and they'll go live when that date rolls around. I use a version of this setup for my blog at greghaskins.com.
Create a GitHub personal access token and save it somewhere. It needs to have the repo access scope (at least).
Create a file at the root of your repo (e.g. .publish) with some dummy content.
$ echo ".publish" > .publish
http://adventuresinxamarinforms.com/2015/03/17/xaml-v-code/
add (to each xaml file, near the top with the other xmlns definitions)
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d"
curl to get the JSON response for the latest releasegrep to find the line containing file URLcut and tr to extract the URLwget to download itcurl -s https://api.github.com/repos/jgm/pandoc/releases/latest \
| grep "browser_download_url.*deb" \
| cut -d : -f 2,3 \
| tr -d \" \| curl --include \ | |
| --no-buffer \ | |
| --header "Connection: Upgrade" \ | |
| --header "Upgrade: websocket" \ | |
| --header "Host: example.com:80" \ | |
| --header "Origin: http://example.com:80" \ | |
| --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" \ | |
| --header "Sec-WebSocket-Version: 13" \ | |
| http://example.com:80/ |
Hello, brethren :-)
As it turns out, the current version of FFmpeg (version 3.1 released earlier today) and libav (master branch) supports full H.264 and HEVC encode in VAAPI on supported hardware that works reliably well to be termed "production-ready".