Use websockets for reporting server uptime, where the panel acts as a "client" and the main monitor instance acts as a "server". A websocket connection is made between the two, in affect allowing real time statistics to flow through from "client server" to "master server" to "client" on the web front end and keeping accurate stats cached in cases of disabled JavaScript or API calls.
requests
| # | |
| # Overwatch Competitive Rank Point Algorithm ^TM ^^Copyright ^^^etc. | |
| # Written by Gabriel Simmer, December 2016 | |
| # Feel free to use this script in your own | |
| # projects, just make sure to provide some attribution | |
| # back to either this gist or my GitHub. <3 | |
| # | |
| def Calculate(time, points, deaths, elims, wins, lost): |
| server { | |
| listen 80; | |
| server_name hostname.com; | |
| location / { | |
| proxy_pass http://127.0.0.1:8080$request_uri; | |
| proxy_set_header Host $host; | |
| } |
mc7.ggservers.com
mc20.ggservers.com
mc38.ggservers.com
mc47.ggservers.com
mc49.ggservers.com
| /* | |
| * Basic FizzBuzz excersize in Golang | |
| */ | |
| package main | |
| import ( | |
| "fmt" | |
| ) |
| +// Converts ajax POST to JavaScript object | |
| +var BodyToObject = function(body) { | |
| + var res = new Object; | |
| + body = body.split("&"); // param1=X,param2=X | |
| + console.log(body); | |
| + for (var i = body.length - 1; i >= 0; i--) { | |
| + var vals = body[i].split("="); // param2,X,param1,X | |
| + for (var k = vals.length - 2; k >= 0; k--) { | |
| + res[vals[k]] = vals[k + 1] // *hopefully* {param1:X,param2:X} | |
| + } |
I hereby claim:
To claim this, I am signing this object:
The goal of this stack shift is to save money while still providing the same writing convienience to authors and performance/readability/etc. for readers. It is imperitive that the transition happens seamlessly, with no downtime for readers, and that all authors are familiar with the process of publishing. We currently operate at a 100% loss, managing our own servers running Ghost and Mail-in-a-box on DigitalOcean hardware.
Currently, there are two options I am actively considering. The first is a publication on Medium, a popular blogging platform. Publications are "a way to group stories together by many writers or by one writer around a common theme or topic" (via Medium). The interface of Medium is minimalistic and attractive, and is extremely easy to use with their rich(ish) text editor and social media logins. It's fairly performant, and supports several features for building communities, e.g following, claps (likes). However there are a few downides - primaril
| # coding: utf8 | |
| """ | |
| This script helps to import content from a Ghost blog database to Jekyll. | |
| The database is expected to be running on a reachalbe MySQL host. | |
| See the very end for DB configuration. | |
| Quick Usage: | |
| pip install -r requirements |
| [8;30;100tUsing a linux flavor or etc. | |
| Using: /mnt/c/Users/gabriel/Documents/Projects/rrpg-cmd | |
| Engine: /mnt/c/Users/gabriel/Documents/Projects/rrpg-cmd/engine | |
| Config: /mnt/c/Users/gabriel/Documents/Projects/rrpg-cmd/config | |
| Mods: /mnt/c/Users/gabriel/Documents/Projects/rrpg-cmd/mod | |
| [3;J[H[2J[modloader] Preloading Functions (mod_aload.bash)...OK | |
| Loading mod_cecho...OK | |
| Loading mod_cfg...OK | |
| Loading mod_Content-Parser...OK | |
| Loading mod_dos2unix...ERR:WRONG_OS |