GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - TheMITTech/thetech.com: The content management system and frontend website for The Tech, MIT's oldest and largest newspaper.

BranchesTags
Open more actions menu

Latest commit

 

History

2,061 Commits
2,061 Commits

Folders and files

NameName
Last commit message
Last commit date
.github/workflows
.github/workflows
 
 
app
app
 
 
bin
bin
 
 
config
config
 
 
db
db
 
 
docker
docker
 
 
lib
lib
 
 
log
log
 
 
public
public
 
 
spec
spec
 
 
util
util
 
 
.dockerignore
.dockerignore
 
 
.editorconfig
.editorconfig
 
 
.gitattributes
.gitattributes
 
 
.gitignore
.gitignore
 
 
.rspec
.rspec
 
 
.ruby-version
.ruby-version
 
 
CHECKS
CHECKS
 
 
DEVELOP.md
DEVELOP.md
 
 
Gemfile
Gemfile
 
 
Gemfile.lock
Gemfile.lock
 
 
LICENSE
LICENSE
 
 
Procfile
Procfile
 
 
README.md
README.md
 
 
Rakefile
Rakefile
 
 
config.ru
config.ru
 
 
docker-compose.yml
docker-compose.yml
 
 

Repository files navigation

The MIT Tech

Deploy

Development Setup

The recommended way to develop on this website is to use Docker. See DEVELOP.md for more details.

Development Workflow

  1. Make your awesome changes.
  2. Add your changes to the Git staging area: git add <changed_files>.
  3. Commit your changes: git commit -m "Some message better than this".
  4. Rebase your changes to make sure you're staying on top of the newest dev branch: git pull --rebase origin dev.
  5. Push to the dev branch: git push origin dev
  6. Ping the Techno Director, to have the changes merged into master, and deployed to the staging/production website.

Deployment Environment Variables

The following environment variables should be set on staging/production servers (also note that production environment should be used for both staging and production):

# Amazon AWS
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
S3_BUCKET
S3_HOST_NAME
AWS_REGION

# Service URLs
REDIS_URL
POSTGRES_URL
ELASTICSEARCH_URL

# Secret keys
DEVISE_SECRET_KEY
SECRET_KEY_BASE

# App configuration
RAILS_ENV

About

The content management system and frontend website for The Tech, MIT's oldest and largest newspaper.

thetech.com

Resources

Readme
License
Activity
Custom properties

Stars

25 stars

Watchers

11 watching

Forks

12 forks
Report repository

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.