Im sorry, I thought that the omega was a complete site setup. I got it installed and successfully installed a pressflow site at mysite.com,
now I am trying to ftp and upload modules to my new created site directory, and I find that It is not configured . I am coming from a shared server, and this is my first time managing my own server. I thought that ftp was autmatically setup with aegir like it was on my old shared manage server, where I can use the user naem and loging and upload to the sites directory.
Its not working like that, so ok I know how to use filezilla to ftp to the root.
I tried uploading a module to here /data/src/001/pressflow-6/sites/all/modules
and that doesnt work...
I cant see the module I uploaded to enable.. any ideas qould be great!
Comments
Well
FTP is pretty insecure. You should use sftp with public key. Anyway my suggestion is for you to find someone who can help you set up the site. It's way too complicated and security hole introducing prone to be done by a neophyte IMHO.
HTH,
António
Thanks for your info. I see
Thanks for your info. I see you are passionate through many of your posts and I look forward to the day I can figure this out enough to learn from your experience. I was expecting a little more of the shared hosting experience with omegas script.Trying to figure out the best way to update modules without using drush, as I useually use dev modules and not the official updates. I think drush only updates official releases....
www.thecenterofthenet.com
http://cn.linkedin.com/in/roberpteatonjr
http://www.facebook.com/robertp.eaton
http://www.alamy.com/stock-photography/6A42F1A1-E40A-48FD-8C7F-FF258A401...
You can use dev versions with
You can use dev versions with drush by doing
drush dl module_name-6.x-2.x-dev. Drush is a timesaver, don't fight it.No, in fact
Drush sometimes updates dev modules also. It depends how it's tagged by the maintainer(s). Like Brian said, is quite easy to force an update download the package and, just to be on the safe side, issue a
drush updbafter downloading the new dev version of your module.I always use, and recommend, running drush from HEAD instead of the current stable release.
Instead of using sftp or scp, I suggest you set up a git workflow with a bare repository acting as "middleman" between your dev site and staging/production. No worries with sftp or SSH issues, since git can use SSH as a transport mechanism.
It also saves time and bandwith since git packs everything. Good luck with your setup. It's really the way to do things. Just do it. With determination in the end you'll have learned a lot and become a better drupaler.