Skip to content

Instantly share code, notes, and snippets.

@mberman84
Created October 4, 2023 16:53
Show Gist options
  • Star 14 You must be signed in to star a gist
  • Fork 4 You must be signed in to fork a gist
  • Save mberman84/9d4aedea777f540d3c537cfa78a2877a to your computer and use it in GitHub Desktop.
Save mberman84/9d4aedea777f540d3c537cfa78a2877a to your computer and use it in GitHub Desktop.
MageGPT Installation
# once you have an app created and downloaded:
curl -sSL https://get.wasp-lang.dev/installer.sh | sh
cd {app_folder}
# to install NVM:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
nvm install 18
nvm use 18
wasp db migrate-dev
wasp start
@nkoch95
Copy link

nkoch95 commented Oct 23, 2023

When I install Wasp a warning apears:

It looks like '/home/nicolas_koch/.local/bin' is not on your PATH! You will not be able to invoke wasp from the terminal by its name.
You can add it to your PATH by adding following line into your profile file (~/.profile or ~/.zshrc or ~/.bash_profile or ~/.bashrc or some other, depending on your configuration):export PATH=$PATH:/home/nicolas_koch/.local/bin

How do I solve this

@jonwash
Copy link

jonwash commented Oct 27, 2023

Determine Your Shell:
Before adding the path, determine which shell you're using as the file you'll modify depends on it.

bash
Copy code
echo $SHELL
Based on the output:

If it's /bin/bash, you'll modify ~/.bashrc.
If it's /bin/zsh, you'll modify ~/.zshrc.

Add to PATH:
Based on the shell you're using, run one of the following commands:

For bash:
echo "export PATH=$PATH:/root/.local/bin" >> ~/.bashrc
source ~/.bashrc

For zsh:
echo "export PATH=$PATH:/root/.local/bin" >> ~/.zshrc
source ~/.zshrc

Verify:
After updating and sourcing the profile or rc file, you should be able to run the wasp command directly from the terminal.

Note: It's unusual for regular users to install software under the /root directory. Generally, software for regular users gets installed under their home directory (e.g., /home/username). Make sure you're not accidentally running commands as the root user unless it's necessary.

@rajivsingha
Copy link

Hi there,

It doesn't the part about needing Docker to run the DB. PostgreSQL that is. Do you think you can add the instructions to your gist for that?

I get the error when

--- [Error] Can not connect to database: ---------------------------------------

The database needs to be running in order to execute this command. You can easily start a managed dev database with wasp start db.

When I ran "wasp start db", I got another error

--- [Error] Couldn't find docker executable: ---------------------------------

To run PostgreSQL dev database, Wasp needs docker installed and in PATH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment