Documentation disaster is ahead

[techtonik]

I see that my commit is not online 95c41f6

And the day somebody decides to follow the README.md to push it will probably kill other changes that are alive.

The solution is to merge changes from the source branch, kill it and setup Sphinx to regenerate HTML in master from _sources/ without overwriting them.

[matthew-brett]

I guess the solution is to have a travis process that pushes to github automatically, but for now, I've just pushed the current master. Feel free to give me a push if it gets out of date again.

[techtonik]

Thanks. I will try to create an exemplary Sphinx project that contains both readable HTML site and sources in one branch.

[matthew-brett]

Will that solve anything though? Unless you're suggesting that the PRs have the source and the built HTML together?

[njsmith]

Different branches (or even repos), with travis responsible for syncing
between them, certainly seems like the easiest approach to me.

On Thu, Feb 11, 2016 at 1:01 AM, Matthew Brett [email protected]
wrote:

Will that solve anything though? Unless you're suggesting that the PRs
have the source and the built HTML together?

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

Nathaniel J. Smith -- https://vorpus.org http://vorpus.org

[techtonik]

Unless you're suggesting that the PRs have the source and the built HTML together?

Yes. Edit the source, preview it locally and commit both.

Different branches (or even repos), with travis responsible for syncing between them, certainly seems like the easiest approach to me.

Yes, but I have no idea how that is set up.

[njsmith]

There's probably some less terse explanation of how this works somewhere,
but:
https://github.com/matplotlib/matplotlib/blob/master/.travis.yml#L147-L169

(or the matplotlib folks are probably happy to explain more, they're
friendly)

On Thu, Feb 11, 2016 at 1:20 AM, anatoly techtonik <[email protected]

wrote:

Unless you're suggesting that the PRs have the source and the built HTML
together?

Yes. Edit the source, preview it locally and commit both.

Different branches (or even repos), with travis responsible for syncing
between them, certainly seems like the easiest approach to me.

Yes, but I have no idea how that is set up.

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

Nathaniel J. Smith -- https://vorpus.org http://vorpus.org

[techtonik]

That's a good example. I don't think explanation is necessary - just some time to read where to configure Travis deploy key and why to encrypt it. If the key appears to be present on Travis site only.

[njsmith]

The key that has write access to github is stored in the .travis.yml file
at the top, where anyone can see it, so it has to itself be encrypted with
a key that only Travis knows.
On Feb 11, 2016 1:46 AM, "anatoly techtonik" [email protected]
wrote:

That's a good example. I don't think explanation is necessary - just some
time to read where to configure Travis deploy key and why to encrypt it. If
the key appears to be present on Travis site only.

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

[techtonik]

Now somebody needs to enable Travis for this repository