News Teknoids Need
ServerWatch: During the opening keynote for the Dockercon 16 conference, a primary message that was repeated time and again was that that Docker is all about building tools that help developers and operators do their jobs, faster and easier.
D’AO!On Friday I wrote about a hack at the Distributed Autonomous Organization, the odd venture capital fund built on top of the Ethereum smart-contract blockchain. In particular, I wrote about the possibility that the hack was not a “hack,” and that the $60 million that the hacker stole was not “stolen,” because the DAO’s governing documents, its terms and conditions, were set out solely in its code. If the code allowed someone to take $60 million, then that’s just how the DAO worked, and whoever took the $60 million got it fair and square.It is an odd view, and not one that I exactly endorse, either as a matter of law or as a matter of, like, how to run a system. But you know who does endorse that view? The hacker! Or, at least, someone claiming to be “The Attacker,” who wrote this:I have carefully examined the code of
Three years ago, Docker made an esoteric Linux kernel technology called containerization simple and accessible to everyone. Today, we are doing the same for container orchestration.
Container orchestration is what is needed to transition from deploying containers individually on a single host, to deploying complex multi-container apps on many machines. It requires a distributed platform, independent from infrastructure, that stays online through the entire lifetime of your application, surviving hardware failure and software updates. Orchestration is at the same stage today as containerization was 3 years ago. There are two options: either you need an army of technology experts to cobble together a complex ad hoc system, or you have to rely on a company with a lot of experts to take care of everything for you as long as you buy all hardware, services, support, software from them. There is a word for that, it’s called lock-in.
Docker users have been sharing with
Docker for AWS and Azure Beta.
Rich IntelliSense, Validation
TypeScript, JavaScript, CSS, LESS
Basic Syntax Colorization
HTML, XML, PHP, C#, C++, Razor, Markdown, Diff, Java, VB, CoffeeScript, Handlebars, Batch, Jade, F#, Lua, Powershell,
Python, SASS, R, Objective-C
Colorizers are implemented using Monarch.
Docker, which is hosting its sold-out developer conference in Seattle this week, today announced a major addition to its core Docker Engine. While the company previously split up many of the features it takes to use containers in production (think building containers, deploying them and then orchestrating them), it is now building container orchestration right into the Docker Engine. The… Read More
In this tutorial we’ll learn how to use Golang and MySQL together to build a login/signup system.
Before starting make sure you have MySQL installed and running.
GET THE REQUIRED PACKAGES
The driver to connect MySQL and Go
go get github.com/go-sql-driver/mysql
Bcrypt to encrypt passwords before saving them
go get golang.org/x/crypto/bcrypt
CREATE A SERVER
package main
import “net/http”
func homePage(res http.ResponseWriter, req *http.Request) {
http.ServeFile(res, req, “index.html”)
}
func main() {
http.HandleFunc(“/”, homePage)
http.ListenAndServe(“:8080”, nil)
}
Create index.html to link to a login/signup page
Home Page
Home Page
Login
Sign Up
CONNECT TO MYSQL
First import the MySQL driver
import “database/sql”
import _ “github.com/go-sql-driver/mysql”
Notice the _ before the driver. Instead of relying on the driver we use “database/sql” in case we want to change the driver in the future.
Now create a global sql.DB object and open a connection to MySQL
package main
import “database/sql”
import _ “github.com/go-sql-driver/mysql”
import “net/http”
// Global sql.DB to access the database by all handlers
var db *sql.DB
var err error
func homePage(res http.ResponseWriter, req *http.Request) {
http.ServeFile(res,
LKML: It’s been a fairly normal week, and rc4 is out. Go test.
A DAO Counter-AttackFriday the 17th of June was a dark day for The DAO. As many of you may have deduced, The DAO was attacked using the recursive call exploit inside the splitDAO() function. The attacker stole 3,641,694 ether which are currently located in a child DAO as can be seen here.There is a lot of debate around this attack, what it means for Ethereum, and most importantly what the potential suggested solutions will mean for Ethereum. This post has nothing to do with any of this. This post is here to empower you, the DAO Token Holders (DTHs) to do something about this attack while we wait for a hard fork.Plan of Action for the DAO Token HoldersWhat can we do from here on out? There are currently soft forks being implemented in the major Ethereum clients that would prevent any and all value transactions from going through via
Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.