There are 91 posts filed in Tech (this is page 3 of 19).
A very quick and dirty way to export key and value pairs from web console of elastic beanstalk environments config page.
While viewing the elastic beanstalk config page containing the variable inputs paste the following into your browser console.
var strs = [], inputs = $('.properties-table input');
$.each(inputs, function(key, input){
if(!((key+1)%2)){
strs.push(inputs[(key-1)].value + ' = ' + inputs[key].value);
}
})
console.log(strs.join("\n"));When you set up an Apache or LAMP Lightsail instance on Amazon Web Services, the default document root is /home/bitnami/htdocs/
If you are migrating to Lightsail already use something other than htdocs as your root folder, for example public_html, then you might want to update this.
Although you could creating a new app on the server to hand it, here is a simpler option which leaves the default folders and setup in place:
In /opt/bitnami/apache2/conf/bitnami/bitnami.conf add your own document root to the end of every location that htdocs is mentioned.
Then
sudo chown -R bitnami:daemon /home/bitnami/htdocs/*sudo chmod -R g+w /home/bitnami/htdocssudo /opt/bitnami/ctlscript.sh restart apache
And you should be good to go.
I’m using Sequal Pro here, but this should work for almost any connection. I’m also going to lock to a single IP for security. You could us ‘%’ for any IP, but I wouldn’t recommend it if you are on a static ip at home of at work.
Log into ssh for the relevant LAMP instance using the browser tool on the Lightsail dashboard.
cat bitnami_application_password to get your application password. Copy it somewhere as you’ll need it shortly.
Run nano /opt/bitnami/mysql/my.cnf
Comment out the line that starts with bind-address. So #bind-address...
Exit and save the file.
For MySQL < 8 – update mysql permissions for root remote access with
/opt/bitnami/mysql/bin/mysql -u root -p -e "grant all privileges on *.* to 'root'@'1.2.3.4' identified by 'PASSWORD' with grant option"
Replace 1.2.3.4 with internet connection IP address. Replace PASSWORD with the password you copied above.
For MySQL 8 we have to create the user first
/opt/bitnami/mysql/bin/mysql -u root -p -e "CREATE USER 'root'@'1.2.3.4' IDENTIFIED BY 'PASSWORD';"
/opt/bitnami/mysql/bin/mysql -u root -p -e "grant all privileges on *.* to 'root'@'1.2.3.4' with grant option";
Restart mysql with sudo /opt/bitnami/ctlscript.sh restart mysql
Copy the IP address of your Lightsail instance. You may want to add a free static IP address, else the IP will change on restart and all this work will need doing again.
In Sequal Pro choose to add a new connection. Select the SSH tab. In both hosts, put the IP of your Lightsail server.
In mysql username put root and in password, put your password from above.
In ssh username put bitnami and in password, put your password from above.
Click to test your connection. All should connect as expected.
You’ll now need to add a database etc. Enjoy.
This is a functioning AndroidManifest.xml for linking via a local url scheme. In this case appname:// with any (*) following path
To test this you have to redirect to it. Chromium at this time does not understand or process app url schemes. So a 302 redirect from a trusted publicly available url is the best method for testing.
Note how the second intent-filter here is still inside the .MainActivity <activity>
Different categories and an additional <data> tag are used.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.appname">
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<application
android:name=".MainApplication"
android:label="@string/app_name"
android:icon="@mipmap/ic_launcher"
android:allowBackup="false"
android:theme="@style/AppTheme">
<activity
android:name=".MainActivity"
android:label="@string/app_name"
android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
android:windowSoftInputMode="adjustResize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<action android:name="android.intent.action.DOWNLOAD_COMPLETE"/>
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter android:label="@string/app_name">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="appname" android:host="*" />
</intent-filter>
</activity>
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
</application>
</manifest>
Yii 1.1 is currently in maintenance mode following Yii 2 being released way back in May 2013.
Support and bug fixes for Yii 1 were only provided until December 31, 2016 and security fixes and PHP 7 compatibility ends December 31, 2020.
That means that right now the only reason updates to Yii 1 are being created and made available are for security issues found in the existing codebase, and from 2021 it’s mothballed completely.
If you’re maintaining a Yii 1 codebase it’s time to start thinking about how to migrate away from Yii completely, or upgrade your codebase to Yii 2.
There is an official guide aimed at supporting the upgrade process, but it is unlikely to get you from Yii 1 to Yii 2 without significant pain and head scratching.
Converting from Yii 1 to Yii 2 is completely unlike developing code for either framework, and you’d want to source a Yii upgrade professional rather than getting an inexperienced developer or team involved with a large or mission critical codebase.
Personally I’ve now upgraded four codebases from Yii 1 to Yii 2. All the upgrades have been different. All follow a similar path, and the repeatable process I’ve created, but each has its own edge cases, bespoke widgets and complexities.
The work takes many days per codebase before testing and perfection can happen, and where an existing development team are involved with ongoing development or support of the Yii 1 system, it’s best handled as a team effort. Acceptance that the process isn’t anywhere close to just flicking a switch or downloading a patch is required from day one.
At this point I’m considering two next steps.
Firstly, if your company has significant budget and is in need of support moving from Yii 1 to Yii 2, I’d be interested in hearing from you. You may want a supportive voice helping your existing developers to make the move. You may also be looking to hand over a Yii 1 codebase and get it back ready for some testing and iteration.
Secondly, I’m considering sharing some or all of the process I’ve created for manually moving a codebase over from Yii 1 to Yii 2, the gotchas, the process and how to update specific things within Yii 1, where it isn’t as simple as a like
Feel free to send me a direct message on Twitter @harrybailey or leave a comment below if you’d like to contact me.