I installed the Parse Cloud Code Command Line Tools last August, and was able to update my Cloud Code regularly using "parse deploy" from the Mac OS X Terminal command line.
I am as of today on the latest Parse CLI version 3.0.1
Now today, when I try to add another Parse function to the main.js file in the "cloud" directory, and save the file, and then to a "parse deploy" I get the message "Not creating a release because no files have changed"
Indeed, the Cloud Code on the Parse.com website has not been updated.
What is my problem here?
Answering my own question... "parse deploy" did not work anymore... so I tried "parse develop", and this successfully uploaded the new JavaScript up to Cloud Code. Thereafter, "parse deploy" worked.
Related
I'm trying to deploy laravel app to aws beanstalk, OS is Amazon Linux 2 AMI.
I've setup following files:
.ebextensions/01-deploy-script-permission.config
It contains below code:
container_commands:
01-storage-link:
command: 'sudo chmod +x .platform/hooks/postdeploy/post-deploy.sh'
And
.platform\hooks\postdeploy/01-post-deploy.sh
It contains below code:
php artisan optimize:clear
Upon deploying it fails with following entry in eb-engine.log file
[ERROR] An error occurred during execution of command [app-deploy] -
[RunAppDeployPostDeployHooks]. Stop running the command. Error:
Command .platform/hooks/postdeploy/post-deploy.sh failed with error
fork/exec .platform/hooks/postdeploy/post-deploy.sh: no such file or
directory
This answer is for users who are using Windows to deploy their files to elastic beanstalk.
I found this information after spending 6 precious hours. Probably not documented anywhere in official documentations
As per this link "https://forums.aws.amazon.com/thread.jspa?threadID=321653"
psss: most important that the file is saved with LF line separator.
CRLF makes "no file or directory found"
So I used Visual Studio Code to convert CRLF to LF for files in .platform/hooks/postdeploy
At the bottom right of the screen in VS Code there is a little button
that says “LF” or “CRLF”: Click that button and change it to your
preference.
I don't know for sure but I think you are running the command before the files are even created hence getting the following error.
A while ago I faced the same kind of problem where I wrote migration commands in .ebextension and it used to give me an error because my env file wasn't even created yet hence no DB connection is made so I was getting the error. Hope this will give you a direction.
By the way, I resolved the problem by creating env then pushing these commands through the pipeline.
While installing the hybris, my localextension.xml is creating in comment form. I am very new in hybris ecommerce development.
So I have followed below steps for installing the hyrbis -
Installed the zip version of Hybris 6.6
Unzip it
From Platform folder, I opened the terminal and ran ". ./setantenv.sh" And after that I ran "ant clean all" and after the build completed succesfully all folders got created in Hybris folder.
Then I ran "./hybrisserver.sh" and my server got started successfully.
Then I ran "https://localhost:9002/" over that I initialize and it also went successfully.
When I try to access hmc or backoffice it is giving me 404 page not found error.
I checked my localextension.xml file and found all the extensions generated as a comment as shown below.
Could anyone help me out where I am doing the mistake.
Thanks in advance.
If you are using original package you need to install a receipt. Go to install folder.
Run below command for listing existing receipt
./install.sh -l
Prepare b2c with acc:
./install.sh -r b2c_acc
Initialize b2c with acc (Also you can use ant clean all for this step):
./install.sh -r b2c_acc initialize
Start hybris (Also you can use ./hybrisserver.sh start for this step):
./install.sh -r b2c_acc start
When you do "ant all" for the first time and set-up the config folder, it generates a localextensions.xml file which contains extensions that are commented out. If you initialize and start Hybris using this setting, you get nothing, except the HAC.
To enable HMC, you need to at least have "platformhmc" extension enabled (i.e. not commented out) in localextensions. So, stop Hybris, uncomment platformhmc, and do another build (i.e. "ant all"). After that, you can do a Platform Update, or a Platform Initialize (to build from scratch again). When it's done, and you've started Hybris, HMC should be accessible.
Or, if you want more features enabled by default, you can do #mkysoft's suggestion and use recipes.
I have Bitnami's Parse Server set up on Azure.
I'm logging some info from cloud code using console.log and console.error. When using hosted Parse these logs were displayed in the Info & Error Logs section on the Dashboard. Any idea where the logs go to now?
The issue is not specific to Bitnami's distribution. I also tested on a local machine with parse-server-example & Parse Dashboard and got the same result (no logs).
I use AWS but you can see the logs by downloading them or running it on localhost just cd into your folder then do Npm start on terminal and switch you parse server URL to http://localhost:1337/parse.
You can manually download them through the azure cli
Take a look here for installation : https://azure.microsoft.com/en-us/documentation/articles/xplat-cli-install/
I used npm : npm install azure-cli -g
open up terminal and type in : azure site log download webappname
This will save the logs for the web app named 'webappname' to a file named diagnostics.zip in the current directory.
Unzip and open the folder diagnostics -> LogFiles -> Application
The text file with -stderr- in the name of it will display the logs you display by using console.error() in your cloud code.
The text file with -stdout- in the name of it will display the logs you display by using console.log() in your cloud code.
This is a known issue on Bitnami Parse. We are working on fixing it for the next release.
You have to log in your server via SSH and modify the line below at the /opt/bitnami/apps/parse/htdocs/server.js file:
From:
cloud: "./node_modules/parse-server/lib/cloud-code/Parse.Cloud.js",
To:
cloud: "./cloud/main.js",
You have to include the path to the ./cloud/main.js you previously created (assuming you created it in /opt/bitnami/apps/parse/htdocs/).
Remember to restart the Server after applying those changes running:
sudo /opt/bitnami/ctlscript.sh restart
In summary of integration I see a link to ipa file
Environment: xcode7, mac os server 5.0.4
I can't find ipa file after success integration in post integration script.
Log from post build script:
submit Crashlytics: Crashlytics.framework/submit 1.3.5 (15)
submit Crashlytics: No file found at path /Library/Developer/XcodeServer/Integrations/Integration-54550b26ed9ba94f644c10b0691a1634/CIT.ipa
I try used the env var, like this -ipaPath "${XCS_OUTPUT_DIR}/${XCS_PRODUCT}" and got the next error
submit Crashlytics: Crashlytics.framework/submit 1.3.5 (15)
submit Crashlytics: Path must be to an .ipa file. To create an .ipa distribute an archive (ad-hoc) using Xcode.
Try this
"${XCS_OUTPUT_DIR}/ExportedProduct/Apps/${XCS_BOT_NAME}.ipa"
It's the only thing working for me.
According to this wwdc 2015 presentation, XCS_PRODUCT should produce:
Path to an .ipa or .app, if the bot produced one
But it's not working right now...
In the latest Xcode Server 5.1 version just use
"${XCS_PRODUCT}"
In Mac Server 5.2 + XCode 8.2, you have to use
"${XCS_PRODUCT}"
The path is temporary path. It will get deleted once integration complete which means finish the last post-script. So you won't be able to find anything in that path after bot completion.
I have scripts set up to run as post- and pre-actions in my Xcode project's scheme. printf and puts in Ruby don't seem to print to the logs that show up on the Xcode continuous integration website's "Logs" tab. How can I print to this log file? Also, is there a way to find out where the log file is located?
Please forgive my naivety: I know very little about how OS X Server works. The Xcode CI web interface is the only place I can see the log file:
Note, this is a cross-post from: https://devforums.apple.com/message/908997#908997
Yes, writing to /tmp is what worked for me, here is an exerpt from one of my scripts:
exec > /tmp/testflight.log 2>&1
echo "uploading to testflight"
On the server running the xcode bot, your file should be there in /tmp as specified. I did not receive the permissions errors so maybe this will work for you.