This issue is because IGB is looking for apps jars in testappstore ec2 instance instead of the s3 bucket.
This issue can be solved by using RewriteEngine.
Reasons for using RewriteEngine:
1. Using this we don't have to give the absolute path of jars in repository.xml
2. We can hide our S3 bucket name from the users.
3. We don't have to to change any setting while working with the development environment.
[~aloraine]
<IMPORTANT>
Below settings are mandatory, without these settings both IGB and AppStore cant install apps. It is because media folder won't point to S3 bucket.
Add below lines in /etc/apache2/sites-available/default-ssl.conf
RewriteEngine on
RewriteRule "^/media/(.+)" "https://<S3-BUCKET-NAME>.s3.amazonaws.com/media/$1" [R,L]
Added these lines in Appstore Google doc (S3 section)
This issue is because IGB is looking for apps jars in testappstore ec2 instance instead of the s3 bucket.
This issue can be solved by using RewriteEngine.
Reasons for using RewriteEngine:
1. Using this we don't have to give the absolute path of jars in repository.xml
2. We can hide our S3 bucket name from the users.
3. We don't have to to change any setting while working with the development environment.
[~aloraine]
<IMPORTANT>
Below settings are mandatory, without these settings both IGB and AppStore cant install apps. It is because media folder won't point to S3 bucket.
Add below lines in /etc/apache2/sites-available/default-ssl.conf
RewriteEngine on
RewriteRule "^/media/(.+)" "https://<S3-BUCKET-NAME>.s3.amazonaws.com/media/$1" [R,L]
Added these lines in Appstore Google doc (S3 section)