while deploying a Phoenix project, on Heroku it is saying mix command not found
I checked the Buildpacks of elixir and Phoenix are installed, pushed the code also before running the task.
tried after doing changes in the bashrc file (commented the code for "if not running interactively, don't do anything")
also tried with a change in the .profile file ($HOME/.asdf/asdf.sh)
although "mix phoenix.server" is working fine
heroku run 'POOL_SIZE=2 mix test.task'
Running POOL_SIZE=2 mix test.task on ⬢ evening-hollows-99899... up, run.2532 (Free)
bash: mix: command not found
Related
I ran npm run dev on the server with Laravel 9 using Vite and Tailwind. Now when I run npm run build it is still trying to load the css and javascript files from a domain 127.0.0.1. I can not get it back to reading the manifest.json in the build folder and loading those files.
npm run build runs without any errors,
however the npm run dev was throwing errors and I killed the process and double cheked using ps aux, and pkill commands.
I am lost.
nvm, for some reason the command
pkill npm
does not work I had to use
kill -9 [process-id]
and it worked.
I wrote a program in VS Code for a Discord bot, and I am trying to run it in Heroku. I was using the Heroku CLI and navigated to the folder with the code in my Command Prompt (I'm on Windows). I tried to add and push my main code, but I got the error in the picture below.
How can I resolve this issue? I am using Windows and my code is in VS Code.
The error states that heroku is unable to determine the language of your project.
You should add a requirements.txt file with the python package names used in your project to allow heroku to detect it as a python project.
Other options include using a setup.py file or Pipfile.
You can also manually set the buildpack using
heroku buildpacks:set heroku/python
in the heroku CLI
For more information check the documentation
I'm working on a Drupal 8 site which is deployed on Heroku, how would I run Drush or Drupal commands on here? When I try it with the built in command line on the Heroku site it complains about MySQL not being present. Is it possible to run Drush or Drupal commands on Heroku? Could I run the commands locally but somehow connect to the Heroku boxes?
I got in touch with Heroku support and managed to resolve the problem, in order to install MySQL you have to use their buildpacks.
If you go to your App > Settings > Buildpacks section you can add https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku-community/apt.tgz which from what I understand allows you to install packages using an Aptfile in your repository.
Once that Buildpack has been added in the root of your code that's deployed to Heroku add a file named "Aptfile", no extension and add the following two lines to it:
mysql-common
mysql-client
I'm not sure if mysql-common is needed but mysql-client certainly is. Deploy this to your Heroku environment and you should be able to run Drush commands now, be sure to add that Buildpack before adding the Aptfile as adding the Buildpack only adds it on the next environment build which happens with a new commit.
Running Drush is pretty easy ones you've done this. To do it via the web interface click the "More" button near the top right of the screen when you're looking at your app in Heroku and select "Open Console" then enter bash in the new panel and click "Run". Now you should be able to run Drush commands from here.
If you want to run the from your local terminal use https://devcenter.heroku.com/articles/one-off-dynos#an-example-one-off-dyno in the Heroku CLI (which you'll have to install). You may have to use the --dyno or --app flags to run Drush in the correct place.
I am using the instructions given on their site for MacOS- https://ipfs.io/docs/install/#installing-with-ipfs-update
[tutorial][1]
To build demo, clone this repo and run the following command:
$ cd contracts
$ npm install
Running the demo
To run demo, first run testrpc by running:
$ testrpc
Then compile and deploy the solidity contracts:
$ truffle compile
$ truffle migrate
Run an instance of IPFS to enable uploads:
$ ipfs daemon
Finally to build website, run:
$ npm run dev
I reached this last step (npm run dev) and I got an error message saying "npm missing scripts dev"
I am in the contracts directory specified, and installed everything there properly I believe. However, I don't see any dev script in the json package(s) which I believe could be being referenced using the npm run dev command. May this be the problem?
Here are the files wihin the folder contracts-master
app
index.html
javascripts
stylesheets
contracts
**ethpm.json** This one?
img
LICENSE
Lockup.sol
migrations
**package.json** Or this one?
Readme.md
scripts
coverage.sh
coveralls.sh
install.sh
test.sh
truffle.js
Any help / suggestions / learning resources would be appreciated.
Thanks for your time,
Elias
Your error is not because of ipfs. You are running dev mode but error saying that you don't have any scripts dev.If you are deploying smart contracts then you don't need ipfs demon. check package.json
"scripts": {
"dev": "command to run service"
}
Your package.json don't have dev scripts recheck package.json
Quick explanation: I have a staging and a production server, both with the same deployment script (the only difference is the repo branch the clone). The deployment script runs bower install which is globally installed on both servers.
To install it globally I changed npm config set prefix to /home/forge/.npm-packages and afterwards ran npm install -g bower (note sudo wasn't needed, that's the point of changing the prefix). Once again, this was done in both servers.
When I ssh into each server, and run bower -v, which bower it is clear the command DO exist, and it IS added to PATH env. It is the same output for both servers.
Manually running bower install on the project root works for both server.
The issue is the forge deployment script, which only fails on production (IKR? I don't know what was I expecting).
The actual output is:
/home/forge/.forge/provision-2394191.sh: line 8: bower: command not found
The interesting part is, in my attempt to debug, I manually ran provision-2394191.sh and it worked.
What is wrong with my production server?
Seems like adding the new /home/forge/.npm-packages to the $PATH using export was not enough. To solve this I had to manually add it to the /etc/environment file.