# Jumpstart Published articles for Jumpstart. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Creating a Rails App Using JumpStart Pro DevFeed: [Creating a Rails App Using JumpStart Pro]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-07T06:36:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Development](), [GitHub](), [Ruby](), [test]() Tags: [github](), [guide](), [jumpstart](), [npm](), [rails](), [ruby](), [test]() ### AI overview A tutorial explaining how to create a Rails application from a JumpStart Pro template, clone it locally, configure Ruby and the database, install dependencies, and run Rails tests. It also discusses resolving an asset-pipeline error by using Node.js 16 and rebuilding the application's JavaScript. ### Source excerpt The view of the shelling of Kharkiv at 4 am Donate Now to Pizza for Ukraine The following blog post is an excerpt from a series of articles I'm working on about JumpStart Pro. I found myself referring to the steps below that I thought it might be generally useful for people. I'm going to walk you through the "post purchase" experience with Jump Start Pro (JSP). This will guide you through creating a new app using JSP. Step 1: Cloning an App Into Your Github Here's what you do: Purchase your Jumpstart Pro license. Log in to https://Jumpstartrails.com/ if you haven't already. Click on your license name. You will end up at a page which tells you to visit your Github repo. You need to goto: https://github.com/orgs/Jumpstart-pro. This in turn will take you here: https://github.com/Jumpstart-pro Click into the Rails repository https://github.com/Jumpstart-pro/Jumpstart-pro-rails Click the green Use This Template button. Change the owner to be your github name Enter the name of the NEW repo: Set your description if you care (I never do). Change the setting to be private. I checked off [ ] include all branches (no clue if that was right or not) Click the green Create repository from template button Step 2: Getting that Cloned App Onto Your Machine Github is going to clone the Jumpstart pro rails repo over to your personal github account. Here's what's next On your new repo, click the green Code drop down and get the clone url . On your development machine, change to your local development directory and clone the repo: git clone (what you copied) Set up your local ruby to be 3.1 if you don't have it. Run a bundle install Edit config/database.yml and change database names as needed. Now you want to run: bin/rails db:create Step 3: Setup and Getting to Green Tests in a Rails 7 World When you're starting with something complex that someone else built then tests are always, always, always your friend. So this means that you start with: bin/rails test This is going to fail but we ## Notes on Setting Up Stripe for Use with Jumpstart Pro DevFeed: [Notes on Setting Up Stripe for Use with Jumpstart Pro]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-31T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [stripe](), [Rails](), [Software as a service](), [Template](), [Command-line interface](), [Homebrew](), [API](), [browser]() Tags: [account](), [api](), [cli](), [credentials](), [homebrew](), [implementation](), [jumpstart](), [logs](), [product](), [rails](), [saas](), [stripe](), [test]() ### AI overview A practical guide to setting up Stripe billing for a multi-license SaaS product built with Jumpstart Pro and Rails. It covers configuring products and subscription plans, adding credentials, installing and authenticating the Stripe CLI, configuring webhook signing, and verifying a test transaction. ### Source excerpt I just finished, with a colleague's assistance, the SAAS implementation of a multi license product using Stripe as the billing engine and Jumpstart Pro as the Rails application template. Listed below, in a mildly random order, are the steps we had to take: Create a Stripe account. Add your bank account credentials. Define your product within Stripe. Define your subscription plans within the product inside Stripe. Pricing plans nest within one product which is not intuitive. Add the Stripe credentials to the Rails environment. Read This Post!. In the /admin/plans urls on your Jumpstart based application, define the plans and prices that you want to offer (remember to enter prices in pennies) and make sure that the plan identifier that Stripe generated is entered into the stripe field inside the plan creation tool. Install the Stripe listen tool using Homebrew: brew install stripe/stripe-cli/stripe Authenticate your Stripe listen with your stripe API key like this: stripe login -api-key pk_BLAH_FOO_BAR_BAZ_DOH_HOMER Start the Stripe Listen tool (it defaults to port 3000; if you are running Rails on another port then you need to figure that bit out yourself). Confirm in a browser that this is the right api return value (and, yes, this supports Choosy). When you see the webhook signing secret show up then use the rails credentials:edit to add that to your environment. Create a test transaction using the Stripe test card numbers and you should see in the logs that the transaction went all the way through with entries something like the ones below. stripe listen Ready! Your webhook signing secret is whsec_TRyDDDDDDDDDDDwnW3Y3u6TY7hDc (^C to quit) 2020-01-31 21:07:18 -> setup_intent.succeeded [evt_1G7BOCARA9hqQw13nA4] 2020-01-31 21:07:24 -> customer.created [evt_1G7BODARA9hqQw13uTOc] 2020-01-31 21:07:28 -> payment_method.attached [evt_1G7BOEARA33c6vCsbI] 2020-01-31 21:07:31 -> customer.updated [evt_1G7BOEARA3b1n6m7mC] 2020-01-31 21:09:25 -> setup_intent.created [evt_1G7BQG ## Retrospective on Using Jumpstart Pro for a Rails Side Project DevFeed: [Retrospective on Using Jumpstart Pro for a Rails Side Project]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-21T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Template](), [Development]() Tags: [app](), [back-end](), [css](), [development](), [email](), [front-end](), [html](), [jumpstart](), [projects](), [rails](), [retrospective](), [side-project](), [tests]() ### AI overview The author reflects on choosing Jumpstart Pro, an application template for Rails projects, as a major development decision in 2019. They describe its prebuilt features, including Devise, Tailwind CSS, transactional email, HTML templates, and tested scaffolding, and recommend it for new projects. ### Source excerpt I don't generally do the retrospective (save in an agile context) - I prefer to look forward. And, yes, I'll admit that given some of the crap in my personal life these days, there's a reason for that. Now, that said, I've been thinking back over my 2019 year and I wanted to comment on my single best development decision of 2019: Buying Jumpstart Pro was my single best development decision in all of 2019. Like a lot of developers out there, I'm a back end guy. Yes I can do front end stuff but it tends towards a local maxima that might best be defined as ugly or even, perhaps, fugly. And, now, I can happily say never again. Jumpstart Pro is an application template for your next Rails app that gives you: A prebuilt starting point where the things that you are going to do anyway are already done like devise like a CSS grid (Tailwind) like transactional email like html templates that look good like a scaffolding generator that is all setup including tests like ... I bought Jumpstart Pro back in August when I had a side project that I was already pretty deep into and since Jumpstart Pro is best for new projects, well, I put it aside - and that was stupid of me. I should have trusted that Chris Oliver, the author of Jumpstart, made Jumpstart awesome - because he did. When I finally realized how good Jumpstart was, well, I started a different side project because I wanted to experience Rails from his perspective. And now that I'm about to ship this new side project, the only thing I have to say is absolutely worth it. Best damn development decision I made in 2019. Recommended. ## Jumpstart Rails Tutorial 01 - Bringing an Existing Codebase In DevFeed: [Jumpstart Rails Tutorial 01 - Bringing an Existing Codebase In]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-02T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Tutorial](), [repo](), [Code](), [Deployment](), [Databases](), [Yarn](), [GitHub]() Tags: [code](), [database](), [deployment](), [development](), [getting-started](), [github](), [how-to](), [jumpstart](), [rails](), [repo](), [tutorial]() ### AI overview This tutorial series documents porting an existing Rails application into the Jumpstart Rails application framework. The first article covers cloning the licensed repository, installing dependencies with Yarn, updating database.yml, and adding the local codebase to GitHub. ### Source excerpt Updated: 5/5/2020 It is the second day of the New Year - welcome to 2020 - and I have still failed to launch my side project that I started midway through 2019. Sigh. I find myself fundamentally regretting this but, well, life: New Job Wife in Hospital Son and Schooling Issues Etc So my New Year's Resolution(s) is: Launch by end of Q1, 2020 Not have deployment eat my brain Launch with Something that I'm Visually Proud Of Launch with SAAS billing features from day 1 and Get paying Customers That last item, SAAS billing features, is a sticky point. I've actually implemented this myself before - I wrote all the back end code for the AppData SAAS engine which successfully processed over 3.1 million dollars in revenue over a 5 year period (BrainTree api). And I really, really, really don't want to rewrite that. Nor do I want to use a third party service and lose another percentage chunk over baseline Stripe fees. And all of this means that I need to use the Jumpstart Rails application framework. I already have a license for it anyway and the issue is that I need to port an existing, almost complete Rails app into it. All of the blog posts starting with Jumpstart Rails Tutorial nn will cover this process. While there is good documentation for Jumpstart Rails, it is reference material rather than how to material. Note: If anything I write during this series comes off as critical of Chris Oliver, the man behind Jumpstart Rails, it isn't. I am an unabashed fan of the damn fine work that Chris Oliver does. Step 1 - Getting Started with Jumpstart Rails - Clone the Repo The first step is to purchase an actual license for Jumpstart Rails. This will get you added onto the Jumpstart Rails git repo: https://gitlab.com/gorails/jumpstart-pro What you need to do is begin by cloning this repo down to your local system: git clone git@gitlab.com:gorails/jumpstart-pro.git web_change_me_now2 You notice that I changed the name of this to: web_change_me_now2 I changed it since my previous re ## Updating to the Latest Version of JumpStart Pro DevFeed: [Updating to the Latest Version of JumpStart Pro]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-12-29T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Git](), [GitLab](), [Rails](), [repo](), [GitHub](), [Development]() Tags: [development](), [git](), [github](), [gitlab](), [jumpstart](), [rails](), [repo]() ### AI overview A tutorial on updating JumpStart Pro projects by cloning the source repository, configuring separate remotes, and pushing project changes. It explains how copying a project without its .git directory disconnected the project from the original remote and prevented normal updates. ### Source excerpt So I've been using JumpStart Pro to build a new side project and in a discussion with Chris Oliver, the creator of JumpStart Pro, I reported a bug which he said "Oh - you should update to the latest". He viewed the update process as something seamless and I, honestly, didn't get it. And, in researching this, I discovered that I made a fatal mistake. The rest of this blog post covers that mistake and explains how you update JumpStart Pro. Here's the tldr (too long; did not read): ALWAYS, ALWAYS, ALWAYS create a new app based on JumpStart Pro by cloning it from the GitLab source i.e. you start with: "git clone git@gitlab.com:gorails/jumpstart-pro.git YOUR_PROJECT_NAME" Go to github and create a repo for YOUR_PROJECT_NAME Copy the github clone info and add it as a separate remote: git remote add YOUR_PROJECT_NAME git@github.com:YOUR_GITHUB_USERNAME/YOUR_PROJECT_NAME.git Make a change like updating the README.md and do the add / commit dance and push to your repo as git push YOUR_PROJECT_NAME master Even though I've worked with Git for more than a decade now, I've previously only worked with Heroku as a git remote so I missed the implications of this when I originally cloned my first JumpStart Pro app. Sigh. The critical mistake I made was that I had started my second JumpStart Pro project by copying from the first JumpStart Pro project I had made and the NOT moving over the .git folder. This meant that my new project was now disconnected from the original remote so I couldn't just do a git pull to update it. Fixing My Own Stupidity Here's what I did to fix this: I started by creating a new application cloning into a new location: git clone git@gitlab.com:gorails/jumpstart-pro.git okrsnow I created a new git repo for my app I added the new repo with: git remote add okrsnow git@github.com:fuzzygroup/okrsnow.git I made a change and pushed to git push okrsnow master I manually copied over all the code from my original JumpStart pro repo. Given that Rails apps have such a c ## How Do You Know What ActiveRecord Table Has a user\_id Attribute? DevFeed: [How Do You Know What ActiveRecord Table Has a user\_id Attribute?]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-12-28T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Development](), [data-modeling](), [business logic]() Tags: [active-record](), [activerecord](), [business-logic](), [class](), [classes](), [console](), [development](), [id](), [jumpstart](), [metaprogramming](), [migration](), [migrations](), [rails](), [relationships](), [schema](), [table]() ### AI overview This article explains how to identify application classes whose ActiveRecord-backed tables have a user_id attribute. It introduces a DataObject class with a .has_user_id method that can be run in the console, helping the author add belongs_to user relationships without repeatedly checking the schema. ### Source excerpt Even though I'm a firm, firm believer in agile, I've recently been experimenting with a throwback to waterfall style development and it very quickly left me with a fully featured data structure of tables and relationships modeled as example data. What I did is very rapidly write a series of migrations and then populate them to represent a sample "installation". My goal with this approach was to play to my strengths - data modeling - and avoid getting tied down in user interface stuff (my weakness). This was a very, very interesting approach and what I found was that I got much further along the lines of the "guts" of an application simply because I never got discouraged by: Oh Shite - I know this should look good but I'm too much of a hoser to make it look good; I guess I'll put it aside and go watch TV The downside to this is that I never bothered setting up the normal associations that you do when you write a migration; I simply thought about this application in terms of the example data: the users who would be using the system the data objects that they would create how the data objects would interact with each other One of the things that I noticed when I started filling in the basics like "belongs_to :user" was that I kept constantly jumping between the class I was working on and the schema file. Finally it hit me - what I needed was a method that I could execute in the console that would tell me what classes had a user_id attribute. And so I wrote a class called DataObject (for an ActiveRecord class which stores data) and a method .has_user_id. What I was looking for was output that looked like this: > DataObject.has_user_id Initiative Yes - has a user_id field KeyResultOwner Yes - has a user_id field KeyResult Yes - has a user_id field ObjectiveOwner Yes - has a user_id field ObjectiveType Objective Yes - has a user_id field OkrTeamMember Yes - has a user_id field OkrTeam Yes - has a user_id field OrganizationGroup Organization Quarter ResponsibilityRole Stat ## ESP32 Device Provisioning: Configuring Custom Data DevFeed: [ESP32 Device Provisioning: Configuring Custom Data]() Original publisher: [Read original article]() Author: John Lee Published: 2019-10-11T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Provisioning](), [ESP-IDF](), [ESP32](), [configuration](), [API](), [client]() Tags: [api](), [ble](), [blog](), [configuration](), [esp-idf](), [esp32](), [http](), [iot](), [jumpstart](), [provisioning](), [wi-fi]() ### AI overview This tutorial explains how to configure device-specific custom data during initial ESP32 provisioning using the unified provisioning infrastructure in ESP-IDF and ESP-Jumpstart. It covers the provisioning communication stack, custom API endpoints, and a callback-based implementation for configuring values such as a user-friendly device name. ### Source excerpt One of the common requirements I have seen is, during the initial device provisioning, configuring some device specific custom data on the device. This could be something as easy as assigning a user-friendly name to the device, or something like initialising the Alexa credentials on the device. The unified provisioning infrastructure within the ESP-IDF/ESP-Jumpstart allows for this mechanism with ease. ## ESP-Jumpstart: A Customizable ESP32 and ESP8266 Firmware Template for IoT Product Development DevFeed: [ESP-Jumpstart: A Customizable ESP32 and ESP8266 Firmware Template for IoT Product Development]() Original publisher: [Read original article]() Author: John Lee Published: 2019-05-12T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Template](), [ESP8266](), [Embedded Software Dev](), [Tutorial](), [Development](), [GitHub](), [Android](), [iOS](), [Amazon Web Services](), [Cloud](), [Internet of things]() Tags: [android](), [applications](), [aws](), [blog](), [cloud](), [esp](), [esp32](), [esp8266](), [firmware](), [github](), [gpio](), [iot](), [jumpstart](), [ota](), [product-development](), [tutorial](), [wi-fi]() ### AI overview ESP-Jumpstart is a customizable firmware template for ESP32 and ESP8266 product development. It provides incremental tutorial steps for building a deployable smart power outlet, with phone applications for Wi-Fi configuration, cloud synchronization through AWS IoT, remote control, OTA firmware upgrades, and factory reset functionality. ### Source excerpt ESP-Jumpstart (GitHub repository) is a production-ready, easy-to-customise firmware template that you can use to jumpstart your product development with ESP32 / ESP8266. ESP-Jumpstart builds a fully functional, ready to deploy "Smart Power Outlet" in a sequence of incremental tutorial steps.