Discuss Source

Perhaps I should look at building a "nightly release" process. A couple of options are available:

  1. Pull the latest checkin from git, zip it up, and drop it in the downloads directory. This might be the "safest" (i.e. less likely to break spectacularly) way, however since I don't check code in to git regularly, it will be stagnant for several days or even weeks at a time. Will that really be "nightly"?
  2. Pull the latest live code from the directory where it lives on my system, zip it up, and drop it in the downloads directory. This will have a lower likelihood of getting stagnant for long periods of time, however the likelihood that it might break in spectacular fashion is significantly higher (as I may be in the middle of updating a block of code when it is pulled which might cause it to be inconsistent).

Any ideas are welcome.

-- AaronGraves Sun Jul 10 14:51:07 UTC 2016 (216.105.250.127)

Name:
Message:

Styling
**bold**, //italic//, __underline__, --strikethrough--, `teletype`
Headers
= Level 1 =, == Level 2 ==, === Level 3 ===, ==== Level 4 ====, ===== Level 5 ===== (ending ='s optional)
Lists
* Unordered List, # Ordered List, ** Level 2 unordered, ### Level 3 ordered (up to 5 levels, NO SPACES IN FRONT)
Links
[[Page]], [[Page|description]], [[http://link]], [[http://link|description]]
Images
{{image.jpg}}, {{right:image.jpg}} (right aligned), [[link|{{image.jpg}}]] (image linked to link), {{image.jpg|alt text}}
Extras
---- (horizonal rule), ~~~~ (signature)