-
Notifications
You must be signed in to change notification settings - Fork 5
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 changes not reflected on website #9
Comments
D) the auto-deploy is unfortunately down. Sadly there isn't much I can do about, but the admin promised to fix it soon. I will keep you updated once it's fixed... |
Unfortunate indeed. Is there a manual deploy that can be used? |
Hmm we have never done this before. The reason why auto-deploy was disabled were some weird issues with Docker. |
The README in deploy should help hopefully. And docs of Docker-compose for the commands. Essentially it should be just 'pull' and 'up -d'. |
Hmm FYI that shortly broke the website as apparently our SSL redirect wasn't perfect: dlang-tour/core#537 |
We are back online 🎉 |
FWIW (in case you are wondering why the basic pages aren't shown): the (feel free to ping me for a manual redeploy) |
Thank you for deploying! I've merged #10, so you can redeploy whenever you can. |
Done: https://tour.dlang.org/tour/es/basics/imports-and-modules @stonemaster sometimes I run into the issues that you described:
which weirdly can only be fixed by retriggering a Travis job to rebuild the docker image...
However, it's there and |
Thanks again! Feel free to close this issue, if you wish. |
Several days ago I merged some changes. Surprised not to see those changes reflected in the website after so many days, I clicked around to understand the process a bit better and I found that changes should take around 10 minutes to be deployed thanks to the bot. Given that the changes aren't reflected yet, I have to assume that: a) the webhook isn't configured correctly, b) the bot is down, c) I broke something with my changes, or d) there's something else going on that I don't know about.
The text was updated successfully, but these errors were encountered: