elia/blog.lazkani.io-20200902-historical
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fixing some missed code blocks from the posts

Browse source
This commit is contained in:
Elia el Lazkani 2019-07-02 19:26:29 -04:00 committed by Elia El Lazkani
parent d3649f9a21
commit 5306197a2f
No known key found for this signature in database
GPG key ID: FBD81F2B1F488C2B
3 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
posts/irc/weechat_ssh_and_notification.rst
View file

@ -1,6 +1,6 @@
.. title: Weechat, SSH and Notification .. title: Weechat, SSH and Notification
.. date: 2019-01-01 .. date: 2019-01-01
.. updated: 2019-06-21 .. updated: 2019-07-02
.. status: published .. status: published
.. tags: irc, ssh, weechat, notification, .. tags: irc, ssh, weechat, notification,
.. category: irc .. category: irc
@ -36,7 +36,7 @@ Configuration
Let's look at the configuration to accomplish this... As mentioned in the beginning of the post, I run weechat in *tmux* on a server. So I *ssh* to the server before attaching *tmux*. The safest way to do this is to **port forward over ssh** and this can be done easily by *ssh*'ing using the following example. Let's look at the configuration to accomplish this... As mentioned in the beginning of the post, I run weechat in *tmux* on a server. So I *ssh* to the server before attaching *tmux*. The safest way to do this is to **port forward over ssh** and this can be done easily by *ssh*'ing using the following example.
.. code-block:: .. code:: text
$ ssh -R 5431:localhost:5431 server.example.com $ ssh -R 5431:localhost:5431 server.example.com
@ -44,7 +44,7 @@ At this point, you should have port **5431** forwarded between the server and yo
Once the previous step is done, you can test if it works by trying to run the *weenotify* script in server mode on your machine using the following command. Once the previous step is done, you can test if it works by trying to run the *weenotify* script in server mode on your machine using the following command.
.. code-block:: .. code:: text
$ python weenotify.py -s $ python weenotify.py -s
Starting server... Starting server...
@ -52,7 +52,7 @@ Once the previous step is done, you can test if it works by trying to run the *w
The server is now running, you can test port forwarding from the server to make sure everything is working as expected. The server is now running, you can test port forwarding from the server to make sure everything is working as expected.
.. code-block:: .. code:: text
$ telnet localhost 5431 $ telnet localhost 5431
Trying ::1... Trying ::1...
@ -63,7 +63,7 @@ If the connection is successful then you know that port forwarding is working as
Now we are ready to install the plugin in weechat and configure it. In weechat, run the following command. Now we are ready to install the plugin in weechat and configure it. In weechat, run the following command.
.. code-block:: .. code:: text
/script search weenotify /script search weenotify
@ -75,13 +75,13 @@ At which point, you should be greeted with the buffer shown in the screenshot be
You can install the plugin with **Alt + i** and make sure it autoloads with **Alt + A**. You can get more information about working with weechat scripts by reading the help menu. You can get the scripts help menu by running the following in weechat. You can install the plugin with **Alt + i** and make sure it autoloads with **Alt + A**. You can get more information about working with weechat scripts by reading the help menu. You can get the scripts help menu by running the following in weechat.
.. code-block:: .. code:: text
/help script /help script
The *weenotify* plugin is installed at this stage and only needs to be configured. The plugin has a list of values that can be configured. My configuration looks like the following. The *weenotify* plugin is installed at this stage and only needs to be configured. The plugin has a list of values that can be configured. My configuration looks like the following.
.. code-block:: .. code:: text
plugins.var.python.weenotify.enable string "on" plugins.var.python.weenotify.enable string "on"
plugins.var.python.weenotify.host string "localhost" plugins.var.python.weenotify.host string "localhost"
@ -90,7 +90,7 @@ The *weenotify* plugin is installed at this stage and only needs to be configure
Each one of those configuration options can be set as shown in the example below in weechat. Each one of those configuration options can be set as shown in the example below in weechat.
.. code-block:: .. code:: text
/set plugins.var.python.weenotify.enable on /set plugins.var.python.weenotify.enable on

4
posts/kubernetes/deploying_helm_in_your_kubernetes_cluster.rst
View file

@ -1,6 +1,6 @@
.. title: Deploying Helm in your Kubernetes Cluster .. title: Deploying Helm in your Kubernetes Cluster
.. date: 2019-03-16 .. date: 2019-03-16
.. updated: 2019-06-21 .. updated: 2019-07-02
.. status: published .. status: published
.. tags: kubernetes, helm, tiller, .. tags: kubernetes, helm, tiller,
.. category: kubernetes .. category: kubernetes
@ -48,7 +48,7 @@ This is where we start by creating a ``ServiceAccount``. The ``ServiceAccount``
We de deploy the ``ServiceAccount`` to the cluster. Save it to ``ServiceAccount.yaml``. We de deploy the ``ServiceAccount`` to the cluster. Save it to ``ServiceAccount.yaml``.
.. code:: yaml .. code:: text
$ kubectl apply -f ServiceAccount.yaml $ kubectl apply -f ServiceAccount.yaml
serviceaccount/tiller created serviceaccount/tiller created

4
posts/kubernetes/minikube_setup.rst
View file

@ -1,6 +1,6 @@
.. title: Minikube Setup .. title: Minikube Setup
.. date: 2019-02-09 .. date: 2019-02-09
.. updated: 2019-06-21 .. updated: 2019-07-02
.. status: published .. status: published
.. tags: minikube, kubernetes, ingress, ingress-controller, .. tags: minikube, kubernetes, ingress, ingress-controller,
.. category: kubernetes .. category: kubernetes
@ -126,7 +126,7 @@ Ingress
An ingress is an object of kind ``ingress`` that configures the ingress controller of your choice. An ingress is an object of kind ``ingress`` that configures the ingress controller of your choice.
.. code:: text .. code:: yaml
--- ---
apiVersion: extensions/v1beta1 apiVersion: extensions/v1beta1