This guide is specific to getting LND 0.5-beta and Bitcoind running on Ubuntu 16.04 LTS for mainnet. It is aging rapidly and includes steps not necessary on newer versions of LND. As of April 2021 it is very out of date for bitcoind. As of December 2021 it is outdated for LND too.
Original installation guide:
This guide is broken into the following sections:
bitcoind and set to start automatically
| # create a redis app | |
| flynn create --remote "" redis | |
| # create a release using the latest (at the time of writing) Docker Redis image | |
| flynn -a redis release add -f config.json "https://registry.hub.docker.com?name=redis&id=868be653dea3ff6082b043c0f34b95bb180cc82ab14a18d9d6b8e27b7929762c" | |
| # scale the server to one process. This may time out initially as the server pulls the image, but watch "flynn -a redis ps" and should come up. | |
| flynn -a redis scale server=1 | |
| # redis should now be running in the cluster at redis.discoverd:6379 |
| class DisableMigrations(object): | |
| def __contains__(self, item): | |
| return True | |
| def __getitem__(self, item): | |
| return "notmigrations" | |
| MIGRATION_MODULES = DisableMigrations() |
| # If your test settings file doesn't import any other settings file | |
| # then you can use the function directly: | |
| def prevent_tests_migrate(db): | |
| import django | |
| from django.db import connections | |
| from django.db.migrations.executor import MigrationExecutor | |
| django.setup() | |
| ma = MigrationExecutor(connections[db]).loader.migrated_apps | |
| return dict(zip(ma, ['{a}.notmigrations'.format(a=a) for a in ma])) |
This runs a build for a small elixir (phoenix) project in about 40 seconds by caching as much of the compiled files as possible.
We've been using this for months in multiple projects without any issues. Please ping be if there is any issues with this script and I'll update it.
It should be generic enough to work on any elixir app using mix.
If you have a elixir_buildpack.config, then enable that section in the build script to keep versions in sync!
2016-08-09: Updated to newer Erlang and Elixir and fixed curl command.
Simply put, destructuring in Clojure is a way extract values from a datastructure and bind them to symbols, without having to explicitly traverse the datstructure. It allows for elegant and concise Clojure code.
| package main | |
| import ( | |
| "net/http" | |
| "database/sql" | |
| "fmt" | |
| "log" | |
| "os" | |
| ) |
There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.
So, these are the different settings we are going to compare:
| package main | |
| import ( | |
| "github.com/codegangsta/martini" | |
| "github.com/codegangsta/martini-contrib/binding" | |
| "github.com/codegangsta/martini-contrib/render" | |
| "labix.org/v2/mgo" | |
| ) | |
| type Wish struct { |
