8000 shows 404 error on Jekyll error · Issue #14 · Glavin001/GitLab-Pages · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

shows 404 error on Jekyll error #14

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.

Sign up for GitHub

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

Jump to bottom
Open
phillipthel 8000 en opened this issue May 11, 2015 · 2 comments
Open

shows 404 error on Jekyll error #14

phillipthelen opened this issue May 11, 2015 · 2 comments
Assignees
@Glavin001
Labels
enhancement
Milestone
v0.2.0

Comments

@phillipthelen
Copy link

It would be nice if the old version of the page could still be served and the user who pushed would be notified about the error via email or similar. That way jekyll errors wouldn't result in accidental downtime.
@Glavin001
Copy link
Owner

Great idea

@Glavin001 Glavin001 self-assigned this Jun 15, 2015
@Glavin001 Glavin001 modified the milestone: v0.2.0 Jun 15, 2015
@Glavin001
Copy link
Owner

3 Directories:

  • clone directory
  • temp directory
  • pages directory

When a project's page is being updated, clone / pull the changes into the clone directory. Then run jekyll and build pages into the temp directory. This is where errors will be caught. Finally, if building the pages is successful, move the entire directory from temp directory to pages directory.

Currently GitLab Pages only have a clone directory and pages directory. With the above, we can safely push changes that may break. Furthermore, we can add support for emailing errors to users given the email of the commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Glavin001 Glavin001

Labels
enhancement
Projects
None yet
Milestone
v0.2.0
Development

No branches or pull requests
2 participants
@phillipthelen @Glavin001
0