I like to use Vultr : https://www.vultr.com/

I also use moss.sh to deploy the server and configure it to work with laravel. You can even specify a github repo and have all pushes to the master branch automatically apply on the server. https://moss.sh/

Currently I have 10 server with a coach plan and don't use the free plan (the free one is only good for testing). If I change to the new plan I need to pay 60% more! There is no problem for existing servers, but what if you need to move to another server (f.e. in case of a distro update)? That would be a new server with the new pricing model. I'm one of the first customers and I think it's time for something new. https://moss.sh/ looks interesting and is located in Europe. Does anyone tried Moss yet?

> neither the container nor the host is acting as a DNS server

That's not what this is for - this is for local resolution (through various means, including via dbus) - not so simple as things used to be.

A pertinent quote of a quote from that article:

>> resolved is not supposed to be a DNS server, it’s supposed to be exactly good enough so that libc-like DNS clients can resolve their stuff > >Therefore, it seems s a bit unfortunate that distros like Ubuntu Server (among others) and upstream providers include it as the default solution for name resolution without careful settings.

My advice? Ignore this whole thing, or use something else (like Debian or RHEL's UBI) to build your containers. Personally, I've observed Ubuntu doing "stupid" things over the years.

moss.sh & RunCloud seems to be a pretty good option here. You can always hang out on the free tier on moss and then switch if you have issues with it. You'll most likely have to pay for those features tho and RunCloud seems to have a reasonable price tag for it

Most VPSs that I've used come installed with cpanel but thats $15/month and it does have a Wordpress management toolkit.

In case you've missed it - some cpanel alternatives - https://blog.ssdnodes.com/blog/cpanel-alternatives-vps/

Sorry I dont work for Moss and have no affiliation with ANY company.

But I see why you might have thought so as I included a link to moss.sh . The reason being the URL is easy to type and the fact that if i just had 'Moss' , it would be much harder for anyone to discover using Google and i would like to give moss.sh a fair chance along with Serverpilot, Runcloud, and laravel Forge when it comes to discussion.

If you have a large Wordpress site then move away from shared hosting and shared resources.

The best option is to have your own VPS, which you can scale up vertically and down when you need it according to your traffic. DigitalOcean is a great provider (IMHO) as it provides a very good value for money (It's true that there are cheaper options, like Vultr, but I prefer the quality of DigitalOcean).

And for Server management and site monitoring I would use Moss due to the fact that it supports launching and managing DigitalOcean servers.

You don't need more apps but there are so many good ones to choose from on Cloudron that you'll want to try some out. For example, there's Bitwarden (password manager), Roundcube for managing your email, Wekan (kanban - Trello alternative), Matrix/Element (secure and federated chat), NextCloud (cloud storage), Matomo or Ackee (Google Analytics alternatives), etc..

This post can get really long if I list all the benefits of Cloudron but even though you might be comfortable updating the VPS on your own, having it automated means security updates are applied sooner rather than later. Besides, it's not costing you anything and you can install Cloudron on a VPS with 1-click on DO.

Alternatively, you can look into moss.sh - also manages your server for you but doesn't come close to Cloudron in terms of apps and feature goodiness.

If you are using systemd-resolved, it could be the problem. See this blog posting from June 2018.

​

https://moss.sh/name-resolution-issue-systemd-resolved/

I wrote about this a month ago: https://moss.sh/web-hosting-models-for-software-development-agencies/

While you can certainly host multiple websites on a same droplet, you'll sleep easier if you use different droplets for different customers (better performance and security isolation among them). Given the price points of DigitalOcean and other cloud providers, now it's a cost-effective solution too.

If you want to learn something , please dont be put of by anyone in this comment section. I encourage you to read and experiment to your hearts content.

Runcloud , Serverpilot and Moss.sh are precisely designed to mange a Linux server for you without the need of hiring a system admin . If your server gets hacked, simply restore from your previous backup which is the standard procedure that ANY host , expert will recommend you to do. No need to employ or pay for overpriced hosting for a mundane task that you can do.

This subreddit is brutal. I suggest you take everything with a grain of open mindness and look to other communities.

happy hosting :)

100% agree

BUT

This has dramatically changed with the advent of management panels such as Runcloud , ServerPilot , Moss.sh , Laravel Forge.

In essence these panels handle all the sysadmin stuff for your server such as updates, firewall/security , webapp creation etc.

You will basically have the same experience as a shared host but with the awesome advantage of having a server with Digital Ocean , Vultr , linode who have fricking amazing plans and performance compared to your shared host.

I tried Serverpilot months ago with more than 10 VPS (a mix from DigitalOcean and Vultr) but switched to Moss because their pricing plan doesn't depend on the number of servers you have.

Keep in mind that Serverpilot charges you $10 per server or $49 per server depending on the plan.

If you have 2 authority sites then I would recommend you to use 2 different VPS so that you can scale them up independently of each other.

Take a look into Moss, they offer a flat rate as the don't charge you per server. The Agency plan includes monitoring.

>Got a hold of them. NameSilo is telling me that I need to buy SSL for ~$10, just wanted to make sure this is normal or if I should look elsewhere.

I'd suggest a $5 droplet on DigitalOcean and something like Runcloud.io or moss.sh, etc. (there's a ton of options, happy to provide more if you'd like). <$15/mo and you'll have ssh included no extra cost.

Very useful list!

I'm using Moss.sh right now and it works great (they have a free plan).

If you use my referral code you'll get $10 https://moss.sh/?ref=ee544780e8d6

I agree with your conclusions. In general, I think you have several options to avoid building the assets locally:

• I find CI/CD servers more useful when you also want to run tests automatically (highly recommended). If you're just building your project's assets, you can do it right on your staging/production/whatever servers (see bullet below). In any case, from the CI/CD server you must also "define" how to deploy your new release to the appropriate servers.
• You can also use a tool like Moss [disclaimer: I'm a co-founder] to deploy on the corresponding servers. You can do it manually (1-click) or automatically by pushing your code to a given branch or tag of your git repo (either from a CI pipeline or your development computers). Different versions shouldn't be an issue, since you can install the same PHP or Node versions on all your environments and commit the lock files with your dependencies.
• If you really want to manage immutable infrastructure, then Docker is the way to go (as others have mentioned). You can use e.g. the automated builds of Docker Hub (or any other provider) and deploy them via git pull on your servers (again, either from a CI server or not). However, if your team doesn't have previous experience with Docker in development and production, following this path might impact your current workflow significantly.

We have this case very well supported in moss.sh - your dev can automatically trigger a deployment after a "git push" (if you want to). Otherwise, you can just click our "deploy" button.

As for the credentials, most people rely on env vars. PHP dotenv loads the content of a .env file as env vars for your application. Obviously, such file must be out of version control.

Im sorry but i disagree.

If a plugin gets compromised you would revert to a prior backup . This process is indifferent if you are using a shared host.

Its not going to fail willy nilly as these services have been designed to mange servers and web apps.

Give me 3 ways how a management panel such as cPanel, Runcloud , Server Pilot , Moss.sh , laravel Forge , can just 'fail' ?

I had an account with ServerPilot, but with more than 10 VPS the price were very high, more than $100/month. Also the features were very limited (I didn't have zero downtime deployments or monitoring in my plan).

I switched to Moss some months ago and I'm very happy as I always pay the same every month no matter the number of servers or sites I have.

I have some servers in Vultr and some in DigitalOcean. Both are good solutions. I prefer DigitalOcean but Vultr $2.5/month servers (when available) are a good resource to deploy dev/test environments.

To manage them I use Moss, as they allow me to launch and setup servers and sites in both providers with 1-click without leaving their site.

I think it depends on what are you looking for.

If you want to deal "manually" with everything related to you server (security setup, firewalls, package installation, etc) you can use something like EE.

If you want to focus on your code/projects and want everything to be set up automatically then I would recommend you to try Moss