jmg
/
baysec
Segui 1
Vota 0
Forka 0
Codice Problemi 0 Pull Requests 0 Rilasci 0 Wiki Attività
BaySec website source
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
64 Commit
1 Ramo (Branch)
Ramo (Branch): master
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da 'master'
${ noResults }
John-Mark Gurney a22b755d58 update places to complete the move off github 3 mesi fa
content add next meeting.. 3 mesi fa
layout update places to complete the move off github 3 mesi fa
publishers comment out debugging statement.. 2 anni fa
.gitignore add mac turds to git ignore.. 2 anni fa
Makefile add next month's baysec.. add Makefile for deploy.. 1 anno fa
README.md update places to complete the move off github 3 mesi fa
gennext.sh add support for OpenGraph, and twitter cards... 2 anni fa
info.yaml initial version of the BaySec website.. 3 anni fa
notes.txt initial version of the BaySec website.. 3 anni fa
requirements.txt convert over to s3 for publishing, add requirements.. 3 anni fa
site.yaml add missing charset so it gets set properly.. 2 anni fa

README.md

BaySec Website Source

Source to build the BaySec website.

This is now hosted on AWS CloudFront + S3. The move off github pages was required due to the lack of SSL support for custom domains.

Instructions

  1. Clone this repository: git clone ssh://git@git.funkthat.com:822/jmg/baysec.git
  2. Change directory in the cloned repo: cd baysec
  3. Make sure deploy directory is clean: rm -rf deploy This is needed as hyde does not track deps properly.
  4. Generate new content: hyde gen
  5. Make sure AWS keys are in environment: . ./.key.txt
  6. Publish to S3: hyde publish