Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

I've got a LAMP server that I want to use as a local web server.

I've got a Windows 7 machine that I want to use as my development machine.

The machines will be on the same LAN (or the Windows box will be VPNed into the LAN).

My questions is, what is the best way of sharing the web root of the LAMP server so that I can edit the files on the remote Windows 7 machine and how do I go about configuring this on the Linux machine? (Fedora 16)

I would like the solution to be as easy to use as possible with preferably no extra steps required to save/edit/upload files from my IDE on my Windows 7 machine.

I'm thinking either a Samba or NFS share are the way to go but I'm concerned I'm going to run into issues with permissions and unix/windows file handling. Is one better than ther other for my use case or is there a better alternative solution?

I'm currently using Windows 7 Professional which doesn't have NFS support but would upgrade to Ultimate which does have NFS support if it's the best solution.

EDIT:

This question does relate to usage in a professional capacity.

Regards the criticism regards version control, the LAMP server is used by myself only for development. Other developers have their own development environments. Mercurial is used for version control and for collaboration between developers.

I therefore believed that this question was valid and within the scope of this site.

share|improve this question
1  
If you're doing this in a professional environment, it's really terrible practice to edit files directly on the web server. You should have a source code repository somewhere that you're committing your code to when there are changes and almost all of them have built-in deployment mechanisms that leverage ssh/rsync in some form or another. If you're not doing this in a professional capacity, then this question is off-topic and you should read our faq – MDMarra Apr 12 '12 at 13:03
Agree with MDMarra. Don't do that. Editing files on a running server could have side effects when a process wants to read or run a file that you have a file lock on. Edit the files. Commit them. Test them. Deploy them. – Bart Silverstrim Apr 12 '12 at 13:09

closed as off topic by SvW, MDMarra, Ward, Khaled, WesleyDavid Apr 18 '12 at 5:47

Questions on Server Fault are expected to relate to professional server, networking, or related infrastructure administration within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.

2 Answers

up vote 0 down vote

My first choice is putty with ssh, I'm still work alot with bash/vim.

My second choice is typo3 to do editing via the browser.

share|improve this answer
up vote 0 down vote

You can set up Samba to simply share the stuff out. I also use UltraEdit which can open files over (S)FTP. Here's a sample Samba config that will give you VERY VERY OPEN access to a specific directory in *nix. This also does one other thing. It allows you to create symlinks of directories into your Samba path and have it be visible of Samba. If you do not want this (it is a huge security risk if you're not on a closed environment), disable 'wide links' 'follow symlinks' and 'unix extensions'.

DO NOT USE THE BELOW CONFIG unless you are in a closed environment where you have untrusted people on your LAN.

[global]
netbios name = SAMPLE
workgroup = WORKGROUP
interfaces = lo eth0
guest account = nobody
security = share
hide files = /.*/
#hosts deny = 192.168.1.1
create mask = 0666
domain master = no
local master = no
preferred master = no

wide links = yes
follow symlinks = yes
unix extensions = no

[files]
public = yes
guest ok = yes
read only = no
writeable = yes
path = /var/www/files
browseable = yes
comment = http://community.dakcs.com/files
share|improve this answer
You can add additional users to enable some form of login authentication with 'smbpasswd'. This will allow you to log in just as you would a standard Windows share. – UtahJarhead Apr 12 '12 at 12:40
Couldn't you run into issues editing the files directly...like, race conditions and such...? – Bart Silverstrim Apr 12 '12 at 13:08
Absolutely you will! With the pronouns he used, I'd assumed (there's that word!) that it was going to be him as the sole editor. He NEEDS a true code repository like SVN or git. – UtahJarhead Apr 15 '12 at 1:57

Not the answer you're looking for? Browse other questions tagged or ask your own question.