Install from single source (requirements.txt) when building docs.coopcloud.tech #564
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#564
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forgot to update Dockerfile and it caused a mismatch, we shouldn't need to update two sets of deps?
https://build.coopcloud.tech/coop-cloud/docs.coopcloud.tech/476
/cc @basebuilder
Install from single source (requirements.txt) when building coopcloud.techto Install from single source (requirements.txt) when building docs.coopcloud.techDoes this mean for
abra
? This was an oversight on my part as I updated all the deps inrequirements.txt
and only some of the deps inDockerfile
How would this solved with a single file?
Ah, I mean, in the build of the mkdocs install (nothing to do with
abra
). We specify dependencies in two places but it would be better if we only specificed it in one place. I have a quick patch for this... building...