Skip to content

Instantly share code, notes, and snippets.

ubuntu@ip-172-26-15-143:~/janus-gateway$ /opt/janus/bin/janus
Janus commit: eba22d302e5355726222489bd0c6bbf860453ac0
Compiled on: Fri Aug 21 15:20:11 UTC 2020
Logger plugins folder: /opt/janus/lib/janus/loggers
[WARN] Couldn't access logger plugins folder...
---------------------------------------------------
Starting Meetecho Janus (WebRTC Server) v0.10.5
---------------------------------------------------
@pwrstudio
pwrstudio / gist:7f3c5b79a444206d530d40fbb5c61e00
Created August 21, 2020 15:09
Output of meson --prefix=/usr build
ubuntu@ip-172-26-15-143:~/libnice$ meson --prefix=/usr build
The Meson build system
Version: 0.55.1
Source dir: /home/ubuntu/libnice
Build dir: /home/ubuntu/libnice/build
Build type: native build
Project name: libnice
Project version: 0.1.17.1
C compiler for the host machine: cc (gcc 7.5.0 "cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0")
C linker for the host machine: cc ld.bfd 2.30
@pwrstudio
pwrstudio / gist:ce0977870b0669995ffcef38b70ee555
Last active August 21, 2020 15:19
Output of ./configure --prefix=/opt/janus
ubuntu@ip-172-26-15-143:~/janus-gateway$ ./configure --prefix=/opt/janus --disable-websockets --disable-data-channels --disable-rabbitmq --disable-mqtt
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
@pwrstudio
pwrstudio / gist:dae9e81d293c60e12fc32a17add961ee
Last active August 21, 2020 16:15
Janus-gateway installation on Ubuntu 18.4 AWS instance (Lightsail)
Janus-gateway installation on Ubuntu 18.4 AWS instance (2020/08/21)
HTTP only, no data channels
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
** FIX MISSING LOCALE
LC_ALL="en_US.UTF-8" # <= add this line to /etc/environment and reboot
- - - - - -
const Web3 = require('web3')
const Tx = require('ethereumjs-tx')
const web3 = new Web3()
web3.setProvider(new web3.providers.HttpProvider('https://rinkeby.infura.io/TOKEN'))
const CONTRACT_ADDRESS = '0xxx'
const abi = [
{
Verifying that "pwrstudio.id" is my Blockstack ID. https://onename.com/pwrstudio

Keybase proof

I hereby claim:

  • I am pwrstudio on github.
  • I am pwr (https://keybase.io/pwr) on keybase.
  • I have a public key whose fingerprint is 2948 ED1D 7B0A A9C2 B1A6 D002 C17D A031 155C 0CEE

To claim this, I am signing this object:

@pwrstudio
pwrstudio / gist:76ba6cf14fb6bd3ec660ce2a104154be
Last active August 19, 2016 14:45
wp.sh – wordpress setup script
#!/bin/bash
#
# Useage: wp.sh nameofproject
#
BASEDIR="/where/you/want/the/site/to/be/installed"
# $1 == first command line argument eg. 'nameofproject'
mkdir -v $BASEDIR/$1
@pwrstudio
pwrstudio / .htaccess
Created November 11, 2015 20:11 — forked from ludo237/.htaccess
The ultimate .htaccess file. Please feel free to fork it, edit it and let me know what do you think about it.
# Apache configuration file
# httpd.apache.org/docs/2.2/mod/quickreference.html
# Note .htaccess files are an overhead, this logic should be in your Apache
# config if possible: httpd.apache.org/docs/2.2/howto/htaccess.html
# Techniques in here adapted from all over, including:
# Kroc Camen: camendesign.com/.htaccess
# perishablepress.com/press/2006/01/10/stupid-htaccess-tricks/
# Sample .htaccess file of CMS MODx: modxcms.com
# This is the free sample of .htaccess from 6GO s.r.l.
# @author Claudio Ludovico Panetta (@Ludo237)

Between us [company name] and you [customer name]

Summary:

We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.

So in short;

You ([customer name]), located at [customer address] are hiring us ([company name]) located at [company address] to [design and develop a web site] for the estimated total price of [total] as outlined in our previous correspondence. Of course it’s a little more complicated, but we’ll get to that.