Skip to content

Conversation

Grummfy
Copy link
Contributor

@Grummfy Grummfy commented Jun 9, 2017

here it is.

  • first we build the website
  • then we rn a tool that check the validity of what's builded, validate the html output

More information on travis configuration => https://docs.travis-ci.com/user/customizing-the-build

@Grummfy
Copy link
Contributor Author

Grummfy commented Jun 9, 2017

to make it works:

fix for #16

@MetalArend
Copy link
Contributor

Looking at the Travis documentation now. There's some possibilities with docker-compose, so we could re-use the image from the development environment (which is a github-pages optimized jekyll container), instead of building the complete jekyll environment ourselves. WDYT?

I'll be looking into it next week, I'll keep you posted.

@Grummfy
Copy link
Contributor Author

Grummfy commented Jun 11, 2017

honestly I'm not understand why usign docker compose instead of a simple docker for this, but yeah travis allow it. I just try to go to the essential ;)

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.

2 participants