GitHub/Publishing about moderndive_book HOT 13 CLOSED

For reference whenever we switch moderndive.com over later: https://www.edwinksl.com/blog/set-up-website-with-pelican-google-domains-and-netlify.html

from moderndive_book.

fancy!

from moderndive_book.

This YouTube video should be helpful. Here are instructions on transferring the repo.

from moderndive_book.

• Custom domains: wow, easy-peasy. How do you want to manage the dev vs release on moderndive.com?
• You have repository creation permissions in the moderndive GitHub Org, so you should be able to transfer it.

from moderndive_book.

I think it does make sense to have master be the current "stable" release deployed to https://www.moderndive.com. It might make more sense for us to just convert the current master (whenever it is ready--should probably should for sometime on Wednesday to give us time to check this all out before Data Day Texas on Saturday?) to 0.3.0 instead of trying to put 0.2.0 that current lives on ModernDive.com into a repo as well. (We can copy over all of the older versions including 0.2.0 into different folders on master that deploy to ModernDive.com as needed.)

We can then use the dev branch to be where we make changes and improvements. The "live, on-the-fly" sorts of changes (where we don't build the docs folder can be pushed to gh-pages and then to https://moderndive.netlify.com, which is what I would probably share with your students).

I don't think there is really a need for us to also deploy to https://moderndive.github.io/moderndiver-book, is there?

from moderndive_book.

Repo has been transferred! https://github.com/ismayc/moderndiver-book now redirects to https://github.com/moderndive/moderndiver-book

from moderndive_book.

Unfortunately the book itself link doesn't transfer. https://moderndive.github.io/moderndiver-book/ works, but https://ismayc.github.io/moderndiver-book/ does not. What's the best way to message that people should update their bookmarks to https://moderndive.netlify.com from https://ismayc.github.io/moderndiver-book/? I wonder if we will have to create a repo on my GitHub account with the same name that has GitHub Pages set up with a page that only has a message saying go to https://moderndive.netlify.com instead? Bummer.

from moderndive_book.

Maybe just put a README in https://ismayc.github.io/moderndiver-book/, like you say?

from moderndive_book.

Yeah, I think we should just have it be a webpage with a link to the new one and then update the README in ismayc/moderndiver-book to point to the new repo as well. We can do that when we meet up next.

from moderndive_book.

To clarify, this is what we are thinking when we move to 0.3.0 soon:

moderndive-dev.netlify.com comes from gh-pages which is populated from the dev branch on moderndive/moderndive-book. We could also set up moderndive.netlify.com to come from docs in the master branch on moderndive/moderndive-book which would then be sent to moderndive.org and then re-routed to moderndive.com via Google Domains.

from moderndive_book.

This is the modified workflow:

moderndive.netlify.com comes from gh-pages which is populated from the master branch on moderndive/moderndive-book. We could also set up moderndive-release.netlify.com to come from docs in the (to be created) dev branch on moderndive/moderndive-book which would then be sent to moderndive.org and then re-routed to moderndive.com via Google Domains. We will build the book locally and push to the docs folder ONLY on major releases of the book. moderndive.github.io/moderndive_book is from master/docs and is a backup to ModernDive.org (the stable version).

from moderndive_book.

@ismayc Is my understanding correct that the only outstanding element of this issue is cutting out HostGator from the modified workflow?

from moderndive_book.

@rudeboybert I believe so.

from moderndive_book.