Posts

Showing posts from June, 2021

Deploying Rails to the GCP AppEngine

Image
This post is a progression from a previous post regarding setting oneself up with GCP , and a supplement to the deploy section of the Rails 6 guide in this blog. This post can be used by itself, but it is highly recommended that at the least previous GCP post is read first (particularly to set up the service account ). This process is rather long and can be tricky, so has been split into sections: CloudSQL Instance Setup AppEngine & Google Cloud SDK PostgreSQL Database Setup AppEngine App Configuration Deploy the App     SQL Instance Setup Unlike Heroku, the GCP deploy process is a bit more involved and requires more explicit setup of certain features. This guide will use the ToDoList web application created in the Rails guide as a basis for what we are deploying. We will start by creating our database instance so that our app can interact with data - as sp
Post a Comment
Read more

Creating a Development / Deployment Virtual Machine with GCE

Image
When creating a Rails app, it is helpful to have a decent roadmap of what you're going to do. An important part of this is where you are going to develop your app, and where you are going to host ( deploy ) it. If the answer to one or both of these involves using the Google Cloud Platform, then this guide should help you set yourself up nicely. This process is rather long and can be tricky, so has been split into sections: GCP Account Setup Project APIs & Service Account Setup Virtual Machine Setup Accessing the VM     GCP Signup & Project Initialisation If you don't already have a Google account, this is naturally a prerequisite to getting yourself set up, and you can set one up quickly via accounts.google.com . Once you're set up, head over to cloud.google.com , where there should be a nice Get started for free button, which you can click to get started:
Post a Comment
Read more

Popular posts from this blog

New Rails Apps with Docker Compose

Image
Following on from the Docker & docker-compose guides, it is possible to use docker-compose to build a Rails application that uses a PostgreSQL database without even installing Ruby on your local machine by instead using containers ! This becomes a very useful option to have if you work from many different workstations and don't want to ensure they are all equipped with the correct Ruby and Rails dependencies, or if you wish to use a version of Ruby / Rails not supported by your operating system (for example, Ubuntu 20.04 only allows provides up to Ruby 2.7 in its apt cache). In fact, Rails 7 added native support for Docker, such that it generates almost all of the default files we need for us! This comes with its problems and, I won't lie, updating this post to work with Rails 7 (it was previously written for Rails 6) has been a colossal pain and features a bit of hackery. However it is ultimately a good thing, and having
Read more

[ToDoList] Basic Pages

Image
Well that was fun. However all we’ve really done is spooked someone called Bob, without actually creating anything remotely resembling a web application. Let’s rectify this and create some pages one would normally find on a website; a Home page and an About page. Home & Away About Helpful Links [Insert Beatles Reference]     Because we already learned a bit about MVC, we know that we will need a controller and at least one view to display these pages (we won’t need to worry about models until we’re handling real data). As before, we’ll need to add a route configuration so Rails knows where to go, too. Rails provides a fair bit of magic to streamline this process in the form of generators . However, because we’re learning, we’re going to do this manually for now and learn what this magic entails, so we can appreciate it more later. We already created a PagesController in the last sec
Read more

[ToDoList] Docker Compose

Image
We learned in the previous section how Docker is a fantastic tool with which to build and deploy applications, however has some inconveniences with developing these apps such as having to rebuild the image every time there is a code change as well as any development database entries being wiped. This section will offer some relief against these two issues by using Docker Compose to build our application and make live code changes, as well as using a separate container to host our development database in PostgreSQL - this will encompass three main tasks: Back up and edit the Dockerfile we made in the previous section so our image can be built. Create our docker-compose.yml in the app's root directory to create our web & postgresql database containers. Back up and edit some our app's configuration (namely the database.yml & Gemfile ) to use the new postgresql container . After all this, we can set about
Read more