home audio system

The LOOK

Before i forgot, one thing for you to consider is the ‘furniture’ for your equipments. to me, the ‘look’ of your setup is probably equally important as the audio part of it

one thing i wasn’t able to accomplish when i built my home theater is that it doesn’t fit my living environment. and home theater has the inherent challenge since there will be equipments, cables everywhere. how to store them properly, decorate with your home is something for you to consider. also because most of HT components don’t have the classy look of a stereo system but it can be fixed if you select your audio furniture and equipments properly.

some sites with quality audio furniture for your consideration

https://www1.crutchfield.com/g_15720/Audio-Cabinets-Racks.html#&nvpair=FFBrand|Bell’O&nvpair=FFBrand|Salamander Designs&nvpair=FFBrand|Sanus&nvpair=FFBrand|Solidsteel&nvpair=YCStyle|Cabinet

http://www.audioadvisor.com/

Recommended Home Theater System Brands

 

Advertisements

K8 Quick Guide for MacOS and VirtualBox

Commands

 

# Commands What it does
1 sysctl -a | grep machdep.cpu.features | grep VMX Minikube requires that VT-x/AMD-v virtualization is enabled in BIOS. To check that this is enabled on OSX / macOS ru
2 brew update && brew install kubectl && brew cask install docker minikube virtualbox use brew to install kubectl, docker, minikube and virtualbox
3 docker –version

docker-compose –version

docker-machine –version

minikube version

kubectl version –client

verify the installation
4 minikube start start minikube

a local kubernetes cluster with one node

5 kubectl get nodes should show only one node
6 eval $(minikube docker-env) Use minikube’s built-in docker daemon:
7 docker ps
8 docker run -d -p 5000:5000 –restart=always –name registry registry:2 First setup a local registry, so Kubernetes can pull the image(s) from there.
9 docker build . –tag my-app build the Dockerfile below locally if you want to follow this guide to the letter. Store the Dockerfile locally, preferably in an empty directory and run:
10 docker tag my-app localhost:5000/my-app:0.1.0 You should now have an image named ‘my-app’ locally, check by using docker images (or your own image of course). You can then publish it to your local docker registry:
11 docker images
12 kubectl create -f my-app.yml deployment “my-app” created

service “my-app” created

13 kubectl get all show the pod and service
14 minikube service my-app –url The configuration exposes my-app outside of the cluster, you can get the address to access it by running
15 minikube dashboard start gui dashboard

URL is something like http://192.168.99.100:30000/

minikube ssh ssh to minikube
16 kubectl delete deploy my-app

kubectl delete service my-app

Delete deployment of my-app
17 minikube stop;

minikube delete;

rm -rf ~/.minikube .kube;

brew uninstall kubectl;

brew cask uninstall docker virtualbox minikube;

clean up everything

mysql-wordpress

 

# Commands What it does
1 kubectl version check version
2 kubectl create secret generic mysql-pass –from-literal=password=michelle create secret

use ‘michelle’ as password

3 kubectl get secrets verify secret
4 kubectl create -f mysql-deployment.yaml Deploy MySQL from the mysql-deployment.yaml file

The MYSQL_ROOT_PASSWORD environment variable sets the database password from the Secret

5 kubectl get pvc Verify that a PersistentVolume got dynamically provisioned
6 kubectl create -f wordpress-deployment.yaml Create a WordPress Service and Deployment from the wordpress-deployment.yaml file
7 kubectl get pvc kubectl get pvc
8 kubectl get services wordpress Verify that the Service is running by running the command
9 minikube service wordpress –url
10 kubectl delete secret mysql-pass

kubectl delete deployment -l app=wordpress

kubectl delete service -l app=wordpress

kubectl delete pvc -l app=wordpress

delete secret

delete all deployments and services

delete the PersistentVolumeClaims. The dynamically provisioned PersistentVolumes will be automatically deleted.

expose mysql to local
11 kubectl get pods retrieve the name of mysql pod
12 kubectl port-forward wordpress-mysql-86987f6b9-9zvbx 3306:3306 port forwarding

https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#port-forward/

13 connect to it use mysql workbench to connect via localhost:3306

