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

Update docker-compose to remove the previously generated site and Jekyll metadata before building #3587

Closed
2 tasks done
aricforrest opened this issue Sep 28, 2022 · 4 comments · Fixed by #3741
Closed
2 tasks done
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Infrastructure For changes on site technical architecture role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less Status: Updated No blockers and update is ready for review

Comments

@aricforrest
Copy link
Member

aricforrest commented Sep 28, 2022

Overview

Jekyll does not always rebuild every file in the _site directory every build. This can cause old versions of files to be served.

Action Items

  • Update the docker-compose.yml file to run the jekyll clean command before the existing jekyll serve command.
  • Test updating a file in _projects to ensure the update reflects immediately when running docker-compose up.

Resources/Instructions

@aricforrest aricforrest added role: back end/devOps Tasks for back-end developers Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Sep 28, 2022
@github-actions github-actions bot added the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Sep 28, 2022
@aricforrest aricforrest added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Sep 28, 2022
@kathrynsilvaconway kathrynsilvaconway added Feature: Infrastructure For changes on site technical architecture Ready for Prioritization and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 4, 2022
@bishrfaisal

This comment was marked as resolved.

@bishrfaisal bishrfaisal added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Oct 17, 2022
@aricforrest aricforrest added the size: 0.5pt Can be done in 3 hours or less label Oct 17, 2022
@aricforrest

This comment was marked as resolved.

@blulady blulady added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 24, 2022
@bishrfaisal bishrfaisal added this to the 08. Team workflow milestone Nov 6, 2022
@Adastros Adastros self-assigned this Nov 19, 2022
@github-actions
Copy link

Hi @Adastros, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@Adastros
Copy link
Member

Adastros commented Nov 19, 2022

Availability: 2 - 8 PM 20NOV22, 9 - 11PM 21NOV22, 22NOV22
ETA: 11PM 22NOV22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Infrastructure For changes on site technical architecture role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less Status: Updated No blockers and update is ready for review
Projects
Development

Successfully merging a pull request may close this issue.

5 participants