We tagged the 4.5.0 release yesterday. What's significant about this release is the improved JSON REST APIs for essential operations such as signup, authentication, password recovery, Actor profile settings, and Site Settings.

As you know, Anahita has been moving towards a Client-Server architecture. We are developing a client-side React application for Anahita. We are already using stable variations of this app in public and private platforms that we have implemented for our clients. We are also developing an open-source version of the Anahita React app for our community.

How to upgrade

If you are using the code in the master branch, do a git pull to obtain the latest code. If you are using a stable version of the Anahita, go straight to typing the following commands in the root of your Anahita installations: 

$ composer update

$ php anahita site:configuration

Then using vim or an editor of your choice, edit the configuration.php file in the www directory, and set:

var $client_domain = "https://www.yourappsdomain.com";

Now save and quit the editor.

To be sure, run the database migration command just in case if there are any migrations left in your upgrade that you need to run:

$ php anahita db:migrate:up

Now test your Anahita installation and make sure if everything is working.

Need Support

If you had difficulty upgrading or had any questions, please start a topic on our support group:  https://www.getanahita.com/groups/107732-tribe-support

We also offer paid support through our company, and you can contact us here: https://www.rmdstudio.com/contact 

Want to help?

Follow the Anahita Project group to help us out or work on your own Anahita project alongside: https://www.getanahita.com/groups/42242-anahita-project

Next release's focus

One of the most fundamental changes in Anahita architecture will be happening in the 4.6.0 release we will:

1. Finish implementing version 1.0.0 of the Anahita React app and start using it for our live site.

2. Reduce the Anahita PHP codebase into an application that provides RESTful APIs only. We will accomplish that by removing the following components and libraries:

• All the components' HTML views
• Language package manager and language support because localization is now happening on the client-side.
• All the UI libraries
• All the content plugins because their functionality is now happening on the client-side.
• The Pages component, because a similar Component in the Anahita React will provide static content pages.
• Ideally, use JSON as the default output rather than HTML.
• Provide Markdown Support rather than HTML in the editors where formatted text is desirable. 

Those are significant changes in one release, but at this point, we would like to implement new features in Anahita or improve some of the existing ones, such as the user onboarding workflow. The current legacy HTML views are getting in our way, and it is time to move on to the new Architecture. We expect that the Anahita 4.6.0 will be smaller, less complex, and faster than the previous releases. This code reduction is going to be so much fun!

Photo by Nidhi Shah from Pexels https://www.pexels.com/photo/blue-jellyfish-in-water-3616252/

#Anahita #BirthRelease #REST #API #Announcement

We have just tagged the 4.4.4 Birth release. This version comes with improved REST API for Site Settings and Actor Settings. We have also fixed several bugs.

We have been busy working on the Anahita React app and, through this process, improving the REST APIs in Anahita. 

How to upgrade

If your installation is from the master branch:

$ git pull

$ php anahita db:migrate:up

else, if your installation is from the latest stable release:

$ composer update

$ php anahita db:migrate:up

If you have any issues through the upgrade, please start a topic in the Tribe Support group so we can help you out: https://www.getanahita.com/groups/107732-tribe-support

#Anahita #BirthRelease 

This update contains some critical security updates, so we advise you to update your Anahita installations. We have also improved the overall security of the Anahita domain entities. 

For those of you who have custom Anahita apps on your system, you may need to update them. Here are the changes that you need to make:

What's new

We are now supporting Amazon S3 Regions. When you upgrade your installation, go to Settings > Plugins > Storage Amazon S3 and select the Region for your AWS S3 bucket.

We are also using 2 Google API keys for Geolocation and Google Maps APIs. That is because Anahita does geolocation on the server-side while the maps pass the key on the client-side. You can technically reuse the same key for both services, but you may want to use two different keys with different constraints. Go to Settings > Apps > Locations and update the keys. 

How to update

Go to the root of your Anahita installation and run the following commands:

$ composer update

$ php anahita db:migrate:up

If you are using Amazon S3 for your images, your images will show as broken. Go to the Storage Amazon S3 plugin configuration and select the region for your S3 bucket. That will fix the broken image links. 

You also need to use two Google API keys for the Geolocations and maps. Go to the Locations app configuration and update the keys. 

If you have any issues through the upgrade, please start a topic in the Tribe Support group so we can help you out: https://www.getanahita.com/groups/107732-tribe-support

#Anahita #BirthRelease