You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Modal seems like an awesome product that I've just started playing around with.
One thing I'm particularly interested in doing is using modal to just quickly spin up a GPU on a local working dir (ie. like modal launch jupyter --mount .) It'd be great if there was some way to exclude certain files from being mounted in the cli (ie. so I can ignore my .venv or something)
Also it would ideally be possible to pass secrets with modal launch.
The text was updated successfully, but these errors were encountered:
MiroFurtado
changed the title
Support for something like a .modalignore?
[Feature Request] Support for something like a .modalignore?
Jan 13, 2025
Hi, thanks for your question. We probably aren't going to support a separate .modalignore file. It's possible that will change in the future, but we're somewhat philosophically committed to keeping as much configuration within the Python source files themselves rather than making behavior depend on the existence of other local files.
However we now support passing dockerignore-style patterns in a number of Image methods, e.g. Image.add_local_dir (docs). There's less of an obvious way to leverage that through the modal launch CLI, but note that modal launch is somewhat meant to provide a template that you could take and extend yourself if you need additional flexibility or features.
Hi! Modal seems like an awesome product that I've just started playing around with.
One thing I'm particularly interested in doing is using modal to just quickly spin up a GPU on a local working dir (ie. like
modal launch jupyter --mount .
) It'd be great if there was some way to exclude certain files from being mounted in the cli (ie. so I can ignore my.venv
or something)Also it would ideally be possible to pass secrets with
modal launch
.The text was updated successfully, but these errors were encountered: