Target audience: beginner to intermediate

Recently I have consolidated a number of personal projects that were hosted across a selection of cloud providers to one (relatively) easy-to-manage and cost effective AWS solution. Want to know more?

This article provides a high level overview of my AWS setup and links to past (and hopefully) future articles which provide a practical guide to replicating the setup yourself.

Situation

Over the years I have created and attempted to maintain a number of personal projects. While on the subject, I would strongly encourage all software engineers to work on personal projects as the benefits are…


N.B. This article is not about scheduling infrastructural programmatic tasks such as database backups. Rather it focuses on in-App functionality where the user can set arbitrary tasks to be created/due according to a schedule.

Image for post
Image for post
Fig.1 — The user-facing implementation of the scheduling feature

Situation

One of the projects I am currently working on is a maintenance planning system for large industrial sites (its called Luberly and more info can be found here). Recently we tackled the deceptively complex task of allowing users to set up work routes to be completed periodically. An example of such a work route would be:

replace the oil in every machine in “building A” every…


Situation

Over the weekend, as per a customer request, I started the process of implementing “read-only” user accounts to our flagship web application.

The current application stack is a React front end served by a Django web application interacting with a Django-Rest-Framework backend API.

Having worked with Django in the past I was fairly certain that there existed some great built-in user permission features which, if not a complete solution, would provide a great starting point in my quest to add different levels of customer employee accounts to our application.

Indeed my suspicions were confirmed when revisiting the authentication section of…


Introduction

I wrote this article following a frustrating couple of days trying to deploy my React.js application to AWS and connecting it to a domain I purchased through NameCheap.com.

At the time I was relatively new to the AWS ecosystem as much of my experience was in writing and deploying Django applications hosted on PythonAnywhere.com.

Much of this article recommends following a fantastic series of articles by Antoine Sauvage. However, I have added additional comments to help overcome issues I experienced and to explain the various nuances associated with using a domain from NameCheap.

I hope you find this article…

Scott Fraser

Senior engineer interested in everything tech. Whether its React on the FE, Python BE services, or devops magic — I’m in! Enjoying a contract at heycar uk.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store