Posts

Showing posts with the label gcp

On writing the AppEngine deploy guide

Image
 OHMYGODWHATAMASSIVECOLOSSALFUCKINGPAININTHEARSETHATWASILITERALLYWANTTORIPMYBRAINOUTWITHAPUBECOVEREDSAFETYSCISSORBLADEANDTHROWITATTHENEARESTTWATOFASWANSOICANATLEASTJUSTIFYMYRAPIDDEMISETOUTTERSHITTINGINSANITYINCROWNCOURT. Sorry. Seriously though, the next time I decide to take my Google fanboyism to that level again, just slap me in the bollocks with the nearest cheese grater. I think the only reason I have any remote reserves of remaining sanity is thanks to Taureor, Tom Scott, Jay Foreman and Allix (wife, not YouTuber). I'm sure I'll look back on the experience in a few weeks and remember it fondly, knowing that I've learned a huge amount from the experience and being actually really proud of it (rightly or wrongly). But some quick maths reveals what I could have achieved with that time, each of which seems infinitely more valuable right now: Written a 200-page book of love songs and bawdy limericks to give to my wife. Re-released Chandler's Dumb States Game with some...
Post a Comment
Read more

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 - ...
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

[ToDoList] Front-end Basics

Image
So we now know how to get Rails to perform all of the CRUD actions required to run an application with user data from the console. The next step will be to make this possible from the browser, and allow Todo items to be created, read, updated and deleted from our lovely website! The show View Creating Entries in the Front-End Front-End Feedback     We already have our basic database and our model set up from our efforts in the last section, so we only need to configure some routes and create a controller & some views to make our dream of front-end database manipulation possible. Let's start just by showing a Todo entry on a page on the site. We will need to utilise a bit more magic here, specifically in the form of param (eter) s - these are Ruby Hash objects that contain data to be passed between various components of the Rails application. In this case we wil...
Read more

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

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 - ...
Read more