Skip to content
This repository has been archived by the owner on Apr 29, 2019. It is now read-only.

clear and easy clutter install path(s) #68

Closed
2 tasks
science-girl opened this issue May 8, 2018 · 6 comments
Closed
2 tasks

clear and easy clutter install path(s) #68

science-girl opened this issue May 8, 2018 · 6 comments
Assignees

Comments

@science-girl
Copy link
Contributor

science-girl commented May 8, 2018

As a new clutter user I want the install instructions to not confuse me, and have a very easy time following them while installing them so I can successfully install it.

Current release zip (Feb 13th) is missing the react ui-src folder, meaning the README instructions don't apply.

  • new clutter release zip
  • update readmes to clarify using the source vs. the release version
@science-girl science-girl self-assigned this May 8, 2018
@celestialhanley celestialhanley changed the title Add new release zip add new release zip May 9, 2018
@philipbeadle
Copy link
Contributor

You dont need the ui-src folder as its compiled into UI.

@zippy zippy changed the title add new release zip clear and easy clutter install path(s) May 15, 2018
@zippy zippy added next and removed backlog labels May 15, 2018
@zippy
Copy link
Member

zippy commented May 22, 2018

so it turns out that we MUST include a ui build in at least the develop and master branches. The reason for this is that hcdev init -cloneExample=clutter will fail otherwise. This command does a git clone into \tmp and then copies over just the standard set of directories dna test and ui. And we want people to be able to do that and having a running ui without having to do the npm build step.

@philipbeadle
Copy link
Contributor

Can we change hcdev init -cloneExample=clutter to pull from the latest Release?

@zippy
Copy link
Member

zippy commented May 24, 2018

Well, I don't like that because this is already also implemented: hcdev init -cloneExample=clutter -fromDevelop and also hcdev init -cloneExample=clutter -fromBranch=your-branch-here I guess we could figure out a new pattern going forward that takes into account the build cycle, but I don't want to do that last minute before alpha 1.

@bboyatwork
Copy link
Contributor

Should we use the current develop branch in order to create the new clutter release zip @zippy @philipbeadle. Thinking the 'archive' link the instructions needs to be updated. Anything specific that needs to be updated in the README you all see, I'm not clear if anything needs to be changed based on the previous comments. @science-girl thoughts?

This is all I've added so far to hopefully clarify some of the wording:
...
Dependencies: If you want to run Clutter locally, you will need nodejs (https://nodejs.org/en/) (LTS) installed, with npm or yarn (https://yarnpkg.com/lang/en/docs/install):

The following commands will clone the latest build of clutter to your machine and then you will either install npm or yarn to build the UI for the app. (this)

git clone https://github.com/Holochain/clutter.git
cd clutter/ui-src
npm install # (or yarn install)
npm run build # (or yarn build)
cd ..

Running Clutter (this)

Now if you want to run the app, you can run:

hcdev web # if you want to just run it temporarily and test it out, with scratch data

or

hcd web # if you want to really start to use the app

@science-girl
Copy link
Contributor Author

science-girl commented May 24, 2018 via email

bboyatwork added a commit that referenced this issue May 25, 2018
Addressing #68 Clarifying Clutter install path and links.
@zippy zippy closed this as completed May 28, 2018
@zippy zippy removed the in progress label May 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants