LinuxQuestions.org - Building a small home/web server. Looking for Linux and Apache advice...

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Building a small home/web server. Looking for Linux and Apache advice... (https://www.linuxquestions.org/questions/linux-newbie-8/building-a-small-home-web-server-looking-for-linux-and-apache-advice-4175421027/)

Quote:

Originally Posted by Aunnix (Post 4751114)

Yeah, I'd like to basically only have the two partitions... one to store the OS and programs that control the functioning of my different "components" (web server, file server, etc...), and the second being the partition that will actually store the files, websites, and media. What I would like to do, is store everything on the server pull the files I need on my windows 7 computer work on them then upload them right back to the server and then I can upload them to the web (if they are websites or something). Speaking of which, can I install my programs (like MS Office, Starcraft, Photoshop...) on the server and access them from any computer on the network?

In reality, you'll most likely have more than the two principle partitions. You will need a swap partition (Linux's virtual memory backing store), and you should have a boot partition, especially if you use disks larger than the BIOS knows how to handle natively, and for sure if you use a bootloader like grub (which doesn't know how to access raid partitions).
You can use the Linux host as a file server, and install Windows applications there, in some cases, I think, but that never seems to work well for me. Windows applications are always so tightly coupled to the host that it just isn't usually a good fit. Most are single-seat licensed anyway, so sharing them on multiple Windows hosts isn't technically allowed. The Linux server will work just fine as a file server for Windows data files that your Windows hosts create using the applications you mention. Samba is the file server software used for that. Doing that precludes the need to transfer files between hosts. Just mount the Linux share on your Windows workstation(s), and edit them in place. The shared filesystem behaves just like a local disk on Windows.

Quote:

What do you mean by acquiring music? Are you referring to just simply downloading a music file from the internet?

I guess if you're going to be streaming music, it has to come from somewhere. You might want or need some systematic way of controlling how it gets put on your server.

Quote:

What do you mean by "level 2?"

On most distros, runlevel 2 is a non-GUI mode that just comes up with a text mode console. Boots faster and uses less memory. Typically, runlevel 5 gets you a full GUI Desktop.

--- rod.

Quote:

Originally Posted by theNbomr (Post 4751159)

Ok, putting the windows programs on the one machine sounds like a hassle, lol. I just thought for future reformatting purposes it would have been nice because I wouldn't have to worry about reactivating cd/serial keys.

Partitions... that's fine. Linux can create all the partitions it needs for the OS. I just want all of my files/media on one partition, which then I will separate into folders. All of it needs to be accessible via my home machines, but there will be some that I may like share online. I would hope to find a bootloader that can access my RAID setup since that's what I'll be running so I can mirror the HDDs.

Samba basically allows me to edit my files locally (in my office on windows) then when I save the file, Samba will automatically transfer it to the server (in the basement)?

The streaming I want to do, is just for devices in my home on my own network. I'm not looking to stream out to other internet users. As for acquiring the media I wish to stream, I would download it and FTP it to the server. I have no plans of letting the server just constantly find and download media on it's own (I'm pretty sure people do this, otherwise I assume they are just starting like 30 downloads on their machine and walking away until it's all done?)...

And yeah, I want to run it in level 2 as I plan to do all maintenance, updates, file transfers, etc. remotely from my main Windows machine.

Quote:

Originally Posted by Aunnix (Post 4751186)

Samba basically allows me to edit my files locally (in my office on windows) then when I save the file, Samba will automatically transfer it to the server (in the basement)?

Yes, that's fairly accurate. The application just thinks the file is on a local disk. The 'transfer' happens seamlessly in the background.

Quote:

I have no plans of letting the server just constantly find and download media on it's own (I'm pretty sure people do this, otherwise I assume they are just starting like 30 downloads on their machine and walking away until it's all done?).

There are tools on Linux (so I assume on other OS's, but I've never checked) that can do continuous downloading of streaming audio from online radio stations. You have to point the tool at an appropriate URL, but once you've done so, they will just download perpetually.

--- rod.

Ok, everyone. As long as nothing comes up, I will be making my Linux attempt tomorrow evening. Please post any last minute thoughts or words of wisdom for me. I will keep you posted on how it works out.

Thanks!

Re your ISP: you said 2 different things..
1. your server will only need to be visible in your LAN/house, in which case your ISP isn't involved
2. you might host sites for a few friends:
question; are these people inside your LAN/house; if not they will require access from outside, in which case check the Terms of Service of your ISP

Quote:

Originally Posted by chrism01 (Post 4755107)

hmm.. yeah, the websites would need to be viewable online from anywhere around the world, lol. I will call my ISP and see if I can talk to someone who can actually understand what I'm trying to accomplish.

The server(s) that need to be only visible on home network, would be the server(s) that are allowing me to stream/view/access data files such as music, videos, office files, etc to the other devices (ps3, phone, etc.) connected to the network.