Deploying a Flask application doesn’t have to mean putting everything on the same server. In this tutorial, I’ll walk through how I deployed the **Jersey City Pickleball Club (JCPC)** projects using a hybrid approach: the **JCPC website** as a static site, and the **JCPC booking portal** and **JCPC admin portal** as dynamic Flask applications on Render. This setup demonstrates how different parts of the same application can be deployed independently, depending on their technical requirements. Prerequisite: This tutorial is part of the Flask Landing Page and Reservation System Series. 📚 View the Complete Flask Landing Page and Reservation System Series ⬅ Previous Part Step 1: Set up GitHub First of all, log in to your GitHub account. Then click the '+' button in the top-right corner and select the dropdown to create a new repository. Next, provide a name and add a license; here, I selected Apache License 2.0, and finally, I clicked the green button "Create...
A reliable booking system starts with reliable authentication. In this tutorial, we’ll use Pytest and Playwright to test the Jersey City Pickleball Club (JCPC) website’s essential user flows—sign up, sign in, and sign out. Rather than simply checking whether a page loads, we’ll simulate real user interactions and verify that JCPC responds correctly at each step. By the end, you’ll have a practical foundation for building end-to-end authentication tests for a Flask application.