jmg
/
baysec
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
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.
41 Commits
1 Branch
1.1 MiB
 
 
 
 
 
Tree: ff32a6f27a
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'ff32a6f27a'
${ noResults }
 ZIP  TAR.GZ
John-Mark Gurney ff32a6f27a add Feb's meetup 8 years ago
content add Feb's meetup 8 years ago
layout Remove prev/next links & post date. No one cares when posted. 9 years ago
publishers comment out debugging statement.. 9 years ago
.gitignore add mac turds to git ignore.. 9 years ago
README.md add descrption why clearing the deploy directory is needed 9 years ago
gennext.sh Remove duplicate date, add more description 9 years ago
info.yaml initial version of the BaySec website.. 10 years ago
notes.txt initial version of the BaySec website.. 10 years ago
requirements.txt convert over to s3 for publishing, add requirements.. 9 years ago
site.yaml add missing charset so it gets set properly.. 9 years ago

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 git@github.com:baysec/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