Here we go, you changed the file locally say the mode from 644 to 775 or something and when you do the git status you will see the file permissions being changed and laid there – I know, it sucks..
Here is the good news, you can tell git not to worry about the file mode changes through
git config core.fileMode false
This should take care of the problem you are having.
I was working some minor Facebook reporting which require setting up a Facebook App and hooking it to existing Business manager and it looks there is no direct instruction that I found so here you go…
First thing first, you would need a developer account from https://developers.facebook.com/ – go and get it, it is free.
Then Go ahead and create a Facebook App there – a minimum you need is a facebook page and thats it.
Then from the dashboard you will get the app_id and secret. This is very important for you to keep it as secret as well. From this, you will get yet another important key called Access Token.
Now you have a Facebook App that you will use it to acquire a lot of information for the business manager you have. You can get lots of User related data, analytics, sales, spending and more..
Now head to https://business.facebook.com/ and select your business manager if you have more than one.
On the left of the menu, you will see Claim Assets and from there select App
You will be asked to insert App Id and it will be a matter of following the instruction after that.
Now you have integrated your app to the existing business manager. Which means, your app now has an access to the data under your business manager through different APIs.
trying to install composer on your server and got something like
Some settings on your machine make Composer unable to work properly.
Make sure that you fix the issues listed below and run this script again:
And specifically for suhosin.executor.include.whitelist = phar?
Then the fix is to modify php.ini on the fly while you are passing the installer
sudo curl -sS https://getcomposer.org/installer | php -d suhosin.executor.include.whitelist=phar
That should take care of modifying the php.ini on the fly without you updating the config and re-bouncing the server.
You might start mongo demon as
but, as you close the terminal this will terminate your session.
So, to start it as a service so that it would continue running
mongod --fork --logpath /path/to/log/file
You can specify the log file as you wish
I got the MongoId not found error on the the application I recently moved to remote server.
The app is working fine locally and the problem appears to happen on the remote one only.
The problem seems obvious, and I checked the mongo version I have locally vs the version I have on the remote – they are different
I have newer version of mongo installed on the remote server. And the doctrine orm handling my mongo objects was also older.
I updated my doctrie orm on composer as
This took care of the problem – at least for now ;)
The major issue you would face is memory. Yeah, the instance comes with small memory allocation and anything memory intensive task might not work there. Your composer install command might not do anything as well.
The major one would be Composer install just hangs and even aborts the process
When you are issuing
It will eat a bit of memory and doing it on the instance might not work as expected.
Here are the methods I used to overcome it.
1. Incremental install
On you composer.json file, you can try to list only one or two packages at a time and issue composer update vendor/package and if your individual packages are small enough you might get away with it. In my case this didn’t work
2. Ship your vendor from your local machine to the instance
yeah, just have all your composer install where you will be comforted by memory in Gigabytes and just zip and ship it to your instance.
On your local machine
tar -cf vendor.tar.gz /path/to/vendor/folder
Once you have the tar or zip of any of your favorite compressed file
scp -i /path/to/your/pem/file vendor.tar.gz ec2-user@ec2-domain-goes-here:/path/on/instance
This is assuming this will transfer your vendor file to instance.
Then log into your instance and just uncompress the file and put it on the root directory of your application.
This would be just the half of the work.
Then you will need to generate the bootstrap cache file
composer run-script post-update-cmd
yeah.. this will take care of creating the cache file of the bootstrap along with other stuffs that you put on your composer.json post-update-cmd part.
Sometimes you might want to give the write access to the app/cache and app/logs folders as well
Log in to aws.amazon.com
Click on EC2 virtual servers in the cloud
From the left menu, under Network and Security, select Key Pairs
Create on by hitting “Create Key Pair”. Mind you, aws will give you only one chance to save the pem file you will be using for logging. So make sure you download and save it.
From your select Elastic Beanstalk and follow the wizard to create an instance per your need.
in the wizard, there is a step you will be asked to use the pem file you downloaded.
Now from the left menu, click on the instances.
And click on the instance on the right pane and you will see another pane with description will be opened on the lower part. On that pane, search for security group and click the link
You will be transferred to the security group associated with that instance. Click on the “in bound” tab and check if SSH is listed there, if not, hit the ‘Edit’ button and add a new rule of SSH with the source of anywhere if you would like to ssh into your box from anywhere or you can specify particular ip address.
log to your instance from terminal as
ssh -i /your/downloaded/pem/file ec2-user@public-domain-goes-here
you will get your public domain on the instance you selected.
If you are using Elastic Beanstalk, it will come with installed apache server for as your webserver. Just restart it
sudo service httpd restart
MySQL shell would be there as well but not the mysql server so install that
sudo yum install -y mysql-server
And restart the demon
sudo service mysqld restart
I have checked if git is installed, if you are using any DCVS, which you should and it is installed already to verify do
Next would be the creation of your public and private keys for secure communication with the other servers.
ssh-agent -t rsa -b 4096 "firstname.lastname@example.org"
The above command will provide you with the public and private key that you would use. The default path for it would be on ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub
If you are using github or bitbucket, you would need the content of the id_rsa.pub for logging to the server without password.
If you are going to use mongo just use the very information on the following links https://docs.mongodb.org/ecosystem/platforms/amazon-ec2/
This will get you started with your aws instance