Skip to content

what's cooking in the hack club kitchen

Notifications You must be signed in to change notification settings

hackclub/flavortown

Folders and files

NameName
Last commit message
Last commit date

Latest commit

50ab5b8 · · Dec 11, 2025

History

657 Commits
Dec 11, 2025
Sep 27, 2025
Dec 11, 2025
Nov 21, 2025
Dec 11, 2025
Dec 10, 2025
Dec 8, 2025
Dec 8, 2025
Sep 27, 2025
Nov 17, 2025
Dec 1, 2025
Dec 11, 2025
Sep 27, 2025
Dec 10, 2025
Sep 27, 2025
Oct 12, 2025
Nov 8, 2025
Oct 28, 2025
Sep 27, 2025
Dec 6, 2025
Dec 11, 2025
Sep 27, 2025
Oct 19, 2025
Nov 5, 2025
Nov 24, 2025
Dec 2, 2025
Dec 3, 2025
Dec 9, 2025
Dec 9, 2025
Nov 17, 2025
Dec 5, 2025
Sep 27, 2025
Sep 27, 2025
Nov 20, 2025
Nov 20, 2025
Nov 20, 2025
Dec 5, 2025
Nov 18, 2025
Nov 27, 2025
Nov 18, 2025

Repository files navigation

flavortown

what's cooking in the hack club kitchen 🔥

non-exhaustive list of setup steps

docker

me and the homies love docker, and it makes it stupid simple, so its highly recommended to use docker to make your life easier.

  1. clone it (duh)

  2. you most likely want a database here, so you can run that with this:

    docker-compose up -d db
  3. now to start cookin, run this and it will boot up rails

    docker-compose run --service-ports web /bin/bash
  4. now to really turn on the stove, run this (wait a few seconds for stuff to load) and point your browser to http://localhost:3000

    bin/dev
  5. pull out some instant ramen

random commands you might need

if you just need to run a command once (eg test migrations or whatever) here is how

docker-compose run web bin/rails db:migrate # please dont do this if you are hooked up to prod
docker-compose run web bin/rails bundle install
docker-compose run web bin/lintnt

if its giving you a file not found error and you are on windows, try running these commands. They switch line endings to lf (linux) ones

This will reset all your code!

git config --local core.autocrlf false
git rm --cached -r .   
git reset --hard
d

i hate docker

weirdo, but okay, you gotta figure out how to get postgres running yourself bucko

  1. double check your .env file to make sure its pointed at your database

  2. setup the db

    bin/rails db:prepare
  3. start the dev server

    bin/dev
  4. have a fire extinguisher at the ready