VPSDeploy is a new “cloud” VPS deployment account appear in 2018.
It was advised as a way to actualize immersive agenda adventures (through the web), about acute a ample bulk of “background” work, such as asset development/compilation and server redundancy.
The band-aid was originally created to break the “Ruby on Rails VPS” botheration – which basically states that in adjustment to host “Ruby on Rails” applications properly, you charge to use one of the new “cloud” VPS casework which accept become acutely accepted – the brand of DigitalOcean and Vultr falling into this category.
The botheration for a lot of humans is that whilst accepting a $5/mo VPS server is amazing (equivalent of “shared” hosting prices), it agency you accept to set up the absolute assemblage yourself. This is a above botheration because it agency that you are basically acting as arrangement ambassador – accepting to install, amend and advancement the server & its software.
Whilst installing web server software isn’t that big of a deal, it can get annoying – and creating a “deploy” apparatus is actual catchy (especially over HTTP). To this end, a amount of solutions accept been advised to boldness the problem, including the brand of Capistrano and Chef/Puppet.
VPSDeploy was congenital to accommodate a applicative band-aid to this problem.
It provides a web-based platform, through which you’re able to accouterment billow VPS servers active Ruby/Python/NodeJS/PHP. Unlike added “deployment” solutions (such as Nanobox or Hatchbox), VPSDeploy has several avant-garde appearance which in fact accomplish it awful attractive…
- Endpoint Management
This is the a lot of important allotment of the system. Instead of accessories “applications”, or even “servers” – VPSDeploy focuses on the endpoints that a breadth may accept (subdomains/folders). Each endpoint can be mapped to altered server basement – acceptance for the brand of a “blog” to be hosted on the aforementioned server as a Ruby on Rails application. The accent of this is that it break afar the “build” action for the arrangement – acceptance you to actualize diminutive web casework for users to appoint with. It agency that you’re able to finer administer “support”, “email”, “blog” and “application” apparatus of a axial appliance (rather than accepting to brew it all calm with a amount of altered services). Further, it aswell makes your appliance development absolutely article oriented. Rather than absorption n “pages”, you’re able to analyze the assorted endpoints your appliance may accept – designing adventures about them.
- VPS Dashboard
This gives you the adeptness to accommodate assorted “web services” into the axial VPSDeploy platform. For example, getting able to clue analytics, amusing media posts, SEO achievement and even how abounding users an appliance may have. Think of the axial VPS dashboard as the best “admin” breadth for ANY web based application. Like CPanel, it provides low-level admission to the brand of a database arrangement and added services… except a lot of of them are in fact powered by API’s (meaning you don’t accept to anguish about them on your own infrastructure). This is a advocate section of functionality that has continued been behind for use in the web deployment world.
- GIT-Based Deployment
Finally, a GIT-based deployment apparatus provides users with the adeptness to arrange applications anon to their own basement afterwards accepting to anguish about versioning or body scripts. Much affiliated to how “Heroku” works, this provides users with the adeptness to artlessly “push” an appliance (either to GIT/Bitbucket or anon to the server) and accept it automatically arrange on their own server stack. This has not been accomplished afore in a way agnate to what has been created here. Not alone does it accumulate the deployment process, but aswell ensures that you’re able to extend your basal development processes to actualize the accurate ideal of versioning. The capital botheration today is that whilst “GIT” has been adopted by software developers, appliance it for database backups and added purposes has not yet been popular. VPSDeploy’s basal account gives you the adeptness to aback up the brand of your WordPress accession or Abutment basement afterwards the charge for big-ticket equipment.
To bigger explain the a lot of important aspect of this arrangement – the “Endpoint Manager”, we charge to attending at how “web” applications work, and what their abeyant could be.
The botheration with the accepted way things plan – abnormally online – is that it’s actual monolithic. You’re about encouraged to run one appliance server, acceptance you to arrange the brand of Rails or ASP.net afterwards the adeptness to serve added requests.
The acumen for this is simple – the basement is currently alone at a point whereby humans are able to arrange a individual appliance to a individual server.
The solutions alone apprehend one appliance per domain, and appropriately alone accommodate the functionality to accomplish that work. This is not to say that an adaptable arrangement (such as accepting an AngularJS frontend with a Rails backend) is not possible; it’s just not applicative with the assorted accoutrement that accept been appear / created presently.
The way to boldness this is through what’s accepted as “endpoint management”.
An “endpoint” is basically the point at which a user will be able to admission a computer service. This comes in abounding forms, but in the apple of the Internet – is basically the “query string” of a URL.
There are two elements to a URL which can be customized. These are the “subdomain” and added “folders” afterwards the abject “domain”. The “domain” can either be a domain-name or IP abode (all domains point to IP addresses anyway).
The point is that, in abounding cases, companies will wish to accept abstracted basement active on altered elements of their URL’s. For example, they may accept a “blog” at domain.com/blog, or a absolutely anatomic web appliance at <a target=”_blank” rel=”nofollow” href=”https://app.domain.com”>https://app.domain.com</a>.
The point is that in the present setup, getting able to anticipate how these endpoints are handled is not something that is possible. It’s all done with DNS – acceptation that it’s mostly handled in the breadth registrar’s infrastructure. However, the action does not tie into backend infrastructure, nor is it simple/easy.
An “endpoint manager” changes that. Rather than absorption on basement or even assets (such as domains), the endpoint administrator focuses on the “endpoints” of a accurate web service.
For example, if you’re active a web based bold – you’ll about wish to accept the “game” / “application”, basal functionality and added basement on one endpoint (the capital domain), a abutment account on addition endpoint (a subdomain), and maybe added casework such as email on addition endpoint.
The brand of VPSDeploy is able to set that up almost artlessly (with a beheld editor). Added applications cannot do that because they abridgement the added akin of integration. That’s why the affection has been singled out as one of the added benign the account has to offer.