To install, follow these instructions.
For information on using builderCI, see the project README.
To install, follow these instructions.
Today GemTalk Systems announced the acquisition of the GemStone/S platform from VMware. Before anyone gets their knickers in a knot, this is a good thing:
The entire Smalltalk team is moving intact from VMware to GemTalk Systems and I want to emphasize that both GemTalk Systems and VMware are being very generous and fair during the transition.
We are re-locating to another suite in the same office complex, up the stairs from our old location.
We are not keeping our old name (GemStone Systems) and we are not keeping the gemstone.com domain. I guess one can’t expect everything. I have also been assured that the URLs for GemSource and SS3 will continue to function for at least a year (if not longer).
From a technical perspective GemStone/S has thrived at VMware, the engineering team has been pretty much left alone and we were given all of the necessary resources to “get the job done”. From a technical and personal perspective, I have been very happy with my tenure at VMware.
On the business side, I would say that GemStone/S foundered a bit. The GemStone/S product never got fully integrated into the VMware universe (unlike GemFire), but then the GemStone/S product was not the primary focus of the original VMware acquisition.
GemTalk Systems is a privately held company led by Dan Ware. Prior to the VMware acquisition in 2010, Dan had been an executive with GemStone Systems for 17 years. For most of those years Dan was in charge of the Sales organization, so Dan knows the GemStone/S customer base, very well.
Dan and the investors love GemStone/S and want to see it continue to thrive.
This quote bears repeating:
and from our transition FAQ:
Our core technology will be Smalltalk-based products, but they can provide infrastructure in other environments. We will continue to support GemBuilder for Java, and we will be revisiting MagLev for Ruby and GLASS for Seaside. New initiatives into other development areas are possible.
Frankly, I don’t think that I could have imagined a better home for GemStone/S.
WorldPulse is application for the iPhone and iPad, that shows live accurate cloud cover data, the day/night terminus, night lights, and in 2.0 weather data from all the weather stations in the world.
In John’s presentation:
GemStone/S 64 188.8.131.52 was released August 28, 2012. This release fixes a number of bugs and we recommend all 3.x customers use this release. Be sure to review the release notes and install guides for this release.
GemStone 184.108.40.206 ships with GLASS 1.0-beta.8.7.2 pre-installed in
$GEMSTONE/bin/extent0.seaside.dbf, but there are a few minor issues that show up as test failures. GLASS 1.0-beta.8.7.3 has been released to address those issues.
You should update to GLASS 1.0-.8.7.3 when you start using GemStone 220.127.116.11.
A One-Click GemTools 1.0-beta.8.7 for GemStone 18.104.22.168 can be obtained from the seaside.gemstone.com downloads page or you can download GemTools 1.0-beta.8.7 for Gemstone/S 22.214.171.124 all platforms directly.
You can build a custom GemTools image by following these steps on the glass db wiki.
Seaside 126.96.36.199 should be used with GemStone/S 3.1.x. There are a few critical bug fixes included in that version.
You can download the binaries from ftp://ftp.gemstone.com/pub/GemStone64/188.8.131.52, use the installGemStone.sh script to download and install GemStone/S on your machine (highly recommended), or visit seaside.gemstone.com downloads page.
To use the installGemStone.sh script, your supply the GemStone version number as an argument to the script. The following downloads and installs the GemStone/S 184.108.40.206 release:
If you are upgrading from GemStone/S 2.x, then be sure to read my post on GemStone/S 3.1.0 first.
Let’s say that you’ve got Seaside 220.127.116.11 installed in your GemStone/S 3.1.0 repository. According to the upgrade instructions you will need to define the BootstrapApplicationLoadSpecs for your application. For Seaside 18.104.22.168, that means you’ll run the following topaz script BEFORE running the upgradeSeasideImage.sh script:
The important bits are that you are specifying GLASS 1.0-beta.8.7.3 and specifying the <path to seaside cache repository>. The seaside cache repository is a directory on your machine where you’ve stashed all of the mcz files needed to reload Seaside 22.214.171.124 into your upgraded repository. You can use the following script to create the seaside cache repository:
Finally, as noted in Issue 354, you need to reload the ConfigurationOfGLASS and ConfgurationOfSeaside30: