Skip to content

Remove Heroku setup from installfest instructions #117

Closed

Description

@bridgethillyer

Since we no longer deploy a web app, the Heroku setup can be removed (or, at least, marked as optional) from the installfest instructions. Note: there are multiple versions of the instructions, so need to take them out from multiple places.

Activity

  1. andeemarks commented on Dec 9, 2014

    @andeemarks

    Hi Bridget,

    I would like to help out with this issue by way of harvesting some low hanging fruit, but for the life of me, I cannot find where the specific Installfest instructions referencing Heroku actually are :-( Any pointers would be most appreciated.

  2. k4y3ff commented on Dec 9, 2014

    @k4y3ff
    Member

    Hi, Andy!

    The installfest instructions are all under /setup/outline, where the appropriate files start with the word "setup".

    Alternatively, if you go to setup.md, there's mention of installing Git, and if you follow the links in that file for each operating system, there will be more references to Git on the pages for OS X, Windows 7, Windows 8, and Ubuntu.

    Cheers!

  3. andeemarks commented on Dec 9, 2014

    @andeemarks

    Ah, many thanks.

  4. andeemarks commented on Dec 9, 2014

    @andeemarks

    I have a first cut at a Heroku-less version of the OSX setup over at https://github.com/andeemarks/curriculum/blob/master/outline/setup_osx.md.

    I ended up adding steps to test running the Compojure app locally, which might now also be less valuable given there is no longer a web app in the Curriculum.... if so, the options would be:

    (a) the setup could just stop after the LightTable section
    (b) substitute a sample Quil app repo for https://github.com/heroku/clojure-sample.git for a more realistic test.

    I'm happy to do either (a) or (b) if either of those make sense.

  5. bridgethillyer commented on Dec 9, 2014

    @bridgethillyer
    MemberAuthor

    Thank you, @andeemarks! This is great.

    I think (a) is fine since it does have steps to confirm that everything we need is working. But (b) would be great, too, because it is an extra confirmation step and introduces Quil during the installfest.

  6. andeemarks commented on Dec 12, 2014

    @andeemarks

    Cool - I'm underway on option (a) - might take me a little while to get the screenshots for the Windows instructions though.

  7. duelinmarkers commented on Jan 17, 2015

    @duelinmarkers

    We're looking at merging these changes for Austin ClojureBridge. The only additional work that seems to be needed is providing git installation instructions (except for OS X, which already has them).

    The Ubuntu instructions are easy. Windows is a bit trickier.

    On the git-scm book site, they suggest that GitHub for Windows may be a better way to go than the plain git-scm Windows download. Does anyone know if that's good advice? I like the sound of "solid credential caching and sane CRLF settings."

  8. duelinmarkers commented on Jan 17, 2015

    @duelinmarkers

    My WIP is here: https://github.com/AustinClojure/curriculum/tree/rm-heroku -- currently I'm pointing at the git-scm download for Windows.

  9. k4y3ff commented on Feb 7, 2015

    @k4y3ff
    Member

    @duelinmarkers Did you want to open a PR for the changes from Austin Clojure's hack day? I see a couple relevant commits here, in particular.

  10. duelinmarkers commented on Feb 8, 2015

    @duelinmarkers

    If you think they look worth merging, I'll do that. (I think they are.)
    On Feb 6, 2015 7:49 PM, "Katherine Fellows" notifications@github.com
    wrote:

    @duelinmarkers https://github.com/duelinmarkers Did you want to open a
    PR for the changes from Austin Clojure's hack day? I see a couple relevant
    commits here https://github.com/AustinClojure/curriculum/commits/master,
    in particular.

    —
    Reply to this email directly or view it on GitHub
    #117 (comment)
    .

  11. added a commit that references this issue on Feb 8, 2015
  12. k4y3ff commented on Feb 8, 2015

    @k4y3ff
    Member

    Fixed via #126.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions