Skip to content

Create a "live" branches config for books #1421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 19, 2019

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Nov 18, 2019

We've wanted for a while to mark old versions of books as "noindex" and,
probably, to remove the edit_me links from them. This creates a config
entry for conf.yaml to mark branches as "live". If this list is
specified then everything not in the list will be marked as noindex.
In the future we might remove the edit links from it was well.

This applies that config change to the installation and upgrade guide,
just to apply it to something for testing. I think we'll want to apply
it to most books eventually.

We've wanted for a while to mark old versions of books as "noindex" and,
probably, to remove the `edit_me` links from them. This creates a config
entry for `conf.yaml` to mark branches as "live". If this list is
specified then everything *not* in the list will be marked as `noindex`.
In the future we might remove the edit links from it was well.

This applies that config change to the installation and upgrade guide,
just to apply it to something for testing. I think we'll want to apply
it to most books eventually.
Copy link
Member

@JoshMock JoshMock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Contributor

@olksdr olksdr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left only one question, otherwise it looks good to me.

end
yaml
end
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you build here a lot of yaml by hand. Maybe it's worth pulling yaml lib for this and use ruby hashes/lists to build the structure you want and then just to_yaml it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to investigate that again.... The last time I tried it didn't work because the yaml library emitted yaml that perl couldn't read!

@nik9000 nik9000 merged commit 691f183 into elastic:master Nov 19, 2019
@nik9000
Copy link
Member Author

nik9000 commented Nov 19, 2019

Relates to #1419.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants