I'm trying to deploy a Perfect app to Heroku, but I have only succeeded in getting the Swift compiler to run on Herolu with Perfect's own build pack. However, this build pack uses Swift 2.2 and my app runs on Swift 3.
I have then tried a variety of other build packs, including vapor, neonichu, and the seemingly most popular one: kylef.
But for everyone of them I get the same error message when pushing to Heroku:
Failed to detect set buildpack <url>.git
I feel I have exhausted my options, so this is my final try.
The makefile in your Heroku example project is referencing Ubuntu 14.0.4, the default Heroku app now is 16.0.4 as of May 2017. You need to set the ubuntu stack to cedar-14, and the swift app will deploy fine:
$ heroku stack:set cedar-14 -a example-app
$ git commit -m "update to cedar-14" --allow-empty
$ git push heroku master
I succeed with the error. The project structure didn't work.
Please use this project structure:
https://github.com/taplin/Perfect-Heroku-Buildpack-Example
I was linking this Buildpack at heroku:
https://github.com/PerfectlySoft/Perfect-Heroku-Buildpack
It worked fine for me. All other instructions you can take out of the video:
http://perfect.org/heroku-buildpack-for-perfect-and-swift.html
Related
I trying to acquire this plugins which available with its GitHub directory
https://github.com/jbeuckm/strapi-plugin-import-content
However, the last command:(not workable)
npm run setup --plugins
It prompt me this:
enter image description here
May I know how could i solve it?
I try "npm cache clean --force" but it still not workable
'npm run setup' was available in Strapi 3.x but as far as I know it is no longer available latest by version 4.x - I guess you are using Strapi 4.x.
https://github.com/jbeuckm/strapi-plugin-import-content was updated 4 years ago so I think it was designed for Strapi 3.x.
We have a CD/CI Azure DevOps build pipeline that stop working all of a sudden today. It has been invoked successfully in our pipeline for months on end.
The component that fails is the "npm install" , it fails with the following error in the verbose log:
I google around and some suggested to run: npm cache clear --force prior to npm install.
I tried that but same error persists.
Then I look up earlier in the log and see the following:
I tried to browse to https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node and got the message "Page not found".
I cannot tell if this is related to the root cause why npm fails but it seems to back my assumption that something is not right with "npm install" as of this time of writing (Nov 17, 2020).
Anyone else using Azure DevOps for CD/CI having the same issue?
I look at NPM incident page and see this issue https://status.npmjs.org/incidents/r1tlhscrw3r6 but it should have been fixed.
Recently, a breaking change was made to the default Azure DevOps agent images for the default version of Node.js. It was incremented from 12.x to 14.x.
Breaking changes
Default version of Node.JS on images will be updated
from 12.x to 14.x
Target date
For Windows, Ubuntu images, rollout of this change will
start on 2 November 2020 and will take 3-4 days For MacOS images,
rollout will start on 9 November.
The motivation for the changes
On images, we always install LTS
version of Node.JS by default. On 2020-10-27, Node.JS 14 has become
LTS version. On 2020-11-30, Node.JS 12 will be switched to Maintenance
mode.
Possible impact
If you rely on default Node.JS version and your
project is not compatible to Node.JS 14, it might start to fail
Mitigation ways
Please consider using Node.js Tool Installer task (for Azure DevOps) and
setup-node (for GitHub Actions) to switch back to Node.JS 12.
Switching will take less than a second. Node.JS 12 still will be
available on images along with Node.JS 8, 10.
Based on #Matt's answer, I'll post the fragment of yml you need to fix this:
- task: NodeTool#0
inputs:
versionSpec: '12.x'
For anyone still using the graphical UI rather than YML files, you would add a
"Node.js tool installer" task and configure its version. It would look something like this (where the Version Spec contains the version of node.js you want run):
Also note that it is BEFORE the "npm install" task!!
I have created backend with perfectswift. Now I am trying to deploy that with heroku but I am getting some kind of error while pushing. Help me to solve this issue.
Seems to be an issue related with stack compatibility. You need to downgrade your stack:
heroku stack:set heroku-16 -a Your_App_Name
Stack Version Base Technology
----------------------------------------
Cedar-14 (deprecated) Ubuntu 14.04
Heroku-16 Ubuntu 16.04
Heroku-18 (default) Ubuntu 18.04
If you got that warning, means you'll need to use Cedar-14:
heroku stack:set cedar-14 -a Your_App_Name
List of Heroku's stacks:
https://devcenter.heroku.com/articles/stack
I am not able to do a pod installcommand when I transferred my swift project to another MacBook pro that I have got. I have done a pod disintegrate into my project folder.
Since two days ago I have been trying to do a pod install, but was able to do a pod init. I am prompted with this error msg:
Unable to add source with url 'https://github.com/CocoaPods/Specs.git' named 'master'.
You can try adding it manually in '~/.cocoapods/repos' or via 'pod repo add'.
I have tried the method proposed but I was still not able to install Firebase/Core.
I would like to also know if I should delete away any of the related pod files after I transferred my project to a new terminal?
Side story:
The project was created in an iMac with OS Yosemite. The Macbook Pro I am using now is EI Captain. Does it matter?
Thank you!
Solution:
Hi all,
My issue was due to my wifi connection. Everything works fine after I am in a place with strong wifi.
try pod setup command. That will setup things for you.
after that try pod install
When I try to deploy im getting a:
bash: /srv/books/current/bin/bundle: No such file or directory
When I login on the deploy server doing 'which bundler' results is:
/usr/local/rvm/gems/ruby-2.0.0-p353#books/bin/bundle
Problem when I use the ssh that capistrano uses to deploy and do which then:
ssh root#server 'which bundler'
It throws
which: no bundler in (/usr/local/rvm/gems/ruby-2.0.0-p353/bin:/usr/local/rvm/gems/ruby-2.0.0-p353#global/bin:/usr/local/rvm/rubies/ruby-2.0.0-p353/bin:/usr/local/rvm/bin:/usr/lib/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin)
For more information on why some things in Capistrano don’t work, when they work perfectly in an SSH session, it might be best to read through http://www.capistranorb.com/documentation/faq/why-does-something-work-in-my-ssh-session-but-not-in-capistrano/ and see if you can reproduce the problem after reading through that.
You don't mention which version of Capistrano you are using, but for both 2.x and 3.x there are decent (3rd party and first party) integrations for RVM available)