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

deploy #80

Open
harlantwood opened this issue Aug 3, 2016 · 4 comments
Open

deploy #80

harlantwood opened this issue Aug 3, 2016 · 4 comments

Comments

@harlantwood
Copy link
Collaborator

harlantwood commented Aug 3, 2016 •
edited
Loading

@RichardLitt would you care to manage a deploy? would be good to have someone else try it:

  1. have an ipfs daemon running
  2. npm install && npm prune
  3. (kill your npm run dev script if you happen to have it running)
  4. npm run publish # this should open the published page on the gateway
  5. pin the hash
  6. post to https://github.com/ipfs/ops-requests/issues

We should probably add these instructions to the readme as well...
@RichardLitt
Copy link
Collaborator

Sure. Should I deploy it now?

@harlantwood
Copy link
Collaborator Author

I suggest merging the outstanding PRs first, manually sanity checking, then yes

@harlantwood
Copy link
Collaborator Author

@RichardLitt do you have bandwidth for this at the moment? If not I can take this one.

RichardLitt added a commit that referenced this issue Aug 10, 2016
@RichardLitt
Added deploy section
da33369 
See #80
@RichardLitt RichardLitt mentioned this issue Aug 10, 2016
Merged
@RichardLitt
Copy link
Collaborator

See ipfs-inactive/ops-requests#28. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@harlantwood @RichardLitt