Deployment about happy-git-with-r HOT 23 CLOSED

I obviously plan to start porting more content over ASAP as well, but that largely exists already! Getting deployment sorted out actually concerns me more.

from happy-git-with-r.

Sorry Jenny I was in appointments all day and just got home, you caught me on a bad day! I'll take a look soon

from happy-git-with-r.

That's where I am too.

from happy-git-with-r.

Maybe I'll focus on bringing some content over and see if you have any words of deployment wisdom for me in the next little while.

from happy-git-with-r.

Deployment looks very easy! There's two options:

• option #1 is to publish using RStudio Connect and it will be hosted on bookdown.org
  https://bookdown.org/daattali/happy-git-with-r/
  This is very very simple. Every time we make a change, we need to render the book (using bookdown::render_book()) and then call bookdown::publish_book()
• option #2 is to host on GitHub and use GitHub Pages. This is not too bad supposedly but will be a bit more work initially. If we do this, then we can set up travis so that every time we push a commit to the repo, it will re-render the book automatically. Option 1 is easier :)

from happy-git-with-r.

Re: option 1. I thought about that. But this is going to through a very awkward teenager phase and I don't want it up there during that time. But I don't want to wait until it's very developed to attempt the "real" deployment. That never ends well. I want to know I can fling it up there but have it be very obscure until we think it's ready for human eyeballs. From my quick read, wasn't clear if/how that would work. Can you determine that or conduct a small experiment?

Agree option 1 is easier. Though I'd love to sort out option 2. This is all a pilot study for larger renovations of STAT 545 stuff generally ....

from happy-git-with-r.

They do support the option of having it only visible to a whitelist of people, so that's not a problem. See image below. If option 1 is good enough for useR, I'd prefer to go with that. Because of time constraints I'd rather go the easier route for now and experiment with the github option next month?

from happy-git-with-r.

BTW I did exactly what you say re: RStudio Connect last week when I started this.

But when I logged back in, I could find no evidence of it. If I edit your URL and insert my username, it 404s. So is that some sort of temporary preview thing? Or have I done something really odd? Hmm ... upon further thought I have some memory of deleting the project.

We would need to understand this very well. I want stability, I want to rip this content out of STAT 545 and have it live in exactly one place. I want to tweet and link to this link.

I suspect we should bite the bullet and do the travis + github pages thing.

from happy-git-with-r.

I don't think it should get deleted, it should definitely still be there... if you go to https://bookdown.org/connect/#/documents do you not see anything?

from happy-git-with-r.

No, no documents found. But I think I deleted it. I think this is really about the URL at this point. Well, that, and you sweating through the travis stuff 😅.

from happy-git-with-r.

OK if you really want to do a github deploy, we can do that. I got it working with my version: http://daattali.github.io/happy-git-with-r/

It's actually not too bad. If you want to make the CURRENT repo a github page, it'll be at jennybc.github.io/happy-git-with-r so maybe you'll want to create a new git user for this, or somehow make the URL a bit better?

The steps are:

• add a file .nojekyll
• create a gh-pages branch
• create a build script that will render the book
• create a deploy script
• create a GitHub PAT that has "repo" permission and set the global variable GH_TOKEN on your travis machine
• call the build & deploy scripts with travis
• every time you push a commit with any change in the book content, the book will get regenerated and the website will have the updated version within minutes

I'll be in Berkeley starting the 19th - when are you arriving to the area? I'm pretty sure your travis and github knowledge is better than mine so I'd feel more comfortable if we do this together for the real deal

from happy-git-with-r.

Maybe it's time to get another domain name? Thanks for piloting all of that. Agree I should be able to close the deal.

from happy-git-with-r.

I think spending the ~15$ yearly for a domain would be totally worth it if
you plan on using this git book more long term.
On Jun 16, 2016 02:12, "Jennifer (Jenny) Bryan" [email protected]
wrote:

Maybe it's time to get another domain name? Thanks for piloting all of
that. Agree I should be able to close the deal.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA6IFIf2WFdKJcdP7KA6jjMkUuztfUXuks5qMOlVgaJpZM4I1jyF
.

from happy-git-with-r.

Suggestions for domain name are welcome.

from happy-git-with-r.

Is this book planned to remain focused on git and r?
On Jun 16, 2016 02:20, "Jennifer (Jenny) Bryan" [email protected]
wrote:

Suggestions for domain name are welcome.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA6IFKvdJ4gtDy38r9CzguF0no60awqrks5qMOssgaJpZM4I1jyF
.

from happy-git-with-r.

yes I think so

from happy-git-with-r.

ACK! This, this is exactly what I don't want. Somehow your version of this non-existent book is on the front page of bookdown.org. CAN YOU BRING THAT DOWN ASAP?

I want to know how to develop, deploy, develop, deploy .... and eventually publicize.

BTW how did you even do that? For me bookdown::publish_book() only puts it at:

https://beta.rstudioconnect.com/jennybc/happy-git-with-r/

from happy-git-with-r.

Huh, I guess they automatically show the most recent. OK it's deleted now, but there's still a link on that page that now goes to a 404 and will probably be removed soon. Not sure why my publish_book went to the real website and not to a beta Connect :S Do you want me to take down http://daattali.github.io/happy-git-with-r/ too? That link is not posted anywhere except here

from happy-git-with-r.

This is exactly why I deleted my Connect project last week when I paused working on this. (And then promptly forgot about that, then wondered where it went ...). I was paranoid about this thing appearing at bookdown.org.

I don't really care about the other link but maybe yes bring it down next chance you get.

I opened an issue on bookdown asking about this.

from happy-git-with-r.

I am now the proud owner of

happygitwithr.com

So I guess this is the plan:

travis to build

deploy to GitHub pages

custom domain

from happy-git-with-r.

and you're also the proud owner of a brand new selfie and github bio!

Good domain. This of course doesn't change anything as far as build/deployment goes. The domain should just be a one-time setup thing. I haven't tried setting up a CNAME with a github repo that isn't your username.github.io, but I imagine it works easy enough

from happy-git-with-r.

The selfie is because the Faces API thought I was 50 based on a previous one! Good grief. I had to fix that, but honesty compels me to use a recent photo. Taken today in fact.

from happy-git-with-r.

Got this working.

http://happygitwithr.com

Quick notes.

Good example: https://github.com/coatless/statprogramming.

That basically follows the directions here: https://bookdown.org/yihui/bookdown/github.html.

Moving parts = build script, deploy script, create new PAT, encrypt and put into .travis.yml, turn travis on for repo.

Something that was very important on Travis but is mentioned nowhere: have a DESCRIPTION file. Put bookdown in Imports and Remotes.

Key bits re: custom domain:

• CNAME file holds just this: happygitwithr.com
• sceengrab of DNS set up on hover

from happy-git-with-r.