References

  1. https://gist.github.com/kevin-smets/b91a34cea662d0c523968472a81788f7
  2. https://kubernetes.io/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/#objectives
  3. Kubectl https://kubernetes.io/docs/tasks/tools/install-kubectl/#configure-kubectl
  4. Minikube https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/

comodo SSL

  1. Root CA Certificate – AddTrustExternalCARoot.crt
  2. Intermediate CA Certificate – COMODORSAAddTrustCA.crt
  3. Intermediate CA Certificate – COMODORSADomainValidationSecureServerCA.crt
  4. Your PositiveSSL Certificate – www_example_com.crt (or the subdomain you gave them)
    • SSLCertificateFile /etc/pki/tls/certs/www_example_com.crt
  5. Private key
    • SSLCertificateKeyFile /etc/pki/tls/private/www_example_com.key

Reference

photo.njfcs.org

  • FCS photo site is hosted at dreamhost and built with a open source software called pydio
  • URL – http://photo.njfcs.org/
  • Following is the instruction to upload photos
  1. Get an account by emailing webmaster@njfcs.org then IT director will assist you with it
  2. Navigate to http://photo.njfcs.org/ and login with provided username and password at lower left corner as shown in screenshot below. Check ‘Auto login’ if you’d like browser to remember your login information (which I do)
    •   
  3. Upon login, you will see Administration link as shown in the screenshot above. Click on it and it will take you to the backend dashboard – as shown in the third screenshot above.
  4. Now you’re ready to upload photos. Simply click Add and you will a screen as shown below. From here, you can either create a new album OR use an existing one.
    •  
  5. In this tutorial, I chose to create a new album called “Painting & Calligraphy (國畫/書法)“. Once you enter the Album name, click Create button to create a new album.
    • Please note that Pydio does support nested album (album within an album) so be sure to select “—————” if you DON’T want it to be in a parent album.
  6. Now your album is ready, you can either drag&drop to “Drag files here” area OR click on to  to upload. Keep in mind it does support uploading several photos at the same time so you can add as many as you want.
    •  
  7. When you’re done selecting photos, click  to upload photos.
  8. Now you should see your album and uploaded photos when you go to http://photo.njfcs.org/ – which sorts the albums by the uploaded date.
  9. Shall you have any questions, please contact webmaster@njfcs.org

NJFCS weekly communication

URL: http://sendmail.njfcs.org

Weekly Communication content can be found here

1. Login

  • UID/Password: please check with IT director

2. Landing Page

  • where you can find previous announcements

3. Create & send new campaign

  • click on ?to compose an announcement

  • enter the Subject

  • be sure to correctly enter ‘From name’ and ‘Reply to email’ to reflect your identity (e.g. FCS PA Director / pa@njfcs.org; FCS Culture Director/ culture@njfcs.org; FCS Principal / principal@njfcs.org

  • enter the email body

4. Click on?at the bottom left to continue

5. Choose the intended list – if you have any questions, please contact IT director

  • as of December 2016 – we use following lists

6. Click??to Send announcement

7. Check the status and confirm that the status has reached 100%. If the service stalls for whatever reason, refresh the page and hit ‘resume‘ and check again as shown below. It normally takes couple of minutes to deliver to 500 recipients.

sendmail.njfcs.org admin notes

http://sendy.co/get-started

super user: webmaster@njfcs.org

shared user: board_members@njfcs.org (campaign notification will be sent to webmaster@njfcs.org)

Current verified email:

  • dchang@njfcs.org
  • board_members@njfcs.org
  • pa@njfcs.org
  • principal@njfcs.org
  • sysops@njfcs.org
  • *@njfcs.org
  • webmaster@njfcs.org

change favicon https://sendy.co/forum/discussion/530/how-do-i-update-favicon/p1


Mail list

  • clubs – club leaders and members
  • families – all registered families from reigstration system
  • friends – free subscription – see below – for website subscription only
  • staff/teachers – Principal provide the list

newsletter subscription widget – mapped to 2014-15 friends list (id=14)


Encoding problem.

change database to utf8_general_ci
change following fields to utf8_general_ci – name, plain_text, html_text
change following campaigns table and “title” field (aka subject) to utf8_general_ci (chinese character encoding in the subject)

Blog at WordPress.com.

Up ↑