Joyent Connector - A Symphony Ensemble
A while ago, Joyent announced their Connector Suite as Free + Open, offering free accounts and releasing an open source Ruby on Rails project, with the SVN repository at dev.joyent.net. So, what happened after that? Very little. Apparently, no one was interested.
In my mind, that was a shame. It is a beautiful interface. If only its functionality as an integrated suite of collaboration tools lived up to the promise. A number of issues remain as part of the Maintenance milestone. A few tickets were closed, but little more has happened with the project since.
Having found that the GPL v2 released Joyent Connector is here on GitHub, it would be nice to see this project revived in some way. This repository is my pet project to build the Joyent Connector (or parts of it) as a Symphony CMS Ensemble.
Note: The complete source files are quite large, so have been omitted from this repository. The original Joyent Connector repository can be found here: http://github.com/luke0x/connector/tree/master.
Created with Symphony CMS
- Version: 2.0.6
- Date: 4th August 2009
- Github Repository: http://github.com/symphony/symphony-2/tree/master
Symphony is a
MySQL based CMS that utilises
XSLT as its core
technologies. This repository represents version 2.0.6 and is considered stable.
Visit the forum at http://symphony-cms.com/community/
2.0.5 introduced multiple includable elements, in the Data Source Editor, for a single field. After updating from
2.0.5 or lower, the DS editor will seem to "forget" about any
Textarea fields selected when you are editing existing Data Sources. After updating, you must ensure you re-select them before saving. Note, this will only effect Data Sources that you edit and were created prior to
2.0.5. Until that point, the field will still be included in any front-end XML
Pull from the master branch at
Use the following command to get Extensions up to date:
git submodule init git submodule update
Follow normal updating procedure below from step 2.
Via the old fashioned way
Follow the instructions below if you are updating from Symphony version 2.0 (non Git)
Note: As of 2.0.6, there is no longer a need to backup
update.php, replacing what is already on your server.
If you are updating from a version < 2.0.5, download and install the Debug DevKit and Profile DevKit:
http://yoursite.com/update.phpto complete the update process.
Celebrate by shaving your friend's head for charity!
Clone the git repository to the location you desire using:
git clone git://github.com/symphony/symphony-2.git
Should you wish to make contributions back to the project, fork the master tree rather than cloning, and issue pull requests via github.
The following repositories are included as submodules:
Run the following command to ensure the submodules are cloned:
git submodule update --init
(Optional) If you would like the default theme installed as well, you will need to use the following command from within the Symphony 2 folder you just created:
git clone git://github.com/symphony/workspace.git
Follow normal installation procedure below from step 2.
Via the old fashioned way
Note: You can leave
/workspace out if you do not want the default theme.
This step assumes you downloaded a zip archive from the Symphony website. Upload the following files and directories to the root directory of your website:
Point your web browser at http://yourwebsite.com/install.php and provide details for establishing a database connection and about your server environment.
Jump with both arms up like you're in a car commercial!
Secure Production Sites: Change permissions and remove installer files.
For a smooth install process, change permissions for the
cd /your/site/root chmod 777 symphony . chmod -R 777 workspace
Once successfully installed, change permissions as per your server preferences:
chmod 755 symphony .
Remove installer files (unless you're fine with revealing all your trade secrets):
rm install.php install.sql workspace/install.sql update.php
Dance like it's 1999!