toolshed/organising
toolshed/organising
8
1
Fork 0
Code Issues 120 Pull Requests Releases Activity

Install from single source (requirements.txt) when building docs.coopcloud.tech #564

New Issue
Closed
opened 2024-02-05 12:40:40 +00:00 by decentral1se · 2 comments
decentral1se commented 2024-02-05 12:40:40 +00:00
Owner
Copy Link

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

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
decentral1se added the
good first issue
coopcloud.tech
 labels 2024-02-05 12:40:40 +00:00
decentral1se changed title from Install from single source (requirements.txt) when building coopcloud.tech to Install from single source (requirements.txt) when building docs.coopcloud.tech 2024-02-05 12:41:22 +00:00
decentral1se added
documentation
 and removed
coopcloud.tech
 labels 2024-02-05 12:41:35 +00:00
basebuilder commented 2024-02-05 15:03:07 +00:00
Copy Link

Does this mean for abra ? This was an oversight on my part as I updated all the deps in requirements.txt and only some of the deps in Dockerfile

How would this solved with a single file?

Does this mean for `abra` ? This was an oversight on my part as I updated all the deps in `requirements.txt` and only some of the deps in `Dockerfile` How would this solved with a single file?
decentral1se commented 2024-02-05 23:53:21 +00:00
Author
Owner
Copy Link

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...

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...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abra
Everything to do with abra
abra-gandi
Abra Gandi plugin
awaiting-feedback
Ping/pong on comms
backups
bug
Something is not working
build
Go build related issues
ci/cd
Getting the robots into the mix
community organising
Opening this thing up
contributing
Contributors stuff
coopcloud.tech
Our main website
democracy
Democratic decision making
design
Design thinking required
documentation
Let's write things together
duplicate
This issue or pull request already exists
enhancement
New feature
finance
Money things
funding
Anything related to grant funding
good first issue
Easy start with development
help wanted
Need some help
installer
Installation related issues
kadabra
performance
Performance related
proposal
Large change which requires feedback & decisin making
question
More information is needed
recipes.coopcloud.tech
Our recipes catalogue
security
Securing our shit
test
Unit or integration test suite
wontfix
This won't be fixed
No Label
documentation
good first issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant abra-bot ammaratef45 Apfelwurm carla cas decentral1se fauno kawaiipunk knoflook lambdabundesverband moritz p4u1 simon trav val yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/organising#564
No description provided.
Delete Branch "%!s()"

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?