Showing posts with label computers. Show all posts
Showing posts with label computers. Show all posts
Sunday, December 13, 2015
nginx local proxy
I wanted just a simple nginx setup to forward to a local app. Here's the result:
http {
...
server {
server_name 52.62.72.255;
#access_log /var/log/nginx/histories.log;
location / {
proxy_pass http://127.0.0.1:3000;
}
}
For some reason it was hard to find this info! I had to pull it from one of my other servers. But one good example is this reference: http://wiki.nginx.org/FullExample
Wednesday, March 28, 2012
Make:SLC
In the East half of Make:SLC is the home of the Computer Graphics Museum. (I believe it was Richard Thomson I met.) He highly recommended seeing the Exploratorium in San Francisco.
Scott Lemon came to show off his enclosing for Arduino and other electronics. Other things he mentioned: Patchbase, Thingspeak, X10 for home automation
Friday, May 20, 2011
Today's SLC Tech Breakfast
From today's SLC Tech Breakfast:
Staying secure with guns; Dan recommends TheBoxOTruth.com for gun education
passwords and sharing
- SpiderOak (Makani doesn't recommend for UI)
- LastPass.com (password sharing)
- locking password file: KeePassX, OnePassword, LastPass
For security, Dan wants a hand-held retina-scanner (not a hand-held-retina scanner)
Quantum entanglement, Dan will look up whether a recent experiment that supposedly allowed faster-than-light communication
Sharing code from different languages
- one way is to use JVM-based languages that can be compile-time checked (Josh)
- in C# shop, wants to use Java tool (Flying Saucer) to convert documents, used IKVM.net, also see JNBridge.com (Dan)
- make web-services the architectural organization (Josh)... that's how we organize in FLUX networking (Ryan)
Enterprise security: we share an encrypted DB (KeePassX), but if an employee leaves...?
The best solution is an OAuth-style, revokable auth
OAuth is recommended for phones, too... including web auth (Josh)
How good are your unit tests? (Dan)
- We have over 10% coverage with Sonar (Josh)
- Continuous build: Hudson, Cruise Control
How do we manage DB versioning? (Dan)
- custom system, which builds at any version (Makani)
- each DB change represented by create SQL and hopefully reverse SQL, table with version number in DB (Josh & Makani)
- potentially: make each change a non-breaking change with previous version, so code roll-back is easy, eg. rename is add followed by drop later (Makani)
"No fluff just stuff" conference downtown SLC (Josh)
Jsconf JavaScript conferences
Defrag conference in Denver (Trent)
Javascript libraries: Require, Promise interface, dojo for apps (Josh)
Staying secure with guns; Dan recommends TheBoxOTruth.com for gun education
passwords and sharing
- SpiderOak (Makani doesn't recommend for UI)
- LastPass.com (password sharing)
- locking password file: KeePassX, OnePassword, LastPass
For security, Dan wants a hand-held retina-scanner (not a hand-held-retina scanner)
Quantum entanglement, Dan will look up whether a recent experiment that supposedly allowed faster-than-light communication
Sharing code from different languages
- one way is to use JVM-based languages that can be compile-time checked (Josh)
- in C# shop, wants to use Java tool (Flying Saucer) to convert documents, used IKVM.net, also see JNBridge.com (Dan)
- make web-services the architectural organization (Josh)... that's how we organize in FLUX networking (Ryan)
Enterprise security: we share an encrypted DB (KeePassX), but if an employee leaves...?
The best solution is an OAuth-style, revokable auth
OAuth is recommended for phones, too... including web auth (Josh)
How good are your unit tests? (Dan)
- We have over 10% coverage with Sonar (Josh)
- Continuous build: Hudson, Cruise Control
How do we manage DB versioning? (Dan)
- custom system, which builds at any version (Makani)
- each DB change represented by create SQL and hopefully reverse SQL, table with version number in DB (Josh & Makani)
- potentially: make each change a non-breaking change with previous version, so code roll-back is easy, eg. rename is add followed by drop later (Makani)
"No fluff just stuff" conference downtown SLC (Josh)
Jsconf JavaScript conferences
Defrag conference in Denver (Trent)
Javascript libraries: Require, Promise interface, dojo for apps (Josh)
Thursday, October 15, 2009
Java Tutorial for Absolute Beginners
(I want to give programming newbies an introduction to Java, but in a way that they can do it independently such that the tools won't get in the way (eg. 'javac' to compile, 'java' to run, avoiding classpath issues, and so on). I think the best fit is to have them use Eclipse (or another Java IDE), which will allow them to get to the code quickly; hopefully the IDE won't distract them. Unfortunately, I cannot find any existing tutorials that fit the bill, so here's a set of instructions that I hope will work better.)
- Complete steps 1-4 of the Eclipse Java IDE tutorial. I assume you will be able to find and install Java and Eclipse (which are installed separately); when you choose a Java or Eclipse download, just choose a "Java" version... there's no need for anything fancy like "Java EE".
- Jump into "Part 2: The Syntax" of Brewing Java: A Tutorial, but stop when you get to "Command Line Arguments".
- In Eclipse, try to run the "Command Line Arguments" example, but realize that you'll get an error.
In order to supply run-time data to your program, you'll have to add an argument to run it: right-click on your program and select "Run As...", but then instead of "Java Application" choose "Run...", then click on the "Arguments" tab and fill in something (like your name) and click "Apply".
Now "Run" your program and you should get some good output. - Now you can continue with Brewing Java: A Tutorial. If you get this far, you should be able to do the rest of any other tutorial out there.
Thursday, December 11, 2008
Ancient teleconference demo... of mouse, screen-sharing, hypertext, and more!
Yesterday was the 40th anniversary of what The Register calls "The Mother of All Demos". They're not kidding. You can see it in a video that captured the presentation. Here are some highlights:
- It starts out with 1 minute 30 seconds of text explaining how the whole production was set up, after which he jumps into his demonstration.
- He starts showing the hyperlinking at 15:50.
- He explains his mouse and his one-handed text entry device at 27-30 minutes in.
- Someone else joins in to work on the same screen at 57 minutes in.
Subscribe to:
Posts (Atom)