Skip to content
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

data are not updated on the website #392

Closed
dadoonet opened this issue Jul 8, 2019 · 9 comments
Closed

data are not updated on the website #392

dadoonet opened this issue Jul 8, 2019 · 9 comments
Labels

Comments

@dadoonet
Copy link
Member

dadoonet commented Jul 8, 2019

http://data.brownbaglunch.fr/baggers.js is not published anymore.

For example Arthur Micoulet is in one of the latest commits but not present in http://data.brownbaglunch.fr/baggers.js.

@dadoonet dadoonet added the bug label Jul 8, 2019
@dadoonet
Copy link
Member Author

dadoonet commented Jul 8, 2019

image

@dadoonet
Copy link
Member Author

dadoonet commented Jul 8, 2019

I ran Jekyll locally to see if we have any error message but no luck. It worked locally.
Going to see if I can desactivate the website and reactivate again to trigger a new generation.

@dadoonet
Copy link
Member Author

dadoonet commented Jul 8, 2019

@kassovix
Copy link

Any news on this ?
Let me know if you need help.

@dadoonet
Copy link
Member Author

Sure. I haven't been able to reproduce the issue when building the pages locally.
If you want to try that'd be great.

@kassovix
Copy link

I can run the Jekyll site from https://github.com/brownbaglunch/BrownBagLunch but couldn't find out how you publish the https://github.com/brownbaglunch/bblfr_data/ to http://data.brownbaglunch.fr/baggers.js

@kassovix
Copy link

Ok nevermind, Jekyll is running and serving the baggers.js fine on http://localhost/baggers.js. Do not reproduce any problem here...

@kassovix
Copy link

kassovix commented Sep 20, 2019

Maybe you can try to rollback to the last commit successfully published : 3738085#diff-f68e2795800a6af5bcbab7a5fdb2f2c1
And see if it works with this version...

@dadoonet
Copy link
Member Author

It's fixed now. Was most likely caused by a security issue

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

No branches or pull requests

2 participants