Our copy of squeaksource.com is now running in its own ssdotcom account on box3.squeak.org on port 8888, with a supervisory script that restarts the image in the event of failure. I fixed a problem with reloading the repository on image restart (the one that caused email spam storms on restart), and I have the hourly automatic image process working again (it needed to do the image save from the UI thread).
Everything seems to be working at this point, so I now need to figure out how to bring this up under Apache behind port 80. I will have limited free time over the next week, so this may not happen for a few more days. Meanwhile, if anyone wants to put some load on http://box3.squeak.org:8888, please do so. Extra credit to anyone who can break it :-)
Dave
On Sun, Sep 15, 2013 at 06:05:19PM -0400, David T. Lewis wrote:
An update on the SqueakSource move:
I have moved our copy of squeaksource.com from my personal user account on box3.squeak.org to a newly created account ssdotcom on the same server. All files are now owned by ssdotcom, and the server image is running from a supervisory script ~ssdtocom/SqueakSource/runimage.sh that will restart the image in the event of failure (although that it is not yet wired in to the system start scripts).
Our copy of squeaksource.com has been running without problems on http://box3.squeak.org:8888 (albeit with no load) for about three weeks, so I have moved it to the dedicated ssdotcom account, and I will continue to keep it active there until we can finalize the move.
The most important thing I need to do next is get it running behind Apache on port 80. Unfortunately I have no real experience setting up Apache, so there is a chance that I may screw things up build.squeak.org (which runs on box3 also), so apologies in advance if that happens.
I am keeping some notes in our admin log on box3 /root/admin-log.txt, so if anything looks broken please look there to see how I broke it.
Dave
On Mon, Aug 26, 2013 at 08:38:01AM -0400, David T. Lewis wrote:
FYI, I am currently consuming a large amount of disk space on build.squeak.org for testing squeaksource migration. Let me know if this causes any problems.
Over the weekend I was able to bring up a full copy of squeaksource.com on my home PC. I worked around a couple of problems and got the in-image repository updated (so it won't spam the mailing lists after a SqueakSource restart), and I disabled mail delivery. I then copied the entire thing to my user directory on build.squeak.org.
This is just a temporary test and is not yet properly installed, but anyone interested can connect to it on http://build.squeak.org:8888. VNC is running on display 1, please ask if you would like the password (this list is archived so I won't mention the password here).
I do need some help to identify the right location for the real installation. Will this be on box4? If so, can I please get an account?
Thanks, Dave
On Sat, Aug 24, 2013 at 01:12:22PM -0400, David T. Lewis wrote:
On Fri, Aug 23, 2013 at 09:50:08PM -0400, David T. Lewis wrote:
We now have access to a complete snapshot copy of SqueakSource. I am in the process of retrieving the files to my personal PC (not yet complete, I'm still trying to get a clean copy of one large 15GB file), and I will now need a place to put them on squeak.org.
I need some help to proceed. We need a server with 20 to 30 GB of file space available for the SqueakSource files, and with memory and CPU resources similar to whatever we are currently doing for source.squeak.org.
Can someone help, either by giving me access to an existing server, or by letting me know what is available? I will need a user account (lewis) similar to my current account on build.squeak.org, and I will need sudo privilege to set up an account for squeaksource and to set up the runtime environment.
In addition it would be helpful if I could get enough access to the source.squeak.org server so that I can look at it and figure out how that server is configured. Even better would be if the source.squeak.org server has enough capacity (mainly disk space) to also host squeaksource, in which case we can put both of them on the same server.
I would like to do this as soon as possible (tomorrow perhaps?) so any assistance and pointers will be gratefully received.
I now (finally) have a complete copy of the SqueakSource files sitting on my hard drive here in Ann Arbor, Michigan. Here is what we have:
-rw-r--r-- 1 lewis users 16341844652 2013-08-24 04:21 Squeaksource-projects-22-8-2013.tar -rw-r--r-- 1 lewis users 5558656 2013-08-23 08:20 Squeak-3.9-8-SqueakSource.app.tar -rw-r--r-- 1 lewis users 167474616 2013-08-23 08:19 squeaksource.image -rw-r--r-- 1 lewis users 15721301 2013-08-23 08:18 squeaksource.changes -rw-r--r-- 1 lewis users 718 2013-08-23 08:18 squeaksource.com -rw-r--r-- 1 lewis users 1686 2013-08-23 08:17 Workspace.text -rw-r--r-- 1 lewis users 14542313 2013-08-23 08:17 SqueakV3.sources
After unpacking the files (these are compressed tars), the total disk usage is a bit over 16 GB:
lewis@linux-jh8m:~/squeak/SS/TransitionToSqueakDotOrg/WORK> du -s * 21564 Squeak-3.9-8-SqueakSource.app 15356 squeaksource.changes 4 squeaksource.com 163552 squeaksource.image 14204 SqueakV3.sources 16401280 ss 4 Workspace.text
So a server with 20GB working space is sufficient, and 30GB would provide comfortable headroom.
Dave