![]() ![]() The first and most crucial thing PaaS providers give you are virtual “computers” called instances which run your app. PaaS providers work by giving you easy access to a few resources that any Rails app can’t live without to function on the web. First, let us explore from a high level how PaaS providers work. We will provide a list of our recommended PaaS providers later in the lesson. Using a PaaS provider for deployment, we can focus on learning and mastering Ruby on Rails without taking a significant diversion to learn the specialized knowledge needed to manage and maintain servers ourselves. It’s an incredibly powerful model and perfect for us right now. While you, the developer, focus on furnishing, decorating and living in the space. Taking our landlord metaphor a little further, a PaaS platform is like having a landlord who takes care of all the utilities, building maintenance and security. ![]() Allowing us as developers to focus more of our time on building our applications instead of configuring and managing the servers they run on. They manage many of the low-level nitty-gritty details with the underlying server infrastructure. The most important thing to know about them is they are much easier to use and more approachable for beginners than other hosting providers. Platform as a Service is a specific kind of hosting provider. We will be focusing on and utilizing these latter providers in this lesson. They range from the big and complex cloud providers like AWS, Google Cloud and Microsoft Azure to the more beginner-friendly platform as a service (PaaS) providers like Heroku, Railway and Fly.io. Luckily, many hosting providers do offer everything we need. GitHub Pages cannot run Ruby code and doesn’t have database services we can use. This additional tech prohibits us from using GitHub Pages for hosting our Ruby on Rails apps. But additionally, you need a server-side language such as Ruby and a database. To build dynamic sites, you still need HTML, CSS and JS. Twitter is a good example every Twitter user sees different content on their homepage feed based on who they follow. To build static sites, you only need HTML, CSS and Javascript.ĭynamic websites, on the other hand, are websites that can change content based on the user who is visiting them. They are “static” because everyone who visits them will see the same content. Static websites consist of pre-written HTML pages. We’re going to need something more powerful. GitHub Pages is great for hosting static web pages for free, but we won’t be able to use it for hosting our dynamic Ruby on Rails apps. You’ve already had some experience using a hosting provider when you deployed projects to Github Pages earlier in the curriculum. They own servers and rent space on them to customers, who can then use the space to store their websites and make them accessible to anyone on the web. Hosting providers are like server landlords. How to troubleshoot common deployment issues.The difference between static and dynamic sites.This section contains a general overview of topics that you will learn in this lesson. In this lesson, we will learn how to deploy our apps to a hosting provider, allowing us to run, build, and operate our web applications in the cloud. Whether it’s to share our creations with friends, create a portfolio for future employers, or launch an online business, we need to host our applications somewhere others can publicly access on the internet. Before continuing our web development journey, we must address one important task: showcasing our hard work to the world. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |