|
|
Sponsored Content
Operating Systems
Solaris
Permissions configuration for web server
Post 302694707 by pn8830 on Friday 31st of August 2012 09:25:06 AM
08-31-2012
Permissions configuration for web server
Greetings!
I have a Solaris workstation that I use for web hosting. It runs SAMP and everything was working good for me until I got a need to add a couple of co-workers to help me with development. I'm trying to find some guidance for how to set up filesystem permissions so everybody would be able to upload their PHP scripts to the workstation without permission issues. By no means I'm a system administrator, just using my limited skillset to get things done
So here is my current setup, I don't really know if it's correct, but I'm in secure environment and it gets things done:
- All web pages are in /www directory (documentRoot).
- Apache runs under webservd user, no shell configured for that user.
- /www belongs to my UNIX login, so I can upload scripts to /www.
- subdirectories in /www that are used for uploads through web page (when user sends file to the server) belong to webservd. And that's cool since they have no PHP scripts in them.
Now the project is growing and I need to add a couple of guys who should be able to upload their PHP scripts to /www.
Here is the couple of ways I figured so far:
1) I give them my password - (not cool, like I did not try to figure right thing out)
2) I create a new UNIX user (upload) and change /www owner to that - (again, the password has to be shared, so it's just a little better)
3) Find a right way to do it (that's pretty much why I'm writing this post)
Any ideas/help to point me in a right direction are greatly appreciated!
Thank You,
PN.
I have a Solaris workstation that I use for web hosting. It runs SAMP and everything was working good for me until I got a need to add a couple of co-workers to help me with development. I'm trying to find some guidance for how to set up filesystem permissions so everybody would be able to upload their PHP scripts to the workstation without permission issues. By no means I'm a system administrator, just using my limited skillset to get things done
So here is my current setup, I don't really know if it's correct, but I'm in secure environment and it gets things done:
- All web pages are in /www directory (documentRoot).
- Apache runs under webservd user, no shell configured for that user.
- /www belongs to my UNIX login, so I can upload scripts to /www.
- subdirectories in /www that are used for uploads through web page (when user sends file to the server) belong to webservd. And that's cool since they have no PHP scripts in them.
Now the project is growing and I need to add a couple of guys who should be able to upload their PHP scripts to /www.
Here is the couple of ways I figured so far:
1) I give them my password - (not cool, like I did not try to figure right thing out)
2) I create a new UNIX user (upload) and change /www owner to that - (again, the password has to be shared, so it's just a little better)
3) Find a right way to do it (that's pretty much why I'm writing this post
)Any ideas/help to point me in a right direction are greatly appreciated!
Thank You,
PN.
|
|
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
my company is considering a new development of our web site, which used to run on Apachi over Solaris.
The company who is going to do this for us knows only about developing it in ASP.
I guess this means we'll have to have another ISS server on NT for these dynamic pages :(
What are... (5 Replies)
Discussion started by: me2unix
5 Replies
2. UNIX for Dummies Questions & Answers
hiya All,
New to this Web site stuff.
Will be installing Fedora's latest O/S (including Apache) - onto a spare PC
Then... Gulp... setting up a Web server.
Designing a Web site using WINDOWS FRONT PAGE 2002:
* Simply easiest/quickiest way to knock up a basic site.
* There won't be... (6 Replies)
Discussion started by: marty 600
6 Replies
3. UNIX for Advanced & Expert Users
Dear All,
i'm very new to this forum, infact just joined today. :o .
i want to install and configure web server on Unix (Sco Openserver 5.0.7). i want any documents or text guide on this.....
awaiting for experts help,
Thanx
Nikhil (1 Reply)
Discussion started by: niksharma
1 Replies
4. OS X (Apple)
this could be a dumb question. i am still becoming used to usr / group permissions.
permissions to place a file into XAMPP/htdocs.
the problem is
that when i go to place a TextMate file into XAMPP/htdocs
a window comes up and states:
Type your password to allow TextMate to make changes.
... (2 Replies)
Discussion started by: cowLips
2 Replies
5. UNIX Desktop Questions & Answers
I do not know if this is the correct place to post this, and I have tried to trawl through relevant articles to fix the issue, but I am stumped.
I have a server, log as root.
var/www is root:root
var/www/website-one is root:root
var/www/website-one/neosmart-stream is root:root
This... (10 Replies)
Discussion started by: LightCastle
10 Replies
LEARN ABOUT DEBIAN
backup-manager-upload
BACKUP-MANAGER-UPLOAD(8) backup-manager-upload BACKUP-MANAGER-UPLOAD(8) NAME
backup-manager-upload - Multiprotocol uploader for backup-manager. SYNOPSIS
backup-manager-upload [options] date DESCRIPTION
backup-manager-upload will upload all the archives generated on the given date to the specified host with either ftp or scp. It's also possible to use this program for uploading data to an Amazon S3 account. Some metadates are available like "today" or "yesterday". REQUIRED ARGS
--mode=transfer-mode Select the transfer mode to use : ftp, scp, or s3. --host=hostname1,hostname2,...,hostnameN Select a list of remote hosts to connect to. --user=username Select the user to use for connection. OPTIONAL ARGS
--password=password Select the ftp user's password (only needed for ftp transfers). --key=path_to_private_key Select the ssh private key file to use when opening the ssh session for scp transfer. Obviously, this is only needed for scp transfer mode. If you don't specify a key file, the user's default private key will be used. --directory=directory Select the location on the remote host where files will be uploaded. Default is /backup/uploads. --bucket=bucket Sets the bucket name for the Amazon S3 service backup into. --root=directory Select the local directory where files are. Default is /var/archives --gpg-recipient=gpg-recipient Select the gpg public key for encryptiong the archives when uploading with the method ssh-gpg. This can be a short or long key id or a descriptive name. The precise syntax is described in the gpg man page. --list Just list the files to upload. --ftp-purge Purge the remote directory before uploading files in FTP mode. --s3-purge Purge the remote directory before uploading files in FTP mode. --ssh-purge Purge the remote directory before uploading files in SSH mode. --verbose Flag to enable verbose mode. date Date pattern to select some files to upload, can be a valid date (YYYYMMDD) or 'today' or 'yesterday'. ERROR CODES
If something goes wrong during an upload, backup-manager-upload will exit with a non null value. In such a case every error messages are sent to STDERR. Here are the possible error codes: bad command line (wrong arguments) : 10 FTP transfer failure : 20 SCP transfer failure : 21 S3 transfer failure : 22 Unknown upload method: 23 SEE ALSO
backup-manager(3) AUTHORS
Alexis Sukrieh - main code and design Brad Dixon - Amazon S3 upload method Jan Metzger - ssh-gpg upload method perl v5.14.2 2012-05-09 BACKUP-MANAGER-UPLOAD(8)