added src articles

2 files changed, 52 insertions, 0 deletions

diff --git a/src/getting-started-maas.txt b/src/getting-started-maas.txt
new file mode 100644
index 0000000..adc446b
--- /dev/null
+++ b/src/getting-started-maas.txt
@@ -0,0 +1,35 @@
+MAAS, which stands for *Metal As A Service* allows you to run physical servers as if they were virtual machine instance. This means you can configure, deploy and manage bare metal servers just like you would virtual machines in a cloud environment like Amazon AWS or Microsoft Azure. MAAS gives you the management tools that have made the cloud popular, but with the additional benefits of owning your own hardware.
+
+To run MAAS you'll need a server to run the management software and at least one server which can be managed with a BMC. Canonical recommends letting the MAAS server provide DHCP and DNS for the network the managed machines are connected to. If your setup requires a different approach to DHCP, see the MAAS documentation for more details on how DHCP works in MAAS and how you can adapt it to your current setup.
+
+To install MAAS first download Ubuntu Server 18.04 LTS and follow the step-by-step installation instructions to set up Ubuntu on your MAAS server. Once you have Ubuntu 18.04 up and running, you can install MAAS. To get the latest development release of MAAS, use the PPA `maas/next`. First add the PPA, then update and install. 
+
+~~~~console
+sudo add-apt-repository ppa:maas/next
+sudo apt update
+sudo apt install maas
+~~~~
+
+Once MAAS is installed, you'll need initialize it and create an admin user.
+
+~~~~console
+sudo maas init
+~~~~
+
+The init command will ask you ask you to create a username and password for the web-based GUI. You can optionally import your SSH keys as well.
+
+Once the installation is done you can login to the web-based MAAS GUI by pointing your browser to http://<your.maas.ip>:5240/MAAS/.
+
+maas-01.png
+
+Once you login to the MAAS web UI you'll be presented with the MAAS configuration panel where you can set the region name, configure a DNS forwarder for domains not managed by MAAS, as well as configure the images and architectures you want available for MAAS.
+
+maas-01.png
+
+Here you can accept the defaults and click continue. If you did not add your SSH keys in the init step, you'll need to upload them now. Then click "Go to Dashboard" to continue.
+
+The last step is to configure DHCP. When the MAAS Dashboard loads it will alert you that "DHCP is not enabled on any VLAN." To setup DHCP click the "Subnets" menu item and then click the VLAN where you want to enable DHCP. 
+
+This will bring up a new page where you can configure your DHCP subnet, start and end IP addresses, and Gateway IP. You can also decide how MAAS handles DHCP, whether directly from the rack controller or relayed to another VLAN. If you don't want MAAS to manage DHCP you can disable it here.
+
+To set up your first MAAS instances with MAAS handling DHCP, click the Configure MAAS-managed DHCP button.
diff --git a/src/qutebrowser-notes.txt b/src/qutebrowser-notes.txt
new file mode 100644
index 0000000..f7887e6
--- /dev/null
+++ b/src/qutebrowser-notes.txt
@@ -0,0 +1,17 @@
+handy commands:
+ :download
+
+## shortcuts
+xo - open url in background tab
+go - edit current url
+gO - edit current url and open result in new tab
+gf - view source 
+;y - yank hinted url
+;i - hint only images
+;b - open hint in background tab
+;d - download hinted url
+PP - Open URL from selection in new tab
+ctrl+a Increment no. in URL
+ctrl+x Decrement no. in URL
+
+Solarized theme: https://bitbucket.org/kartikynwa/dotty2hotty/src/1a9ba9b80f07e1f63b740da5e6970dc5a97f1037/qutebrowser.py?at=master&fileviewer=file-view-default