digitalocean / digitalocean/sample-functions-python-jokes

Where to put tests and venv folders?

Offen
#8 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
40
Forks
60
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

When working on my own DO function, I created a tests folder (with unit and integration tests) as well as a virtualenv in the root folder of the project (including a bin, lib, lib64. include and share folder). But when running the `doctl sbx deploy` command from the root folder of the project (same location as the project.yaml file), it failed with an error saying that the bin folder was larger than the allowed 250KB. Only by removing all the virtualenv folders (and thus making the project non-runnable locally) did I manage to upload the function code.

Is there a list of folders that the doctl deploy command will ignore by default? Or is there a way to manually specify folders to ignore when deploying? Or is there an alternative way of structuring the project that avoids the problem of the deploy command trying to upload unrelated folders?

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start by reproducing `doctl sbx deploy` from the project root with the `tests` and virtualenv folders present, using the existing `project.yaml`. Check how deployment selects files and whether ignored folders or a configurable exclusion mechanism is documented; done means the project can retain its local test and virtualenv folders while deployment excludes them and stays within the size limit.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python
Bereich
cli, cloud
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.