jmg
/
baysec
1
0
Forka 0
Codice Problemi 0 Pull Requests 0 Rilasci 0 Wiki Attività
BaySec website source
Non puoi selezionare più di 25 argomenti Gli argomenti devono iniziare con una lettera o un numero, possono includere trattini ('-') e possono essere lunghi fino a 35 caratteri.
37 Commit
1 Ramo (Branch)
1.1 MiB
 
 
 
 
Albero (Tree): f2b3eea27b
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da 'f2b3eea27b'
${ noResults }
 ZIP  TAR.GZ
John-Mark Gurney f2b3eea27b add mac turds to git ignore.. 6 anni fa
content add Oct meetup 6 anni fa
layout Remove prev/next links & post date. No one cares when posted. 7 anni fa
publishers comment out debugging statement.. 7 anni fa
.gitignore add mac turds to git ignore.. 6 anni fa
README.md add descrption why clearing the deploy directory is needed 7 anni fa
gennext.sh Remove duplicate date, add more description 7 anni fa
info.yaml initial version of the BaySec website.. 7 anni fa
notes.txt initial version of the BaySec website.. 7 anni fa
requirements.txt convert over to s3 for publishing, add requirements.. 7 anni fa
site.yaml add missing charset so it gets set properly.. 6 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 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