The Workshopper Remote Verification API is a simple API that allows clients to provide solutions for Workshopper problems to remote websites, and potentially receive [Open Badges][] in response.
The remote website can implement its own verification policies. For instance, a site that trusts its users can simply accept solutions without question, or it can actually execute the code in a sandbox, or it can queue the solution for review by a human.
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
| ZIP,LAT,LNG | |
| 00601,18.180555, -66.749961 | |
| 00602,18.361945, -67.175597 | |
| 00603,18.455183, -67.119887 | |
| 00606,18.158345, -66.932911 | |
| 00610,18.295366, -67.125135 | |
| 00612,18.402253, -66.711397 | |
| 00616,18.420412, -66.671979 | |
| 00617,18.445147, -66.559696 | |
| 00622,17.991245, -67.153993 |
Install cask that extends the brew command :
brew install phinze/cask/brew-cask
Install calibre using cask :
brew cask install calibre
| var download = require('./lib/download'); | |
| download('http://meuarquivolocodedoido.com.br/arquivo.txt', './downloads') | |
| .then(function(id){ | |
| console.log('Arquivo gravado com id %s', id); | |
| }) | |
| .catch(function(err){ | |
| console.log('Deu pau..'); | |
| console.log(err.stack); | |
| }); |
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
| #!/bin/bash | |
| # | |
| # Using the information available in the new iOS8 simulator for each | |
| # device/runtime (device.plist), this script creates a readable folder structure | |
| # (no UDIDs, just simple device/runtime names). Inside that structure it creates | |
| # soft links to your apps in development. | |
| # | |
| # You can run this script every time you install an app to your simulator, or | |
| # you can simply call it to access this folder making sure it will always be | |
| # updated :) |
| <!-- note the ONLY change to this is the additional module="tabIndicator" | |
| attribute + properties to override indicator defaults //--> | |
| <Alloy> | |
| <TabGroup module="tabIndicator" tabsBackgroundColor="#000" tabIndicatorHeight="1" tabIndicatorColor="white" tabIndicatorWidth="75%"> | |
| <Tab title="Tab 1" icon="/images/icons/519-tools-1.png" activeIcon="/images/icons/519-tools-1_active.png" color="#555" activeColor="#fff"> | |
| <Window title="Tab 1" barColor="black" navTextColor = "#fff"> | |
| <Label onClick="openWin1">Tab 1</Label> | |
| </Window> | |
| </Tab> | |
| <Tab title="Tab 2" icon="/images/icons/516-archive-box.png" activeIcon="/images/icons/516-archive-box_active.png" color="#555" activeColor="#fff"> |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>Credit Card Form</title> | |
| <style> | |
| .forAppleCardScan { | |
| width: 1px; | |
| height: 1px; | |
| margin-left: -1000px; |
