DailyFaith Apply for your church
Setup guide · Part 1

Get your GitHub account ready

This is where your church's daily messages will actually live. It sounds technical — it isn't. Follow these steps in order, and by the end you'll have a folder on your computer ready for your first audio or video file.

01

Create a free GitHub account

Go to github.com

Open github.com in your browser and click Sign up, usually in the top-right corner.

Enter your details

An email address, a password, and a username. Your username will appear in some of your church's web addresses later, so pick something simple — your church's name or initials work well (e.g. hopefellowship).

Verify your email

GitHub sends a verification code to your inbox. Enter it to confirm your account.

Skip the extra questions

GitHub may ask about your experience level or interests during setup. None of this matters for what we're doing — choose any answer, or look for a "Skip" link.

Why GitHub? It's free, reliable, and — most importantly — it's your own account. Every message you upload stays under your church's ownership, not locked inside someone else's system.
02

Download and install GitHub Desktop

Go to desktop.github.com

This is a separate, free app (not the website) that lets you manage files on your computer and send them to GitHub with a couple of clicks — no typed commands required.

Download for your computer

Click the download button. It detects whether you're on Windows or Mac automatically.

Run the installer

Open the downloaded file and follow the prompts. Default settings are fine throughout.

Sign in

When GitHub Desktop opens for the first time, click Sign in to GitHub.com and log in with the account you created in Step 1.

03

Create your repository

What's a "repository"?

Just a folder that GitHub keeps track of. You'll have one repository for your church, holding every message you ever upload.

In GitHub Desktop, click "Create a New Repository on your hard drive"

You'll find this on the welcome screen, or under File → New Repository.

Name it

Use something clear, e.g. hopefellowship-content. Lowercase, no spaces (use hyphens instead).

Choose where it's saved

GitHub Desktop will suggest a location (usually a "GitHub" folder it creates for you). This is fine to leave as-is — just remember it, you'll need to find this folder again shortly.

Click "Create Repository"

GitHub Desktop creates the folder on your computer immediately.

Publish it to GitHub

Click the Publish repository button near the top of GitHub Desktop. In the dialog that appears, untick "Keep this code private" if you want it public (this is what our setup expects — it's how the app reads your files), then click Publish Repository.

Public, not private Your church's app reads messages directly from this repository. For that to work without extra setup, the repository needs to be Public — meaning anyone with the link can see the files, which is fine since the same messages are already meant to be heard by your whole congregation.
04

Create your audio and video folders

Find the repository folder on your computer

In GitHub Desktop, click Repository → Show in Explorer (Windows) or Show in Finder (Mac). This opens the folder you created in Step 3.

Create a new folder named "audio"

Right-click inside the window → New → Folder (Windows) or File → New Folder (Mac). Name it exactly audio — lowercase.

Create a second folder named "video"

Same process, named exactly video.

hopefellowship-content/
├── audio/
└── video/
Send the empty folders to GitHub

Go back to GitHub Desktop. You'll see the two new folders listed as changes on the left. Type a short message at the bottom (e.g. "Add audio and video folders"), then click Commit to main, followed by Push origin near the top.

A small quirk worth knowing GitHub doesn't keep a folder unless it has at least one file inside it. An empty audio or video folder may not "stick" until your first real file is added — that's expected, and nothing to worry about. It will appear properly once you upload your first message.
05

You're ready

That's the whole setup. You now have your own GitHub account, your own repository, and an audio and video folder ready to receive your church's messages.

Next: naming and uploading your first message

From here, every message follows a simple naming pattern (date, optional announcement marker, and a short title) that the app reads automatically — no extra setup needed for each new upload. We'll walk you through that as part of getting your app live.

Apply for your church →