Skip to content

Conversation

@csegarragonz
Copy link
Collaborator

@csegarragonz csegarragonz commented Feb 20, 2023

In this PR I make two important changes to the way we interact with Faasm.

First, I move the ./bin/cli.sh bash script to an invoke task. This solves a long-running, recurring, error newcomers to Faasm where facing: even though you need to activate the virtual environment to start a cluster, you can not start the CLI container from a virtual-environment-activated shell (see #636). (NB: the migration to python does not actually solve the issue, but given that I had to modify the script, I prefered to port it to Python tasks).

In addition, I modify the cluster task (and the quick-start test) to also run a cluster with the latest code version (not the latest tag). This can be enabled/disabled with the inv cluster.start [--detached] flag.

Closes #636

@csegarragonz csegarragonz changed the title Quick Start Remove ./bin/cli.sh and mount checked-out code in quick start tests Feb 27, 2023
@csegarragonz csegarragonz changed the title Remove ./bin/cli.sh and mount checked-out code in quick start tests Move ./bin/cli.sh to inv May 3, 2023
@csegarragonz csegarragonz changed the title Move ./bin/cli.sh to inv Move ./bin/cli.sh to an invoke task May 3, 2023
@csegarragonz csegarragonz mentioned this pull request May 3, 2023
45 tasks
@csegarragonz csegarragonz mentioned this pull request Aug 2, 2023
@csegarragonz csegarragonz deleted the quick-start branch October 12, 2024 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue with FAASM_BUILD_DIR

2 participants