just brew it! wrote:IMO unless you're handling highly sensitive data setting up a chroot jail or docker container is just extra complexity you don't need.
just brew it! wrote:Any idea what distro you plan to use?
alloyD wrote:Arch. (cue ridicule )
just brew it! wrote:(Personally I'd go with Debian or Ubuntu 14.04 LTS if I was deploying a new Linode today; my existing Linode currently runs Ubuntu 12.04 LTS.)
alloyD wrote:Out of curiosity what kind of stuff do you guys do with your VPS's that you couldn't do with a shared plan?
alloyD wrote:I currently have a shared hosting plan with Dreamhost. I know there are some people who absolutely hate Dreamhost, but I've had a good experience with them. The point being that their basic shared hosting plan has enough juice to serve the (very) small sites that I run. Unfortunately for Dreamhost, I'm a tinkerer and really like to be able to have full control over whatever projects I'm working on and Dreamhost isn't always flexible with custom stuff.
I'm planning on running Nginx as the server on the VPS, but I'm wondering with the differences in architecture between Apache and Nginx and the fact that the low tier VPS only has one core, is it worth switching server software? Also, for you folks who have done this more than I, is it worth segregating the web server from other services I might run with a chroot jail, docker container, etc, or is running it all directly sufficient?
just brew it! wrote:- When I access the Internet on the road, I run a SSH tunnel to a SOCKS proxy on the Linode, to ensure that all local traffic on public WiFi and hotel Internet is encrypted.
alloyD wrote:just brew it! wrote:- When I access the Internet on the road, I run a SSH tunnel to a SOCKS proxy on the Linode, to ensure that all local traffic on public WiFi and hotel Internet is encrypted.
Oh yes, I've wanted to do this for some time, but it keeps getting bumped from the top of my project list. I imagine it'll be one of the first things I implement once the web services actually work.
ssh -D 1080 yourname@yourserver
just brew it! wrote:You don't even need the web services up and running to do this. All you need is the SSH service (it has a built-in SOCKS proxy).
Just establish a SSH session with the "-D" option, e.g.:
and tell your browser to use localhost:1080 as a SOCKS proxy.
- Code: Select all
ssh -D 1080 yourname@yourserver
(This is actually less important than it used to be, with more and more sites switching to HTTPS by default.)
just brew it! wrote:The only downside I've found of doing the remote SOCKS proxy thing (and it is only a small one) is that it confuses the web sites of B&M retailers when you click the button to find their nearest stores. The default list of choices is invariably in NJ (where my Linode is hosted) instead of near where I live (hundreds of miles from there). But having to click "change location" and key in my zip code every time isn't *that* much of a hardship. (And I'm sure many people would consider the ability to trip up web sites' location tracking capabilities to be a feature instead of a bug... )
Users browsing this forum: Google [Bot] and 1 guest