Question
What is the correct structure for the build file in the lib folder of a serverless function?
- Posted on May 31, 2023
- DigitalOcean FunctionsPythonServerless
Asked by Peter Aling
I have been implementing serverless functions (python) and would like to implement multiple packages under one app. Each of these functions require access to a separate toolset (toolset.py) which I’ve placed in the lib folder. Since the toolset requires additional python libraries (psycopg2), I’ve created a requirements.txt file within the lib folder and an associated build.sh file.
I have followed the same build.sh structure in the tutorials but on compilation, I receive the following error:
╭──────────── project build ───────────╼
│ Started running ./build.sh in /.app_platform_workspace/lib
│ ./build.sh: line 5: virtualenv: command not found
│
│ › Error: './build.sh' exited with code 127
The code is hosted on Github and remote builds are triggered on repo updates.
What is the correct structure for the build.sh file in the lib folder?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Hi there,
The contents of the
libfolder and the contents of each function’s directory affect what is included in each deployed function and how that function is built.Here is also an example project that might help:
https://github.com/digitalocean/sample-functions-todo/tree/main
The structure is more or less just the
build.shfile and your library.Here is also another example on how this is implemented:
https://github.com/digitalocean/functions-deployer/tree/main/e2e/use-lib/lib
The above is from an end-to-end test and includes a simple use of the
libdirectory and abuild.shfile.If your serverless function repository is public, feel free to share it here and I will be happy to take a further look at why the builds might be failing.
Best,
Bobby