Today the Geego cms is officially released as open source to the public.
Geego puts no restrictions on data structure or final output and has built in image manipulation and multi-language support.
All information can be found at.
Ant Peacocke wrote:
Today the Geego cms is officially released as open source to the public.
Geego puts no restrictions on data structure or final output and has built in image manipulation and multi-language support.
All information can be found at.
...and all my thoughts about picking between Radiant and Mephisto just got blurred further.... Thanks for the effort - I have to add this to my to-evaluate list now!
Cheers Mohit.
Why is a ftp server a requirement for a CMS package?
Ant Peacocke wrote:
It makes the moving of manipulated images and other files that are uploaded by users very straight forward with no hitches in terms of users, groups and permissions.
As most websites allow for updating of files via ftp it means the ftp user and webserver user will play together nicely.
Ant
so you dont actually need an ftp server for Geego?
you could run sftp instead?
or is cms actually tied into using ftp specifically?
Ant Peacocke wrote:
Hi Sean
Here is the code that logs on to the ftp. Note that the host in most cases is localhost (unless you want to store images and other assets on another server). So sftp is not needed from a security point of view. Of course if there was lots of demand and good reasons for using Net::SFTP it could be an option.
require ‘net/ftp’
ftp = Net::FTP.new(ADMIN_FTP_HOST)
ftp.login(ADMIN_FTP_USER, ADMIN_FTP_PASS)
As some more background into why I use ftp for moving files within in a website. If you upload content files from you dev machine to a live machine via ftp then everything is good to go in terms ownership and permissions when Geego needs to overwrite these files and directories with updated content.
Ant