X-Git-Url: https://feistymeow.org/gitweb/?a=blobdiff_plain;ds=inline;f=production%2Fsites%2Fcakelampvm.com%2Fdocs%2Fmanual%2Fcakelampvm_guide_v002.html;h=71db45c80c026657b05807c7a7e7b657070f55d9;hb=df7e2dd0c79566650f4104496679c43a6a059424;hp=81ba2ece90304bef8c6a0e51b1e9db95460da0c8;hpb=6b91cc7376d82a4fb9260c32349eca0244a00f80;p=feisty_meow.git diff --git a/production/sites/cakelampvm.com/docs/manual/cakelampvm_guide_v002.html b/production/sites/cakelampvm.com/docs/manual/cakelampvm_guide_v002.html index 81ba2ece..71db45c8 100644 --- a/production/sites/cakelampvm.com/docs/manual/cakelampvm_guide_v002.html +++ b/production/sites/cakelampvm.com/docs/manual/cakelampvm_guide_v002.html @@ -1,7 +1,7 @@
- +The cakelampvm project provides a Virtualbox VM that acts as an "internet in a bottle", serving up your web sites securely and only to your local host. The virtual machine provides DNS services (gnome display manager
★ This section requires that the VM is already configured properly for + Host-Only and NAT networks.
Using the Virtualbox interface, you should now be able to start your virtual machine. Virtualbox will complain if it detects any remaining configuration problems in the VM. The Linux boot sequence @@ -153,15 +154,35 @@ with:
ssh developer@10.28.42.20
# or perform the equivalent connection with your ssh client.
And then provide the password to log in.
-Once the DNS services are set up (discussed in detail below), you will be - able to run the much friendlier command:
++ +
++ + ★ It is very important that the ssh connection is working properly before + proceeding to other configuration steps. If ssh is not working, try + pinging the host:
+ping 10.28.42.20+
If the ping is also failing, then please re-check the two network + configuration sections above (for Host-Only networking and NAT + networking). These are both required for the VM's network to + function as designed.
+Optional: Once the DNS services are set up (discussed in detail below), + you will be able to run the much friendlier command:
ssh developer@cakelampvm.com
It is important to set up ssh key forwarding to enable your use of git repositories while logged into the VM. Key forwarding should be enabled for the VM's two fake host identities:
cakelampvm.com
10.28.42.20
+ The details of configuring ssh key forwarding vary for each ssh + client. For Linux ssh, the ~/.ssh/config file might contain + this information:
+Host cakelampvm.com 10.28.42.20+
ForwardAgent yes
★ This section requires that the VM is already configured and is + accessible via ssh.
The cakelampvm v002 is released with the intention that it not need to be released again. Version 001 was not built with that explicit intention, which then required the release of Version 002. But we @@ -169,12 +190,13 @@
There is an update feature built into the VM that is quite easy to use. The updates are driven by the feisty meow script repository in conjunction with a local scripted command. To activate the "update - process" for your VM, run the following commands on the VM:
-# update to the latest version of feisty meow.
rpuffer $FEISTY_MEOW_APEX; reconfigure_feisty_meow
# enact any configuration changes needed, such as permissions and account setup.
+ process" for your VM, run the following commands on the VM, logged in as
+ the developer user:
+ # update to the latest version of feisty meow.
rpuffer $FEISTY_MEOW_APEX; regenerate
# enact any configuration changes needed, such as permissions and account setup.
revamp_cakelampvm
These two commands can be run at any time to patch up your VM to the
- latest.
+ latest configuration.
Recent versions of feisty meow support a new "get_feisty"
command, which will behave the same as the first line above. Once
you have run the "puffer..." command above for the first time (on
@@ -189,7 +211,9 @@ revamp_cakelampvm
gone astray, especially for problems with permissions.
Here are some first steps that will make the vm your own:
+★ This section requires that the VM is already configured and is + accessible via ssh.
+Here are some first steps that will make the vm your own.
(The feisty meow codebase is already configured for the developer account on the cakelampvm virtual machine.)
★ This section requires that the VM is already configured and is + accessible via ssh.
The cakelampvm has been set up to provide a DNS server which will answer name lookup requests on any of the sites that the cakelampvm is hosting for you. It will also serve as a general DNS server for any other @@ -397,6 +423,114 @@ href="http://mapsdemo.cakelampvm.com">http://mapsdemo.cakelampvm.com describes how to set up Cygwin to run X server, which enables X11 forwarding to your local display.
...{insert that info}...
+A Cheat sheet for the Vim editor (there are many of these available): https://vim.rtorr.com/
+A git branching model that seems to work well: http://nvie.com/posts/a-successful-git-branching-model/
+This is a basic guide to the Google Developer Console and API Key + management: Google + API Docs
+Meld is a great comparison tool that displays differences between two + files or directories or directory trees in a graphical view. Meld is + pre-installed on the VM. This tool can be launched either in the + VM's X Windowing System (on the console) or if X11 forwarding is enabled.
+To run meld, just type this command:
+meld A B
+ where A and B are either both file names or they are both directory + names. If A and B are directories, meld will compare the entire tree + structure between the two directories. It allows one to copy from + one side to the other, even if the item that needs to be copied is an + entire subdirectory.
+Run this command:
+ifconfig
+ In the results, look for "inet addr". + There may be more than one, if there are multiple network interfaces.
+The standard IP address is 10.28.42.20 for the cakelampvm.
+When you've got the DNS and everything integrated, these commands will + manage the vm's state:
+First, log into the guest VM:
+ssh developer@cakelampvm.com
+ Then, to reboot the guest VM:
+sudo reboot
+ Or, to halt the guest VM:
+sudo shutdown -h now
+ Using these commands is kinder to the VM than just cycling the power from + the Virtualbox control panel.
+This is the lowest level of plumbing for your VM. Hopefully you + will not need to engage with this section. The most useful doc + section here is the one below about the "Virtualbox guest additions", + which you will probably need at some future point. Oracle releases + updates to the guest additions fairly regularly.
+The guest VM should already be set up appropriately. These steps + are provided for reference and updates.
+sudo mount /dev/sr0 /media/cdrom
+ Linux will mention that the device is mounted "read-only".
+cd /media/cdrom
sudo sh VBoxLinuxAdditions.run
+ The network interfaces should already be configured on the guest within + the Virtualbox configuration. This is available by clicking on the + VM in the Virtualbox manager and selecting "Settings". These are the + configuration settings used:
+ Adapter 1:Adapter 2:
+ Attached to: Nat Network
+ Name: NatNetwork
On the guest VM itself, the network settings are specified in a file + called /etc/network/interfaces. Here are the current contents of + that file:
+source /etc/network/interfaces.d/*+
auto lo
iface lo inet loopback
auto enp0s3
iface enp0s3 inet static
address 10.28.42.20
netmask 255.255.255.0
network 10.28.42.0
broadcast 10.28.42.255
dns-domain cakelampvm.com
dns-search cakelampvm.com
dns-nameservers 127.0.0.1 8.8.8.8
auto enp0s8+
iface enp0s8 inet dhcp+
+
To minimize the size used for the disk image, there are three major + steps.
+1. While running the VM, run this command:
+sudo apt clean
+ This throws away any cached data from the apt tool, which can be + substantial.
+If there are other junk files you know of that can be removed, delete + those now also.
+2. Reboot the VM to the gparted ISO image (available at the gparted + site) and run the following command:
+sudo zerofree /dev/sda
+ This sets all free space to the zero byte, enabling Virtualbox to free + that space in the next step.
+3. Shut the vm down after zerofree is complete and run this command on + the host PC (this is the Linux version of the command):
+VBoxManage modifyhd --compact ~/cake_lamp_vm/cake-lamp-vm-hd.vdi
+ Replace the ~/cake_lamp_vm + path with the real VM storage path. This command compacts the root + (and only) partition of the VM.
+After these steps are complete, the VM should be its minimal size.
Note: these instructions, even the quick approaches below, pale in comparison to the ease of use of the "standup" command in feisty meow's @@ -515,114 +649,6 @@ href="http://mapsdemo.cakelampvm.com">http://mapsdemo.cakelampvm.com for any error messages that can be corrected. The log files are stored in "/var/log/apache2" and are named after the website (if configured through the above process).
-A Cheat sheet for the Vim editor (there are many of these available): https://vim.rtorr.com/
-A git branching model that seems to work well: http://nvie.com/posts/a-successful-git-branching-model/
-This is a basic guide to the Google Developer Console and API Key - management: Google - API Docs
-Meld is a great comparison tool that displays differences between two - files or directories or directory trees in a graphical view. Meld is - pre-installed on the VM. This tool can be launched either in the - VM's X Windowing System (on the console) or if X11 forwarding is enabled.
-To run meld, just type this command:
-meld A B
- where A and B are either both file names or they are both directory - names. If A and B are directories, meld will compare the entire tree - structure between the two directories. It allows one to copy from - one side to the other, even if the item that needs to be copied is an - entire subdirectory.
-Run this command:
-ifconfig
- In the results, look for "inet addr". - There may be more than one, if there are multiple network interfaces.
-The standard IP address is 10.28.42.20 for the cakelampvm.
-When you've got the DNS and everything integrated, these commands will - manage the vm's state:
-First, log into the guest VM:
-ssh developer@cakelampvm.com
- Then, to reboot the guest VM:
-sudo reboot
- Or, to halt the guest VM:
-sudo shutdown -h now
- Using these commands is kinder to the VM than just cycling the power from - the Virtualbox control panel.
-This is the lowest level of plumbing for your VM. Hopefully you - will not need to engage with this section. The most useful doc - section here is the one below about the "Virtualbox guest additions", - which you will probably need at some future point. Oracle releases - updates to the guest additions fairly regularly.
-The guest VM should already be set up appropriately. These steps - are provided for reference and updates.
-sudo mount /dev/sr0 /media/cdrom
- Linux will mention that the device is mounted "read-only".
-cd /media/cdrom
sudo sh VBoxLinuxAdditions.run
- The network interfaces should already be configured on the guest within - the Virtualbox configuration. This is available by clicking on the - VM in the Virtualbox manager and selecting "Settings". These are the - configuration settings used:
- Adapter 1:Adapter 2:
- Attached to: Nat Network
- Name: NatNetwork
On the guest VM itself, the network settings are specified in a file - called /etc/network/interfaces. Here are the current contents of - that file:
-source /etc/network/interfaces.d/*-
auto lo
iface lo inet loopback
auto enp0s3
iface enp0s3 inet static
address 10.28.42.20
netmask 255.255.255.0
network 10.28.42.0
broadcast 10.28.42.255
dns-domain cakelampvm.com
dns-search cakelampvm.com
dns-nameservers 127.0.0.1 8.8.8.8
auto enp0s8-
iface enp0s8 inet dhcp-
-
To minimize the size used for the disk image, there are three major - steps.
-1. While running the VM, run this command:
-sudo apt clean
- This throws away any cached data from the apt tool, which can be - substantial.
-If there are other junk files you know of that can be removed, delete - those now also.
-2. Reboot the VM to the gparted ISO image (available at the gparted - site) and run the following command:
-sudo zerofree /dev/sda
- This sets all free space to the zero byte, enabling Virtualbox to free - that space in the next step.
-3. Shut the vm down after zerofree is complete and run this command on - the host PC (this is the Linux version of the command):
-VBoxManage modifyhd --compact ~/cake_lamp_vm/cake-lamp-vm-hd.vdi
- Replace the ~/cake_lamp_vm - path with the real VM storage path. This command compacts the root - (and only) partition of the VM.
-After these steps are complete, the VM should be its minimal size.
This is all work that should already have been done. It is mentioned here just as breadcrumbs for a future vm builder.