Help setting up Linux Host

[El Toro]

I'm a LAMP guy not a SysAdmin guy and need advice or help on setting up an Apache/MySQL host for testing a PHP website.

I've got an older Intel core 2 duo desktop I plan to use and it will be on an internal, firewalls network. Only person hitting this website will be me on the same network.

Any step by step website you can refer me to would be great. If someone wants to drop by my offices in Newport Beach and set this up for $100 and a couple boxes of 12 Ga shot shells even better!

[ocabj]

You basically want to setup a LAMP stack from scratch?

There's plenty of guides out there if you don't know how to do this.

https://www.linode.com/docs/websites/lamp/

https://www.digitalocean.com/community/tags/lamp-stack?type=tutorials

Just adjust the steps accordingly since you're not running in a VPS environment.

If you're only setting up a LAMP stack for your own personal development and no one else is connecting to it, you're better off just running Vagrant.

https://www.vagrantup.com/

Safer, faster, cleaner. Not to mention you can destroy and reconstruct your stack repeatedly and fairly quickly.

[El Toro]

Yes I need a LAMP stack from scratch. I only run Win10 and ftp PHP files up to a hosted Apache server. I use Cpanel to access the MySQL host. I need a local host that I can take with me. Right now I have my laptop for Dev and a spare desktop Core 2 Duo box I would target for a local host.

I don't need this to be a Windows box but I'm not familiar with setting up a lightweight Linux host the above purpose.

Vagrant looks interesting but requires VirtualBox. How well does this VM run under Win10 with 2 Core processors?

[El Toro]

The Linode guides look good. THX

[FreshTapCoke]

If you can get vagrant running, I believe you can find an image with the setup that you're looking for and do a vagrant up and have everything you need running in a virtual box VM.

I could probably write you a vagrant file if you gave me the requirements.

Keep in mind though that this is like a temp dev environment. It's meant to be destroyed and recreated. Anything you want to persist should be kept elsewhere or at least backed up.

[the86d]

Slackware is pretty lean, and will not even run a GUI by default, to stay lean...
Slack has always been good to me, I even have an old thin client I slapped an SSD (USB powered from the header) in it, and that is my main home Linux box, single-core, and works well as a 1-4-trick pony.