Skip to content

Use latest hugo for website #67

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

Closed
filiphr opened this issue Oct 22, 2017 · 3 comments
Closed

Use latest hugo for website #67

filiphr opened this issue Oct 22, 2017 · 3 comments

Comments

@filiphr
Copy link
Member

filiphr commented Oct 22, 2017

There were some issues when I used a newer version of hugo. Therefore, until now We were using 0.18. The problem was some new property (disablePathToLower, which by default is false) which caused the paths of the released articles to be lower case. We have fixed this.

In any case we need to add the version of hugo in our publish.sh so we are always using a fix version when doing a publish.

filiphr added a commit to filiphr/mapstruct.org that referenced this issue Oct 22, 2017
filiphr added a commit to filiphr/mapstruct.org that referenced this issue Oct 22, 2017
@filiphr filiphr mentioned this issue Oct 22, 2017
@gunnarmorling
Copy link
Member

+1 for mandating a specific version. Related to this, a great improvement would be to publish the website from Travis automatically after a push to master.

@filiphr
Copy link
Member Author

filiphr commented Oct 23, 2017

@gunnarmorling completely agree with you 😄. I don't think it would be too complex to add that to the build. However, it would mean that we need to allow Travis to push to our repo, that is OK for you I presume 😉.

@gunnarmorling
Copy link
Member

Applied the PR.

However, it would mean that we need to allow Travis to push to our repo, that is OK for you I presume

Yes, it would be ok. I don't know Travis very well, but there's a way for managing secrets such as credentials. We should use a dedicated account with the minimum set of permissions. Let's continue the discussion over at #69 which I just filed.

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

No branches or pull requests

2 participants