# the "fredme" macro enables the feisty_meow environment.
alias fredme='source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"'
-# synonym for fredme.
+# synonym for fredme which makes more sense to most people.
alias feistyme='source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"'
# if not commented out, then feisty meow will run all the unit tests during builds.
~
Never admit defeat. Just move the front.
-- fred t. hamster
+~
+down came eddy from his heady,
+where he dwells often unsteady,
+you see he gets so high,
+mind expanded to sky;
+real world grokking just not ready.
+ -- fred t. hamster
+
# specifies the version of the code that is being constructed here.
major=2
minor=140
-revision=97
+revision=98
build=420
# specifies the remainder of the version record info.
--- /dev/null
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta content="text/html; charset=windows-1252" http-equiv="content-type">
+ <title>Cake LAMP VM Documentation</title>
+ </head>
+ <body>
+ <h1 style="text-align: center;">The cakelampvm VM:<br>
+ Configuration and Usage</h1>
+ <h2 style=" text-align: center;">By Chris Koeritz</h2>
+ <h3 style=" text-align: center;"> Vintage: cakelampvm v002
+ Updated: 2017-11-10</h3>
+ <h6> </h6>
+ <h2>Basic info for the guest VM</h2>
+ <ul>
+ <li>hostname: cakelampvm.com</li>
+ <li>local IP address: 10.28.42.20</li>
+ <li>services: DNS (bind9), apache2, fluxbox X windowing system, gnome
+ display manager</li>
+ <li>main user: developer (password distributed separately)</li>
+ <li>mysql root password: (password distributed separately)</li>
+ </ul>
+ <h2>How to set up virtualbox for your host PC</h2>
+ <ol>
+ <li>Download and install virtualbox:
+ https://www.virtualbox.org/wiki/Downloads</li>
+ <li>Install the extension pack for virtualbox: This provides USB drivers
+ and other features. This is installed on virtualbox itself, not on
+ the guests.</li>
+ <ol>
+ <li>Download the extension pack at
+ https://www.virtualbox.org/wiki/Downloads</li>
+ <li>Stop any running virtualbox vms.</li>
+ <li>Close virtualbox control panel.</li>
+ <li>Double-click on the downloaded extensions package (in a file
+ explorer) and virtualbox should install it.</li>
+ </ol>
+ <li>Run the virtualbox control panel.</li>
+ <li>Download the cakelampvm guest vm package and unzip it. Store the
+ unzipped version in some appropriate place where you want the virtual
+ machine to reside on your host's hard drive.</li>
+ <li>Add the guest VM to your list of VMs. From the virtualbox menus,
+ choose the "Machine" menu and select "Add". Point the selector
+ dialog at the cakelampvm folder you created above and open the
+ cakelampvm.vbox file.</li>
+ <li>Now the cakelampvm should show up in the list of virtual
+ machines. Before starting it, perform the following network
+ configuration sections.</li>
+ </ol>
+ <h3>Configure the Host-Only network on virtualbox</h3>
+ <p>Configuring host-only networking for the VM makes the VM completely local
+ to your machine. The cakelampvm will not be accessible on the
+ internet or from the LAN, and can only be accessed by your host PC.</p>
+ <ol>
+ <li> Go to virtual box "Preferences" (global preferences, not for a
+ specific vm).</li>
+ <li> Click on the "Network" tab.</li>
+ <li> Choose the "Host-only Networks" tab from within "Network".</li>
+ <li> Click the plus icon to add a new host-only network.</li>
+ <li>Set the "Adapter" parameters:<br>
+ IPv4 Address: 10.28.42.1<br>
+ IPv4 Network Mask: 255.255.255.0<br>
+ IPv6 Address: (leave blank)<br>
+ IPv6 Prefix Length: 0<br>
+ Virtualbox will fill in the other details like so:<br>
+ <p><img alt="host only network adapter" src="images/host_only_network_adapter.png"></p>
+ </li>
+ <li>Set the "DHCP Server Settings" to disabled, e.g.<br>
+ <img alt="host only dhcp" src="images/host_only_adapter_dhcp_server.png"><br>
+ This is disabled because we will be using statically assigned addresses
+ for convenience and stability.</li>
+ </ol>
+ <p>Additional information on host-only (and other) network adapter types is
+ at: https://www.virtualbox.org/manual/ch06.html#network_nat_service<br>
+ </p>
+ <h3>Configure the Nat Network on virtualbox</h3>
+ <ol>
+ <li> Go to virtual box "Preferences" (global preferences, not for a
+ specific vm).</li>
+ <li> Click on the "Network" tab.</li>
+ <li> Choose the "Nat Networks" tab from within "Network".</li>
+ <li> Click the plus icon to add a new host-only network.</li>
+ <li>Set the "NAT Network Details" parameters:<br>
+ Network Name: NatNetwork<br>
+ Network CIDR: 10.0.2.0/24<br>
+ Supports DHCP: checked<br>
+ Supports IPv6: optionally checked<br>
+ These are my settings, with IPv6 left disabled:<br>
+ <img alt="nat net config" src="images/nat_network_config.png"></li>
+ </ol>
+ <h2>Using the guest VM's DNS services</h2>
+ <p>The cakelampvm has been set up to provide a DNS server which will answer
+ name requests for all of the sites that the VM hosts.</p>
+ <p>To use the cakelampvm DNS, modify your host operating system network
+ configuration by adding or changing the DNS server to use the guest VM's
+ DNS service. This is available at the local address
+ 10.28.42.20. The DNS server can be tested with nslookup, dig and
+ other tools.</p>
+ <p>Note that the cakelampvm DNS should be listed first, if one intends to
+ override any DNS names that actually exist out on the internet.</p>
+ <p>If the DNS server is properly set up, then these ping commands should get
+ answering responses:</p>
+ <pre>ping cakelampvm.com</pre>
+ <pre>ping defaultcake.cakelampvm.com</pre>
+ <pre>ping mapsdemo.cakelampvm.com</pre>
+ <h2>Editing files on the guest VM from the host</h2>
+ <p>On the host computer, look for the guest vm as a networked computer
+ called cakelampvm. This should provide some network shares using
+ Microsoft SMB protocol, and they can be attached to using the "developer"
+ user and its password.</p>
+ <p>On windows, one may want to mount this network location as a drive letter
+ for easier access.</p>
+ <p>Currently, the root of all web servers is exposed as "www". Editing
+ the files in those folders requires ownership by the developer user.
+ Currently the defaultcake server is owned by developer.</p>
+ <p>One should be able to create a new directory in the www folder owned by
+ the developer user over the network also, which can be used for creating
+ new projects. However, there is a config issue in the current vm
+ (v001) about this; to fix, run this command on the guest vm as the
+ developer user:</p>
+ <pre>sudo chmod g+w /var/www</pre>
+ <p>Afterwards, the www folder should allow the developer user to create new
+ folders at will.</p>
+ <h2>Accessing files on the host PC from the guest VM</h2>
+ <p>If you want to share a folder from the host to the guest, perhaps for
+ driver updates or other conveniences, then make the share with these
+ steps:</p>
+ <ol>
+ <li>Create a folder on the host that is to be shared.</li>
+ <li>Right-click on the vm in virtualbox manager and choose "Settings".</li>
+ <li>In the "Shared Folders" tab of the settings, go to "Machine Folders".</li>
+ <li>Click the folder plus icon to create a new share.</li>
+ <li>Fill in the "Folder Path" on the host PC to the folder that will be
+ shared, and give it a name for the guest. We assume the folder
+ name will be "myshare".</li>
+ <li>On the guest vm, run the following commands to mount the share:<br>
+ <pre>mkdir ~/shared # for the guest's version of the shared folder</pre>
+ <pre>sudo mount -t vboxsf myshare ~/shared # mount the vm's share name onto the folder on the vm.</pre>
+ </li>
+ </ol>
+ <h2>Adding a new website and domain on the guest VM</h2>
+ <p>To add a new website, you will need to pick one of the DNS options below
+ (A or B) depending on how you want to name the site. After the DNS
+ is updated, then follow the section after for creating a new apache conf
+ file.</p>
+ <p>Assuming one has created a new folder in "www" called "greatsite", then
+ the new web site can be brought online on the vm with one of the following
+ options.</p>
+ <h3>DNS Option A: Using a sub-domain in the cakelampvm.com domain</h3>
+ Connect to the cakelampvm via ssh as the developer user, e.g.: ssh
+ developer@cakelampvm.com
+ <p>Execute the following command to edit the DNS file for the cakelampvm
+ domain:</p>
+ <pre>sudo vi /etc/bind/cakelampvm.com.conf</pre>
+ <p>Add a stanza for the new site at the end of this file:</p>
+ <pre>greatsite.cakelampvm.com IN A 10.28.42.20<br> IN HINFO "linux server" "ubuntu"</pre>
+ <p>Restart the DNS server: sudo service bind9 restart</p>
+ <p>Afterwards, pinging greatsite.cakelampvm.com should work from either the
+ guest or the host.</p>
+ <h3>DNS Option B: Using an entirely new domain for the site</h3>
+ <p>Similar procedure to above, but we will create a new file for the new
+ domain and add it to the bind directory. For this example, we will
+ create a file called /etc/bind/greatsite.tv.conf for our new domain
+ greatsite.tv with these contents:</p>
+ <pre>$TTL 1W<br>@ IN SOA @ fred.cakelampvm.com. (<br> 2017100801 ; serial<br> 2H ; refresh<br> 8M ; retry<br> 14D ; expiry<br> 6H ) ; minimum<br><br> IN NS ns.cakelampvm.com.<br> IN MX 10 mail.cakelampvm.com.<br><br># main domain for machine.<br>greatsite.tv. IN A 10.28.42.20<br> IN HINFO "linux server" "ubuntu"</pre>
+ The gnarly prefix stuff above the "greatsite.tv." listing establishes
+ configuration info for the new domain. This file relies on the
+ existing cakelampvm.com infrastructure in DNS, such as the "ns" host, which
+ is the domain's name server.
+ <p>Now that the config file is in place, edit "named.conf.local" to add the
+ new file by adding this bit of configuration at the end:</p>
+ <pre>zone "greatsite.tv" in {<br> file "/etc/bind/greatsite.tv.conf";<br> type master;<br> allow-query { any; };<br>};</pre>
+ <p>Restart the DNS server: sudo service bind9 restart</p>
+ <p>Afterwards, pinging greatsite.tv should work from either the guest or the
+ host.</p>
+ <h3>Create a new apache configuration file and load it</h3>
+ <p>Start with the following template file for the new website, and modify it
+ for the appropriate host name:</p>
+ <pre><VirtualHost *:80><br> ServerName greatsite.cakelampvm.com<br> ServerAlias greatsite.cakelampvm.com *.greatsite.cakelampvm.com<br> DocumentRoot /var/www/greatsite<br> ErrorLog ${APACHE_LOG_DIR}/greatsite.cakelampvm.com-error.log<br> CustomLog ${APACHE_LOG_DIR}/greatsite.cakelampvm.com-access.log combined<br> Alias /statistics "/var/www/webwork.repository/webwork/maps_demo/webroot/statistics"<br> Include /etc/apache2/conf-library/basic-options.conf<br> Include /etc/apache2/conf-library/rewrite-enabling.conf<br></VirtualHost></pre>
+ <p>The above example is pre-modified for DNS Option A above, the
+ greatsite.cakelampvm.com name. Switching all of those to
+ "greatsite.tv" instead would support DNS option B.</p>
+ <p>Copy that file into /etc/apache/available-sites under an appropriate
+ name, which here we will call "greatsite.conf".</p>
+ <p>Tell apache to use the new file:</p>
+ <pre>a2ensite greatsite.conf</pre>
+ <p>Finally, restart apache to get it to begin serving the site:</p>
+ <pre>sudo service apache2 restart</pre>
+ <h3>Test the new web site</h3>
+ <p>Given the configuration above, your host PC should now be able to access
+ the new website.</p>
+ <p>To test this, first try pinging the hostname, e.g.: ping
+ greatsite.cakelampvm.com or ping greatsite.tv</p>
+ <p>Then, if there are responses to the ping, it means the DNS is
+ working. If there are no responses, check the instructions in the
+ above DNS option section.</p>
+ <p>Once the DNS is working, one can try browsing to the site at:
+ http://greatsite.cakelampvm.com or http://greatsite.tv (depending on the
+ DNS option chosen).</p>
+ <p>If the site is not showing up properly, try examining the apache logs for
+ error messages that can be corrected. The log files are stored in
+ /var/log/apache2 and are generally named after the website.</p>
+ <h2>Configuring the guest VM</h2>
+ <p>The guest VM should already be set up appropriately. These steps
+ are provided for reference and updates.</p>
+ <h3>Set up virtualbox guest additions for the VM</h3>
+ <p>** note for v001 of cakelampvm: the below steps are still needed on the
+ shipped image.</p>
+ <p>This procedure is needed if the guest provides an older or incompatible
+ version of the guest additions (which have already been installed on the
+ guest vm). It may also be necessary when a new version of the guest
+ additions becomes available.</p>
+ <ol>
+ <li>To install the guest additions, open the guest VM and have its window
+ in focus.</li>
+ <li>Choose the "Devices" menu and select "Insert Guest Additions CD
+ Image". This will mount the CD's ISO image on the VM.</li>
+ <li>On the guest VM, it may be necessary to mount the CD image that's now
+ available:<br>
+ sudo mount /dev/sr0 /media/cdrom</li>
+ <li>Since the VM currently has no windowing system installed, one must
+ start the Guest Additions install manually:<br>
+ cd /media/cdrom<br>
+ sudo sh VBoxLinuxAdditions.run</li>
+ <li>This should install the guest additions.</li>
+ </ol>
+ <h3>Set up network adapters on guest VM</h3>
+ <p>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:</p>
+ Adapter 1:<br>
+ Attached to: Host-only Adapter<br>
+ Name: vboxnet0 <br>
+ <p>Adapter 2:<br>
+ Attached to: Nat Network<br>
+ Name: NatNetwork</p>
+ <p>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:</p>
+ <pre>source /etc/network/interfaces.d/*<br><br>auto lo<br>iface lo inet loopback<br><br>auto enp0s3<br>iface enp0s3 inet static<br> address 10.28.42.20<br> netmask 255.255.255.0<br> network 10.28.42.0<br> broadcast 10.28.42.255<br> dns-domain cakelampvm.com<br> dns-search cakelampvm.com<br> dns-nameservers 127.0.0.1 8.8.8.8</pre>
+ <pre>auto enp0s8</pre>
+ <pre>iface enp0s8 inet dhcp</pre>
+ <p> </p>
+ <h2>Handy Techniques</h2>
+ <h3>Get the network address on the guest vm</h3>
+ <p>Run this command: ifconfig</p>
+ <p>In the results, look for "inet addr". There may be more than one,
+ if there are multiple network interfaces.</p>
+ <h3>How to cleanly reboot or shut down the guest VM</h3>
+ <p>When you've got the DNS and everything integrated, these commands will
+ manage the vm's state:</p>
+ <p>First, log into the guest VM: ssh developer@cakelampvm.com</p>
+ <p>Then, reboot the guest VM: sudo reboot</p>
+ <p>Or, halt the guest VM: sudo shutdown -h now</p>
+ <p>Using these commands is better than just cycling the power from the
+ virtualbox control panel.</p>
+ <h2>Notes on building the Cake Lamp VM</h2>
+ <p>This is all work that should already have been done. It is
+ mentioned here just as breadcrumbs for a future vm builder.</p>
+ <ul>
+ <li>Downloaded and installed virtualbox for host computer (where the vm
+ image will be built).</li>
+ <li>Downloaded ubuntu server 16.04 iso.
+ (https://www.ubuntu.com/download/server)</li>
+ <li>Created a new vm in virtualbox, telling it to start from the ubuntu
+ server iso.</li>
+ <li>Installed LAMP stack on guest VM. Some help here:
+ http://howtoubuntu.org/how-to-install-lamp-on-ubuntu</li>
+ <li>Configured CAKE on the guest VM. Useful link:
+ https://askubuntu.com/questions/628938/how-to-install-cakephp-in-ubuntu-14-04</li>
+ <li>Configured the two network adapters as needed (one for host-only
+ network and one for nat network). Here's some info about
+ virtualbox networking with two adapters similar to our setup:
+https://askubuntu.com/questions/293816/in-virtualbox-how-do-i-set-up-host-only-virtual-machines-that-can-access-the-in<br>
+ </li>
+ <li>Installed and configured Samba service for the guest VM. The
+ main config file lives in "/etc/samba/smb.conf". Some pointers
+ here:
+https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated%2C%20Simple%20and%20Brief%20Way%21</li>
+ </ul>
+ <p><br>
+ </p>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta content="text/html; charset=windows-1252" http-equiv="content-type">
+ <title>cakelampvm.com official internet site (NOT the local virtual machine)</title>
+ </head>
+ <body>
+ <div style="text-align: center;"><img alt="uh oh red exclamation" src="images/red_exclamation_mark_icon_256.png" width="140" height="140">
+ <img alt="x marks a bad spot" src="images/red_x_1194985626525719339tasto_11_architetto_fran_01.svg.med.png" width="140" height="140">
+ <img alt="uh oh red exclamation" src="images/red_exclamation_mark_icon_256.png" width="140" height="140"></div>
+ <h1 style=" text-align: center;">cakelampvm.com REAL INTERNET site</h1>
+ <h2 style=" text-align: center;"> </h2>
+ <h2 style=" text-align: center;"> ★★ If you are running the cakelampvm, ★★<br>
+ ★★ then it is not yet configured properly. ★★ </h2>
+ <h3 style=" text-align: center;">This is the cakelampvm.com domain that is
+ actually <span style="font-weight: bold;">on the internet</span>.</h3>
+ <h4 style=" text-align: center;">Official cakelampvm setup guide: <a
+ target="_blank" href="docs/manual/cakelampvm_guide_v002.html">The
+ cakelampvm.com VM: Configuration and Usage</a></h4>
+ <div style="text-align: center;"><img alt="uh oh red exclamation" src="images/red_exclamation_mark_icon_256.png" width="140" height="140">
+ <img alt="x marks a bad spot" src="images/red_x_1194985626525719339tasto_11_architetto_fran_01.svg.med.png" width="140" height="140">
+ <img alt="uh oh red exclamation" src="images/red_exclamation_mark_icon_256.png" width="140" height="140">
+</div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta content="text/html; charset=windows-1252" http-equiv="content-type">
+ <title>cakelampvm.com served by your local virtual machine!</title>
+ </head>
+ <body>
+ <div style="text-align: center;"><img alt="yay, green exclaimed" src="images/green_globe_exclamation_point_570.jpg"
+ height="140" width="140"> <img alt="you're in the right place, and dns is being hosted by your local cakelampvm.com virtual machine"
+ src="images/green-check-mark-in-circle-hi.png" height="140" width="140">
+ <img alt="yay, green exclaimed" src="images/green_globe_exclamation_point_570.jpg"
+ height="140" width="140"></div>
+ <h1 style=" text-align: center;">Yes!<br>
+ You're on the cakelampvm.com virtualized site!</h1>
+ <h2 style=" text-align: center;"> </h2>
+ <h2 style=" text-align: center;"> ★★ Your cakelampvm virtual machine seems
+ to be ★★<br>
+ ★★ successfully overriding this domain (and any ★★<br>
+ ★★ other sites you have added to host on the vm). ★★ </h2>
+ <h3 style=" text-align: center;">This is the cakelampvm.com domain that is
+ served from your cakelampvm virtual machine<br>
+ <span style="font-style: italic;">(as long as browser URL bar actually
+ says "cakelampvm.com" or "www.cakelampvm.com").</span></h3>
+ <h4 style=" text-align: center;">Official cakelampvm setup guide: <a target="_blank"
+ href="docs/manual/cakelampvm_guide_v002.html">The cakelampvm.com VM:
+ Configuration and Usage</a></h4>
+ <div style="text-align: center;"><img alt="yay, green exclaimed" src="images/green_globe_exclamation_point_570.jpg"
+ height="140" width="140"> <img alt="you're in the right place, and dns is being hosted by your local cakelampvm.com virtual machine"
+ src="images/green-check-mark-in-circle-hi.png" height="140" width="140">
+ <img alt="yay, green exclaimed" src="images/green_globe_exclamation_point_570.jpg"
+ height="140" width="140">
+ </div>
+ </body>
+</html>
Note that this actually modifies ~/.bashrc. This step is only needed once.
# bash /opt/feistymeow.org/feisty_meow/scripts/core/connect_feisty_meow.sh
+| For the root user, you can pass a flag '--root' to the connect_feisty_meow
+| script. This will add an alias for 'feistyme' which loads the feisty meow
+| scripts on demand (instead of automatically upon login).
+
Load the script environment into the current shell. This can be done for
any new shell. This is idempotent, so it does no harm to run it again.
Note that you should not need this step if you connected feisty meow to
# notes are individual files of tasks, usually, although some are combined.
analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes (externalities)"
+# web site development tasks.
+analyze_hierarchy_and_report ~/cloud/webular "web design (ideas and tasks)"
+
# feisty notes are about feisty meow(r) concerns ltd codebase development.
analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes (mondo coding)"
# some important retreads on aliases that provide a sudo-ized version of other scripts.
define_yeti_alias snarf_linux_config="sudo -E PERLLIB=\$PERLLIB perl \$FEISTY_MEOW_SCRIPTS/archival/snarf_linux_config.pl"
-define_yeti_alias standup="sudo bash \"$FEISTY_MEOW_SCRIPTS/site_avenger/standup.sh\""
+#no, does its own sudo wrangling.edefine_yeti_alias standup="sudo bash \"$FEISTY_MEOW_SCRIPTS/site_avenger/standup.sh\""
#hmmm: some magma intrusions from the fred customizations...
-define_yeti_alias revamp_web_permissions="sudo bash \"$FEISTY_MEOW_SCRIPTS/customize/fred/scripts/cakelampvm/revamp_web_permissions.sh\""
+define_yeti_alias revamp_cakelampvm="sudo bash \"$FEISTY_MEOW_SCRIPTS/site_avenger/revamp_cakelampvm.sh\""
##############
##############
-# remove the fredization macro if it was defined, helping to avoid running
-# the shell scripts twice for users like root that don't always load this
-# stuff.
-unalias fredme &>/dev/null
-unalias feistyme &>/dev/null
+# remove the "fredization" or "feistymeowization" macros if they're defined,
+# which reduces the chance of loading the shell environment twice for users
+# like root that don't load feisty meow automatically.
+unalias fredme feistyme &>/dev/null
##############
>> "$HOME/.bashrc"
echo "Feisty Meow is now configured in '~/.bashrc' for standard users."
else
- # stuff the root user init file into .bashrc. this one doesn't automatically load
- # feisty meow. instead, it provides a fredme macro to load the feisty meow scripts.
- # fredme comes from the main author being fred t. hamster. we have since added a
- # feistyme macro too, to be less personalized...
+ # stuff the root user init file into .bashrc. this one doesn't
+ # automatically load the feisty meow scripts. instead, there is a macro
+ # (uhh, an alias) that loads the feisty meow scripts. the 'fredme' macro
+ # comes from the main author of feisty meow, named fred t. hamster. we
+ # have since added a 'feistyme' macro too, to be slightly less
+ # idiosyncratic, as if that were possible.
cat $FEISTY_MEOW_APEX/infobase/feisty_inits/dot.bashrc-root |
sed -e \
"s?FEISTY_MEOW_APEX=\".*\"?FEISTY_MEOW_APEX=\"$FEISTY_MEOW_APEX\"?" \
+++ /dev/null
-#!/bin/bash
-
-# fixes the cakelampvm permissions according to the way.
-
-##############
-
-if [[ $EUID != 0 ]]; then
- echo "This script must be run as root or sudo."
- exit 1
-fi
-
-##############
-
-export WORKDIR="$( \cd "$(\dirname "$0")" && \pwd )" # obtain the script's working directory.
-export FEISTY_MEOW_APEX="$( \cd "$WORKDIR/../../../../.." && \pwd )"
-
-source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"
-
-##############
-
-# fix up the main web storage.
-chown -R www-data:www-data /var/www
-group_perm /var/www
-
-##############
-
-# set up access on some important folders for the developer user.
-chown -R developer:developer /home/developer
-harsh_perm /home/developer/.ssh
-chown -R developer:developer /opt/feistymeow.org
-group_perm /opt/feistymeow.org
-chown -R developer:developer /etc/apache2 /etc/bind
-group_perm /etc/apache2 /etc/bind
-
-##############
-
-# fix perms for fred user.
-chown -R fred:fred /home/fred /home/archives/stuffing
-harsh_perm /home/fred/.ssh
-
-##############
-
#!/bin/bash
-# this config file provides the default values for the variables used in our site management scripts.
+# provides the default values for the variables used in our site management scripts.
+
+# config files for site avenger apps usually override nothing, since we
+# auto-construct the app name and domain.
+# if they do need to override anything, they can just specify replacement
+# values for the variables in this file.
####
# basic information that is constant for all site avenger sites.
-APPLICATION_DIR="$HOME/apps"
-DEFAULT_REPOSITORY_ROOT="git@github.com:kwentworth"
-CHECKOUT_DIR_NAME="avenger5"
-
-####
-
-# config files for site avenger apps usually override nothing, since we
-# auto-construct the app name and domain. but if they do need to override
-# anything, it will be below this point in the file.
-# the derived config file should include the basic configs like so:
-#
-# source "$WORKDIR/config/default.app"
+export APPLICATION_DIR="$HOME/apps"
+export DEFAULT_REPOSITORY_ROOT="git@github.com:kwentworth"
+export CHECKOUT_DIR_NAME="avenger5"
####
# deployment information for the application / site.
-APPLICATION_NAME="${app_dirname}"
+export APPLICATION_NAME="${app_dirname}"
echo app name was computed as $APPLICATION_NAME
# change this if the site is on the "real" internet.
-DOMAIN_NAME="${app_dirname}.vm"
+export DOMAIN_NAME="${app_dirname}.vm"
echo domain name was computed as $DOMAIN_NAME
-REPO_NAME="${app_dirname}.git"
+export REPO_NAME="${app_dirname}"
echo repo name was computed as $REPO_NAME
-THEME_NAME="$(capitalize_first_char "${app_dirname}.git")"
+export THEME_NAME="$(capitalize_first_char "${app_dirname}")"
echo theme name was computed as $THEME_NAME
# a special override for the mapsdemo site, which we want to put in as
# a subdomain of the cakelampvm domain.
-source "$WORKDIR/config/default.app"
+export DOMAIN_NAME="${APPLICATION_NAME}.cakelampvm.com"
-DOMAIN_NAME="${APPLICATION_NAME}.cakelampvm.com"
+echo "*** overrode domain name as: $DOMAIN_NAME"
# start with. The concept of the theme comes from cakephp.
export WORKDIR="$( \cd "$(\dirname "$0")" && \pwd )" # obtain the script's working directory.
+export FEISTY_MEOW_APEX="$( \cd "$WORKDIR/../.." && \pwd )"
+
+source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"
############################
function print_instructions()
{
echo
- echo "$(basename $0 .sh) [app dirname] [repository] [theme name]"
+ echo "$(basename $0 .sh) [app dirname] [repository] [theme name] "
+#[user name]
echo
echo "All parameters are optional, and intelligent guesses for them will be made."
echo
echo "app dirname: The folder where the app will be stored."
echo "repository: The name of the git repository (short version, no URL)."
echo "theme name: The name to use for the cakephp theme."
+# echo "user name: The name of the user to chown the checkout to."
echo
exit 0
}
app_dirname="$1"; shift
repo_name="$1"; shift
theme_name="$1"; shift
+#user_name="$1"; shift
+
+#echo "*** user name is $user_name"
if [ "$app_dirname" == "-help" -o "$app_dirname" == "--help" ]; then
print_instructions
echo "Theme name: $theme_name"
sep
+echo in powerup before update repo with:
+var CHECKOUT_DIR_NAME DEFAULT_REPOSITORY_ROOT
+
# this should set the site_store_path variable if everything goes well.
update_repo "$full_app_dir" "$CHECKOUT_DIR_NAME" "$DEFAULT_REPOSITORY_ROOT" "$repo_name"
test_or_die "Updating the repository storage directory"
sep
+#if [ ! -z "$user_name" ]; then
+# echo "Chowning the apps folder to be owned by: $user_name"
+##hmmm: have to hope for now for standard group named after user
+# chown -R "$user_name:$user_name" "$APPLICATION_DIR"
+# test_or_die "Chowning $APPLICATION_DIR to be owned by $user_name"
+#fi
+
+sep
+
+
echo "Finished powering up the site in '${app_dirname}'."
--- /dev/null
+#!/bin/bash
+
+# fixes the cakelampvm permissions according to the way.
+
+##############
+
+if [[ $EUID != 0 ]]; then
+ echo "This script must be run as root or sudo."
+ exit 1
+fi
+
+##############
+
+export WORKDIR="$( \cd "$(\dirname "$0")" && \pwd )" # obtain the script's working directory.
+export FEISTY_MEOW_APEX="$( \cd "$WORKDIR/../.." && \pwd )"
+
+source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"
+
+##############
+
+# fix up the main web storage.
+chown -R www-data:www-data /var/www
+group_perm /var/www
+
+##############
+
+# set up access on some important folders for the developer user.
+chown -R developer:developer /home/developer
+harsh_perm /home/developer/.ssh
+chown -R developer:developer /opt/feistymeow.org
+group_perm /opt/feistymeow.org
+chown -R developer:developer /etc/apache2 /etc/bind
+group_perm /etc/apache2 /etc/bind
+
+##############
+
+# fix perms for fred user.
+chown -R fred:fred /home/fred /home/archives/stuffing
+harsh_perm /home/fred/.ssh
+
+##############
+
export SITE_MANAGEMENT_CONFIG_FILE
if [ -z "$SITE_MANAGEMENT_CONFIG_FILE" ]; then
SITE_MANAGEMENT_CONFIG_FILE="$WORKDIR/config/default.app"
+ echo "Site management config file was not set. Using default:"
+ echo " $SITE_MANAGEMENT_CONFIG_FILE"
fi
# load in at least the default version to get us moving.
fi
}
+# tries to find an appropriate config file for the application.
+function locate_config_file()
+{
+ local app_dirname="$1"; shift
+
+ local configfile="$WORKDIR/config/${app_dirname}.app"
+echo hoping config file would be: $configfile
+ if [ ! -f "$configfile" ]; then
+ # this is not a good config file. we can't auto-guess the config.
+ echo -e "
+There is no specific site configuration file in:
+ $configfile
+We will continue onward using the default and hope that this project follows
+the standard pattern for cakephp projects."
+ # we'll pull in the default config file we set earlier; this will
+ # reinitialize some variables based on the app name.
+ else
+ # they gave us a valid config file. let's try using it.
+ export SITE_MANAGEMENT_CONFIG_FILE="$configfile"
+ fi
+
+ # try to load the config.
+ source "$SITE_MANAGEMENT_CONFIG_FILE"
+ test_or_die "loading site management configuration from: $SITE_MANAGEMENT_CONFIG_FILE"
+
+}
+
# this function will seek out top-level directories in the target directory passed in.
# if there is only one directory, then it is returned (in the app_dirname variable).
# otherwise, the user is asked which directory to use.
test_or_die "Testing application folder: $app_dirname"
echo "Application folder is: $app_dirname"
-
- local configfile="$WORKDIR/config/${app_dirname}.app"
- if [ ! -f "$configfile" ]; then
- # this is not a good config file. we can't auto-guess the config.
- echo -e "
-There is no specific site configuration file in:
- $configfile
-We will continue onward using the default and hope that this project follows
-the standard pattern for cakephp projects."
- # we'll pull in the default config file we set earlier; this will
- # reinitialize some variables based on the app name.
- else
- # they gave us a valid config file. let's try using it.
- SITE_MANAGEMENT_CONFIG_FILE="$configfile"
- fi
-
- # try to load the config.
- source "$SITE_MANAGEMENT_CONFIG_FILE"
- test_or_die "loading site management configuration from: $SITE_MANAGEMENT_CONFIG_FILE"
}
# ensures that the app directory name is valid.
mkdir "$combo"
test_or_die "Making application directory when not already present"
fi
+
+ locate_config_file "$dir"
}
# eases some permissions to enable apache to write log files and do other shopkeeping.
local repo_root="$1"; shift
local repo_name="$1"; shift
+echo here are parms in update repo:
+var full_app_dir checkout_dirname repo_root repo_name
+
# forget any prior value, since we are going to validate the path.
unset site_store_path
print_instructions
fi
-if [[ $EUID != 0 ]]; then
- echo "This script must be run as root or sudo."
- exit 1
-fi
+#we will require sudo later.
+#if [[ $EUID != 0 ]]; then
+# echo "This script must be run as root or sudo."
+# exit 1
+#fi
source "$WORKDIR/shared_site_mgr.sh"
test_app_folder "$APPLICATION_DIR" "$app_dirname"
fi
-add_domain "$DOMAIN_NAME"
+#echo "!! domain being added is: $DOMAIN_NAME"
+
+sudo bash "$FEISTY_MEOW_SCRIPTS/system/add_domain.sh" "$DOMAIN_NAME"
test_or_die "Setting up domain: $DOMAIN_NAME"
sep
-add_apache_site "$APPLICATION_NAME" "$DOMAIN_NAME"
+sudo bash "$FEISTY_MEOW_SCRIPTS/system/add_apache_site.sh" "$APPLICATION_NAME" "$DOMAIN_NAME"
test_or_die "Setting up apache site for: $APPLICATION_NAME"
sep
+#echo about to do powerup with: app="$APPLICATION_NAME" repo="$REPO_NAME" theme="$THEME_NAME"
+#echo default repo is "$DEFAULT_REPOSITORY_ROOT"
+
powerup "$APPLICATION_NAME" "$REPO_NAME" "$THEME_NAME"
+# pass the real user name who should own the files.
+# "$(logname)"
sep
echo "
-Finished standing up the full domain and site in:
-${app_dirname}"
+Finished standing up the full domain and site for: ${app_dirname}
+The domain name is: $DOMAIN_NAME
+"
# auto-find the scripts, since we might want to run this as sudo.
export WORKDIR="$( \cd "$(\dirname "$0")" && /bin/pwd )" # obtain the script's working directory.
-source "$WORKDIR/../core/launch_feisty_meow.sh"
+export FEISTY_MEOW_APEX="$( \cd "$WORKDIR/../.." && \pwd )"
+
+source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"
# some convenient defaults for our current usage.
Include /etc/apache2/conf-library/rewrite-enabling.conf
</VirtualHost>
" >"$site_config"
+
+ chown "$(logname):$(logname)" "$site_config"
+ test_or_die "setting ownership on: $site_config"
}
# turns on the config file we create above for apache.
#
# Author: Chris Koeritz
+export WORKDIR="$( \cd "$(\dirname "$0")" && \pwd )" # obtain the script's working directory.
+export FEISTY_MEOW_APEX="$( \cd "$WORKDIR/../.." && \pwd )"
+
+source "$FEISTY_MEOW_APEX/scripts/core/launch_feisty_meow.sh"
+
# some defaults that are convenient for current purposes.
-# hmmm: these would need to be parameterized somehow for this script to become really general.
+
+# hmmm: !!! these would need to be parameterized somehow for this script to become really general.
# in our scheme, the single IP address that all our domains map to.
IP_ADDRESS="10.28.42.20"
# the email address (where first dot is replaced by @) for the administrator of the domain.
-SERVER_ADMIN="fred.cakelampvm.com"
+SERVER_ADMIN="developer.cakelampvm.com"
# the name of the name server for the new domains (should already be configured).
MAIN_NAME_SERVER="ns.cakelampvm.com"
# the name of the mail server for a new domain (should already be configured).
${domain_name}. IN A ${IP_ADDRESS}
IN HINFO \"linux server\" \"${DISTRO}\"
" >"$domain_file"
+
+ # our personalized configuration approach wants the real owner to own the file.
+ chown "$(logname):$(logname)" $domain_file
+ test_or_die "setting ownership on: $domain_file"
}
# hooks up a new config file into bind's list of zones.
////////////////////////////////////////////////////////////////////////////
" >> /etc/bind/named.conf.local
+
+ # keep ownership for the real user.
+ chown "$(logname):$(logname)" /etc/bind/named.conf.local
+ test_or_die "setting ownership on: /etc/bind/named.conf.local"
+
}
# adds a new subdomain under a containing domain.
IN HINFO \"linux server\" \"${DISTRO}\"
" >> /etc/bind/${containing_domain}.conf
+ # keep ownership for real user.
+ chown "$(logname):$(logname)" "/etc/bind/${containing_domain}.conf"
+ test_or_die "setting ownership on: /etc/bind/${containing_domain}.conf"
}
function restart_bind()
then try openshot. it also supports simple saving with different quality levels, which
lets you drop a bunch of size at the expense of the picture. sometimes needed.
+---------------------------
+music collection management
+---------------------------
+
+dupeguru:
+found this to be pretty helpful in finding my duplicate songs. it is able to analyze
+when the files are the same, even if their names don't match.
+check: did it even compare by metadata? not remembering currently.
+
+fdupes:
+another useful tool for finding duplicate tracks in a music collection, but relies on exact
+matches in the names(?). was not so powerful as dupeguru, but still useful.
+
+
+
+
projects / feisty_meow.git / commitdiff
