- Setting up archlinux mirrors
- Pangenome browser
- Wikonnect
- Mapping outbreaks
- Covid Feeds
- Creating a racket web framework
- Working in GUILE sheepdog
I hereby claim:
- I am BonfaceKilz on github.
- I am bonfacemunyoki (https://keybase.io/bonfacemunyoki) on keybase.
- I have a public key whose fingerprint is D4F0 9EB1 1017 7E03 C28E 2FE1 F5BB AE1E 0392 253F
To claim this, I am signing this object:
xrandr --output HDMI1 --auto --right-of eDP1 |
# First searc for availabe networks
nmcli device sifi list
# Connect to device
nmcli device wifi connect <ssid name> password <pass>
import sys | |
import librosa | |
from numpy.linalg import norm | |
import librosa | |
from numpy.linalg import norm | |
from dtw import dtw | |
from random import shuffle | |
words = ['open','close'] | |
chosen_word = words[:] |
I've setup a docker image to work with the laravel 4.1 project and all its dependencies. Working with depracated code can be a nuisance, especially if you run a rolling release distro. You might break stuff in you local machine when downgrading things. Needless to say, it's frustrating. This is a short guide on how to set up and run a docker instance that has everything you need to work on any laravel 4.1 project.
I'll try as much as possible to dockerize things since upgrading the project in a safe way is one of the future goals of this project.
My goal for this was to have a working stable environment that can be replicated anywhere on any machine that has docker installed.
For the initial setup, I've cloned laradock
to the repository and set up the initial .env
.
nohup jupyter notebook &
# When you want to kill it:
lsof nohup.out
kill -9 <PID>
virtualenv -p /usr/bin/python3.5 py35
source py35/bin/activate
# For the first time run:
# pip install jupyter
# pip install matlab_kernel
jupyter # Jupyter running Python 3.5
deactivate # Leave virtualenv
If you don't set permissions right, your server will be down. If too restrictive, i.e. your server(e.g nginx or apache) has no write permissions for some things, content won't be served. If too liberal, you will pawned and alot of bad things will maybe happen. Here's how I set the permissions(should be added to playbooks if possible).
There are 2 ways of setting up the permissions:
- Make webserver owner of all files [Recommended]
- Giving yourself ownership
sudo chown -R www-data:www-data /path/to/dir