I have been trying to deploy a symfony2 app via capifony but I keep getting an error at assets:install step. Here is the output when I run cap deploy:
--> Updating code base with checkout strategy
--> Creating cache directory...........................✔
--> Creating symlinks for shared directories...........✔
--> Creating symlinks for shared files.................✔
--> Normalizing asset timestamps.......................✔
--> Reinstalling vendors...............................✔
--> Building bootstrap file............................✔
--> Installing bundle's assets.........................✘
*** [deploy:update_code] rolling back
failed: "sh -c 'sudo -p '\\''sudo password: '\\'' sh -c '\\''cd /var/www/example.com/releases/20120919025653 && php app/console assets:install web --env=prod'\\'''" on stage.example.com
It fails while installing bundle's assets. Anyone run into this situation? Can anyone help me?
Add following line to your app/config/deploy.rb to increase the verbosity:
logger.level = Logger::MAX_LEVEL
You should be able to see what went wrong.
I can see you're using sudo. Is it installed? Did you give rights to use it to the user you deploy with?
I know it's months late, but this just caught me out on a new server setup.
The reason was that the date.timezone setting was not set in php.ini and this threw an ErrorException when running php app/console assets:install web --env=prod
Related
I have been using mongo-driver in my project, deploying with gcloud app deploy for a while now. I recently rebuild my machine, and simply ran go get to get fetch ally my dependencies. Everything is compiling fine locally, however, gcloud app deploy fails:
Failed to build app: building app with command '[go build -o /tmp/staging/usr/local/bin/start ***\admin]', env '[PATH=/go/bin:/usr/local/go/bin:/builder/google-cloud-sdk/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=***HOME=/builder/home BUILDER_OUTPUT=/builder/outputs DEBIAN_FRONTEND=noninteractive GOROOT=/usr/local/go/ GOPATH=/go GOPATH=/tmp/staging/srv/gopath]': err=exit status 1, out=srv/gopath/src/go.mongodb.org/mongo-driver/x/mongo/driver/compression_cgo.go:15:2: cannot find package "github.com/DataDog/zstd" in any of:
/tmp/staging/srv/gopath/src/go.mongodb.org/mongo-driver/vendor/github.com/DataDog/zstd (vendor tree)
/usr/local/go/src/github.com/DataDog/zstd (from $GOROOT)
/tmp/staging/srv/gopath/src/github.com/DataDog/zstd (from $GOPATH).
Any ideas? app.yaml is just runtime: go113
Have you tried specifying dependencies with go mod yet?
I faced the same issue and finally can solved by generating go.mod file with these command,
GO111MODULE=on go mod init
GO111MODULE=on go mod tidy
Here is the details explanation.
I have practised Ionic a lot so these Problems are not new for me but I am unabale to solve this one.
I am currently trying to migrate my Ionic3 project to Ionic4.
To do this I have created a new Ionic4 tabs project.
Every time I try the Ionic serve command I am getting:
[ng] An unhandled exception occurred: Unknown browser query
basedir=$(dirname "$(echo "$0" | sed -e 's
Maybe you are using old Browserslist or made typo in query.
[ng] See "C:\Users\Admin\AppData\Local\Temp\ng-9er5Id\angular-errors.log" for further details.
[ERROR] ng has unexpectedly closed (exit code 127).
The Log file:
[error] BrowserslistError: Unknown browser query `basedir=$(dirname "$(echo "$0" | sed -e 's`. Maybe you are using old Browserslist or made typo in query.
at unknownQuery (D:\Wisex\Technik\Client\safehome_client\node_modules\browserslist\index.js:204:10)
at D:\Wisex\Technik\Client\safehome_client\node_modules\browserslist\index.js:296:11
at Array.reduce (<anonymous>)
at resolve (D:\Wisex\Technik\Client\safehome_client\node_modules\browserslist\index.js:237:18)
at browserslist (D:\Wisex\Technik\Client\safehome_client\node_modules\browserslist\index.js:361:16)
at new BuildBrowserFeatures (D:\Wisex\Technik\Client\safehome_client\node_modules\#angular-devkit\build-angular\src\utils\build-browser-features.js:17:35)
at generateWebpackConfig (D:\Wisex\Technik\Client\safehome_client\node_modules\#angular-devkit\build-angular\src\utils\webpack-browser-config.js:24:34)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
Does anyone of you have an possible solution for this.
I am really greatful for help cause I takes my days to migrate by now.
Yours,
Benjamin
Do you have the last version of the angular cli?
npm install -g #angular/cli
It might also be useful to post the log
I have spent several hours to fix this .Hope it will help someone
Kindly follow the below steps:
find your npm path from the environmental variable. And copy that path and paste it in notepad
2.Go to control panel ->uninstall the node js
3.after uninstalling,restart the system.
4.Now go to npm path in file explorer.
5.And delete the folder named npm and npm-cache
6.And now install the node(LTS version) and angular(refer from the below link for step by step installation)
https://www.zeolearn.com/magazine/setup-angular-windows
note:Dont run the cmd as administrator.Unless ,the installation fails
7.Once you verified that angular is running fine using ng serve -o
8.Install the ionic by npm install -g ionic#latest
9.And run ionic serve.
10.Hope it helps.Happy coding :)
How to run .AppImage on ubuntu 17.10?
I did cura-build from the following exec (AppRun and Appimagetool) files from https://github.com/AppImage/AppImageKit/releases
~cura-build/build$ make
Copying AppRun executable...
...
...
...
...
...
Embedding ELF...
Marking the AppImage as executable...
Success
Please consider submitting your AppImage to AppImageHub, the crowd-sourced
central directory of available AppImages, by opening a pull request
at https://github.com/AppImage/appimage.github.io
[ 98%] Built target packaging
Scanning dependencies of target signing
[100%] Signing Package...
Generating signature...
Generating SHA-1 sum...
[100%] Built target signing
After generated package I got an .Appimage file, then I try to run this file,
~: chmod a+x Cura-0.0.0-master.AppImage
~: ./Cura-0.0.0-master.AppImage
execv error: No such file or directory
I checked with these file properties as 'Allow executing file as program'
How to resolve this?
Please download a readymade AppImage from https://ultimaker.com/en/products/ultimaker-cura-software and report issues at https://github.com/Ultimaker/Cura/issues, thanks.
for RUN
in linux(ubuntu)
chmod +x Name.AppImage
./Name.AppImage
I am quiet new to rabbitmq and currently trying to install Postgres listen exchange plugin at:
https://github.com/aweber/pgsql-listen-exchange
I tried following the instructions listed there but i am getting following errors:
/bin/sh: escript: command not found
make[1]: *** [deps.mk] Error 127
make: *** [../rabbitmq-server/dist/.done.0.0.0] Error 2
I am currently working on Mac, not sure if it is because of i missing some essential libraries.
If you want just install the plugin you have to:
Download the package here https://github.com/aweber/pgsql-listen-exchange/releases and exactly this https://github.com/aweber/pgsql-listen-exchange/releases/download/0.3.0-v3.5.x/pgsql-listen-exchange-0.3.0-v3.5.x.zip
Extract the zip and copy the files into the rabbitmq plug-in directory, usually this : rabbitmq_server-3.5.4/plugins
After that execute sudo ./rabbitmq-plugins enable pgsql_listen_exchange, and as result you should have:
The following plugins have been enabled:
epgsql
pgsql_listen_exchange
you are trying to rebuild the package, but if you want just use it, you don't need to rebuild it.
hope it helps
I recently update my QtSdk to 1.2 and after that, I am unable to deploy a debian file of more then 6 mb. It gives me the following error:
16:32:02: Preparing SFTP connection...
16:32:02: Starting upload...
16:32:03: Failed to upload package: Failure
16:32:03: Deploy step failed.
Error while building project Animal101SymbianMeegov1 (target: Harmattan)
When executing build step 'Deploy Debian package via SFTP upload'
Has anyone run across this problem?
The workaround I use to deploy is to create a link in /tmp/.deb pointing to /var/tmp/.deb and the run the deploy step in QtCreator.