The long awaited server switch finally took place today. We changed the Propel server, domain name, and website design, mostly to solve the speed and stability problems of the previous host. The new Propel website is http://www.propelorm.org
, and you're welcome to visit it anytime. It still has few rough edges, but with your feedback and a few days of polish, it will be almost perfect!
The new website emphasizes the installation and documentation sections. It's still based on Trac, but we managed to make Trac a little more discreet in the documentation pages. Of course, all the Trac history, tickets and milestones from the phpdb.org
server were imported, and you will find the ticketing, source and timeline under the 'Dev
' section. We couldn't import the old user accounts from the previous site, but the good news is that it is now easy to register directly in the 'Dev' section. If you had a user account, open a new account at propelorm.org
with the same username, and you should receive alerts on the tickets you've opened. If you had commit access, you'll have to ask me again.
The subversion server has also moved. The old server, available at http://svn.phpdb.org/propel
, is still accessible, but it's now read only, and the next changes won't appear there. The new Propel SVN server address is http://svn.propelorm.org
. It has been synchronized with the previous server. You'll need to change your svn externals, or relocate your existing checkouts:
The PEAR server will remain at the previous address for a short period of time. We'll soon offer a pear channel at pear.propelorm.org
The old server should redirect most of the documentation and ticket pages to the new server, page to page. However, search engines may take time to update their index, so mentioning the new Propel website url in your own sites may speed up re-crawl.
I'd like to thank Veikko Mäkinen, for giving the domain name and designing the new website, and Benjamin Boerngen-Schmidt, for providing the server, adapting the design to Trac, transferring all the data from the old server, and administering the new server.
Of course, your feedback is welcome!