Closed edrf12 closed 4 days ago
Looks like this issue is caused by the actix-web
crate, but I don't think this is the actual problem.
Argon automatically moves/copies its binary to the ~/.argon/bin/argon
when it gets first launched. Could you verify that the proper executable is used? Just run whereis argon
or to be sure remove ~/.argon/bin
directory, run Argon, and check whether you get Installation completed! Do you want to remove this executable?
prompt.
My argon never does that, I've just deleted the ~/.argon folder, and ran ./argon (in downloads folder), all it does is say what commands are available. The folder is created again but it never moves itself there, even when run as root.
I just moved argon to the ~/.argon/bin folder and I think it now works fine, but installation is completely broken, if needed I can open another issue for that
I daily drive macOS and have never had a similar issue so I don't think the installation process is broken. However, on your side, it clearly fails (see the second line of the logs - unsupported shell
error) so it appears to be caused by the shell you use. Could you give me its name?
My main shell is fish, but I tried running argon on bash as well and it didn't install either. Maybe it would have worked fine if I had used zsh?
Yeah fish is not supported, I'm going to add list of the supported shells to the wiki.
You can give zsh a try though bash should have worked just fine. Could you check if Argon throws the same unsupported shell
error when using bash and zsh?
I will try it but I’d have to serve a project to serve a project to see the error since verbose is not available without a command.
Message ID: @.***>
I'm not sure what you mean. Just run argon serve -vvvv
on any project.
I'm closing this issue as it's no longer relevant but feel free to re-open it.
I have installed the cli using the file downloaded from GitHub, it was placed in /usr/local/bin/argon and has the following permissions
Running
argon serve -vvvv
(File paths truncated)Running as root does work but it complicates my workflow since files that are synced back will be owned by root preventing write by my user.