Categories
- Databases (12)
- MySQL (8)
- Oracle (4)
- PostgreSQL (3)
- SQL Server (3)
- SQLite (1)
- General Info (8)
- Hardware (7)
- Hosted 64-bit Software (22)
- Lightning Plug-In (3)
- Xine RPMs (20)
- Linux (22)
- Audio / Video (3)
- Internet Apps (11)
- Office Productivity (4)
- Printing (1)
- Red Hat / Fedora (3)
- Samba (1)
- White Box (3)
- Wine (5)
- Wireless Support (8)
- Programming (26)
- C# / .NET (4)
- Mono (2)
- C++ (1)
- JavaScript (1)
- PHP (9)
- SQL (3)
- PL/SQL (1)
- Web Services (1)
- WordPress (13)
- Plug-Ins (7)
- C# / .NET (4)
- Projects (1)
- Security (3)
- Web Servers (6)
- Windows Open Source (1)
- Databases (12)
Archives
- January 2012 (1)
- November 2011 (1)
- October 2011 (2)
- September 2011 (1)
- August 2011 (1)
- May 2011 (1)
- September 2010 (2)
- August 2010 (3)
- March 2010 (1)
- April 2009 (1)
- February 2009 (1)
- January 2009 (1)
- October 2008 (2)
- June 2008 (3)
- May 2008 (1)
- March 2008 (4)
- January 2008 (2)
- December 2007 (2)
- November 2007 (1)
- October 2007 (1)
- September 2007 (2)
- August 2007 (5)
- July 2007 (2)
- June 2007 (2)
- May 2007 (3)
- November 2005 (1)
- August 2005 (2)
- June 2005 (3)
- September 2004 (7)
- August 2004 (2)
- July 2004 (8)
- June 2004 (10)
Monthly Archives: September 2010
40/40 Web Service
The Ethics and Religious Liberty Commission of the Southern Baptist Convention is holding a “40/40 Prayer Vigil,” encouraging prayer through the end of October. While some of the prayer is focused on the upcoming elections, the focus is on national revival. They have produced a prayer guide, which details suggestions for prayer over the course of 40 days, beginning September 20th, and for 40 hours, beginning October 29th at 4pm.
We have created a web service to break this guide up into day and hour-sized chunks. The service is at http://services.djs-consulting.com/FortyForty.asmx. There are several ways to retrieve this information.
- GetDay
This gets one of the 40 days, by the day number. (September 20th is 1, September 21st is 2, etc.) The “day” parameter controls which day is returned. - GetHour
This gets one of the 40 hours, by the hour number (10/29 4pm is 1, 10/29 5pm is 2, etc.) The “hour” parameter controls which hour is returned. - GetDate
This gets one of the 40 days, by the current date. The “date” parameter controls which day is returned. (The time portion may be given, but it is ignored.) - GetTime
This gets one of the 40 hours, by the date/time. The “time” parameter controls which hour is returned. - GetDayHTML, GetHourHTML, GetDateHTML, and GetTimeHTML
This is the same as the above 4 calls, except what is returned is a formatted block of text that can be displayed on a web page.
In all cases, if the day/hour/date/time does not match a valid value for the vigil, a null is returned.
If you’re not interested in consuming the web service, but you’d like to see the suggested prayer each day, the Hoffmantown Prayer site is displaying the days and hours on Mountain Time. This information is on the front page with no login required.
This web service will be discontinued at some point after December 31, 2010.
Tagged erlc, prayer, sbc, web service
Mono / FastCGI Startup Script
We’ve begun running Mono on some DJS Consulting servers to enable us to support the .NET environment, in addition to the PHP environment most of our other applications use. While Ubuntu has nice packages (and Badgerports even brings them up to the latest release), one thing that we were missing was a “conf.d”-type of configuration; my “/applications=” clause of the command was getting really, really long. We decided to see if we could create something similar to Apache / Nginx’s sites-available/sites-enabled paradigm, and we have succeeded!
To begin, you’ll need to create the directories /etc/mono/fcgi/apps-available and /etc/mono/fcgi/apps-enabled. These directories will hold files that will be used define applications. The intent of these directories is to put the actual files in apps-available, then symlink the ones that are enabled from apps-enabled. These files have no name restrictions, but do not put an extra newline character in them. The script will concatenate the contents of that file to create the MONO_FCGI_APPLICATIONS environment variable, which tells the server what applications exist. (The syntax is the same as that for the “/applications=” clause – [domain]:[URL path]:[filesystem path].) Here’s how the site you’re reading now is configured (from the file djs-consulting.com.techblog.conf)…
techblog.djs-consulting.com:/:/path/to/install/base/for/this/site
Finally, what brings it all together is a shell script. This should be named “monoserve” and placed in /etc/init.d. (This borrows heavily from this script, which we used until we wrote this one.) Note the group of variables surrounded by the “make changes here” notes – these are the values that are used in starting the server. They are at the top so that you can easily modify this for your own needs.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 | #!/bin/bash ### BEGIN INIT INFO # Provides: monoserve.sh # Required-Start: $local_fs $syslog $remote_fs # Required-Stop: $local_fs $syslog $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start FastCGI Mono server with hosts ### END INIT INFO PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin DAEMON=/usr/bin/mono NAME=monoserver DESC=monoserver ## Begin -- MAKE CHANGES HERE -- PROGRAM=fastcgi-mono-server2 # The program which will be started ADDRESS=127.0.0.1 # The address on which the server will listen PORT=9001 # The port on which the server will listen USER=www-data # The user under which the process will run GROUP=$USER # The group under which the process will run ## End -- MAKE CHANGES HERE -- # Determine the environment MONOSERVER=$(which $PROGRAM) MONOSERVER_PID="" FCGI_CONFIG_DIR=/etc/mono/fcgi/apps-enabled # Start up the Mono server start_up() { get_pid if [ -z "$MONOSERVER_PID" ]; then echo "Configured Applications" echo "-----------------------" # Construct the application list if the configuration directory exists if [ -d $FCGI_CONFIG_DIR ]; then MONO_FCGI_APPLICATIONS="" for file in $( ls $FCGI_CONFIG_DIR ); do if [ "$MONO_FCGI_APPLICATIONS" != "" ]; then MONO_FCGI_APPLICATIONS=$MONO_FCGI_APPLICATIONS, fi MONO_FCGI_APPLICATIONS=$MONO_FCGI_APPLICATIONS`cat $FCGI_CONFIG_DIR/$file` done export MONO_FCGI_APPLICATIONS echo -e ${MONO_FCGI_APPLICATIONS//,/"\n"} else echo "None (config directory $FCGI_CONFIG_DIR not found)" fi echo # Start the server start-stop-daemon -S -c $USER:$GROUP -x $MONOSERVER -- /socket=tcp:$ADDRESS:$PORT & echo "Mono FastCGI Server $PROGRAM started as $USER on $ADDRESS:$PORT" else echo "Mono FastCGI Server is already running - PID $MONOSERVER_PID" fi } # Shut down the Mono server shut_down() { get_pid if [ -n "$MONOSERVER_PID" ]; then kill $MONOSERVER_PID echo "Mono FastCGI Server stopped" else echo "Mono FastCGI Server is not running" fi } # Refresh the PID get_pid() { MONOSERVER_PID=$(ps auxf | grep $PROGRAM.exe | grep -v grep | awk '{print $2}') } case "$1" in start) start_up ;; stop) shut_down ;; restart|force-reload) shut_down start_up ;; status) get_pid if [ -z "$MONOSERVER_PID" ]; then echo "Mono FastCGI Server is not running" else echo "Mono FastCGI Server is running - PID $MONOSERVER_PID" fi ;; *) echo "Usage: monoserve (start|stop|restart|force-reload|status)" ;; esac exit 0 |
This needs to be owned by root and be executable (“chmod +x monoserve”). You can use “update-rc.d monoserve defaults” to set this to start at boot.
Tagged badgerports, config, fastcgi, mono, script