|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Applications Questions about desktops (KDE, Gnome, XFCE, etc.), software applications (configuration, usage, bugs, documentation) |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I saw that too when I was doing a Joomla installation for a client.
I believe it's a feature that's provided by Joomla itself and doesn't involve the Linux authentication. So you would have to read the Joomla doco. Also if you have a firewall, particularly a NAT border firewall, there would probably also be hassles with the port forwarding rules for FTP, which is traditionally problematic for firewalls because it involves two ports, one of which is transmitted inside the command stream at connection establishment time. I didn't enable for my client because I have already set up a more secure sftp (over ssh) system for them. Also the ssh protocol is easy to port forward. |
|
|||
|
Hi,
i usually install joomla extension through the administrator page, extensions>install/uninstall, based on my experience you don't have to use the joomla FTP functionality to install the extensions, just need to give the right permission to the apache user to write on the joomla folders
__________________
"And just as you want men to do to you, you also do to them likewise." Luke 6:31 NKJV |
|
||||
|
I'm installing joomla so I can build and test a website locally and I'll be the only user using it. It will not be open for access from the outside.
Quote:
Quote:
However if I can just assign the necessary permission to Apache then that would be better I think.
__________________
IBM Thinkpad X60s | Intel L2400 1.66Ghz | Mesa DRI Intel 945GM video | 3GB Ram openSuSE 11.1 | Linux 2.6.27.29-0.1 pae i686 | KDE 4.3.3 |
|
|||
|
Hi,
if you are using it for testing, the easiest way is to: Code:
chmod -R 777 yourjoomlafolder
__________________
"And just as you want men to do to you, you also do to them likewise." Luke 6:31 NKJV |
|
|||
|
And for further testing, if you decided to install another joomla site locally, you can also change the default apache user to your current user, by editing /etc/apache2/uid.conf
Code:
User yourusername Group yourusergroup HTH
__________________
"And just as you want men to do to you, you also do to them likewise." Luke 6:31 NKJV |
|
|||
|
Quote:
The ftp upload is only a convenience for people who want to upload using a ftp client. If you have access to the command line, it's just as easy to deposit the files there directly. I do not recommend using mode 777 or changing the uid of the Apache process. |
|
||||
|
Quote:
![]() I'm a little confused now as conflicting advice is being offered. I appreciate the suggestions being offered and clearly there are differeing opinions as to what is correct / acceptable or not. I'm trying to get my head around this. On my local system (localhost), I am unable to install extension, modules, templates, etc through the Joomla web admin page. I cannot make changes to the joomla global site configuration from the joomla web admin page. However, on my host with the live site I can do all those things. So what's different? It seems my local server is not properly configured. It doesn't make sense to have to keep changing permissions to install components or make site configuration changes. The advice is against using mode 777 or changing the uid of Apache. So what is the best way for me to set things so I can use Joomla on localhost without having to manually change permissions to folders and files before wantting to install a component or make a global site config change?
__________________
IBM Thinkpad X60s | Intel L2400 1.66Ghz | Mesa DRI Intel 945GM video | 3GB Ram openSuSE 11.1 | Linux 2.6.27.29-0.1 pae i686 | KDE 4.3.3 |
|
|||
|
You can change the ownership of the Joomla directories and files to wwwrun and then you will be able to modify things through the web interface.
Once your site is bedded down though, it would be additional security to change the ownership away to some other account so that the site cannot be defaced through any latent bug in the Joomla code that takes advantage of being able to write to the installation files. (Yes, web apps do remain a large area of vulnerability for servers.) Any areas that are used for uploads (e.g. pictures, attachments, etc) should however remain writable to Apache. You could also enable the FTP feature, since it shouldn't be an issue if you are accessing it internally. But you still have to make the Joomla directories owned by wwwrun for FTP to be able to write there. I can't tell you how to get the Joomla FTP feature working though, I didn't use it. |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|