Parse to Coronium.io migration - AWESOME :-) ! Just few minor API issues

Third Party Coronium
#1

Dear Develephant,

To start with - Coronium.io is AWESOME. We had few Corona apps which were using Parse.com backend.  Due to Parse decision to close within a year, we started looking at various alternatives. Coronium.io worked perfectly and smoothly till now - we have migrated a lot of our APIs from Parse.com to Coronium.io. It is extremely easy (migration work is still going on but we are very comfortable that Coronium.io will work for us). Thank you from bottom of my heart - I sincerely appreciate the great work that you have put in.  And dashboard and performance is very good.

We have tried a lot of the APIs and they are working great. Few minor issues we are having (Note: we are using it on AWS cloud):

1) coronium:uploadFile() is not working when “destDir” is given in filemetatable. The directory is already created on coronium server under “/home/coronium/files”. It is working if destDir is not there.

  1. coronium:registerUser() is creating the user successfully. But not returning the newly created user’s objectId in the result. Because of that, we are not able to extract more information using coronium:getUser() call. Though I am able to get it working by using a cloud API (coronium.user.getUsers), but its an extra API call. Is it possible to return objectId in registerUser() itself.  

  2. When I try to change admin password to something else using the dashboard, it says “Oops an error has occurred”.

Regards,

Samir Jain

#2

Hi Samir,

My apologies for the issues. I will take a look.

Are you running the 1.93 AWS image?

Cheers.

#3

Yes - the default image that is launched from coronium.io site - when you click on EC2 instance.

#4

Hi Develephant,

Any update on the above three issues - specifically issue 3 - as we are unable to change the password for admin user.

Regards,

Samir

#5

Hi Samir,

Been a lot going on. I updated the AWS stack last week (1.93.1), is that the one you are using?

I will double check the issues today, promise.

Cheers. 

#6

I though that too but it will allow you to change it if you change ‘admin’ to something else, it shows admin and coroniumserver but they are place holders you still have to type something in all fields. It just looks confusing because it has the default settings for the placeholders.

#7

I tried changing username from admin to something else. But still the same issue.

#8

Hi,

I think I’ve pin-pointed issue #1, so making some adjustments to the EC2 image to address that, which appears to be permission related. Amazons Ubuntu image is configured slightly different, so it causes all sorts of issues for building Coronium base images.

The admin update (#3) still not working is kind of baffling, as it worked when I tested it yesterday. For reference, User names are limited to 255 bytes and may not include the character :

Though, there is a possibility that the permission issue is hosing the admin update as well.

#2 Is being added. Makes perfect sense.

Also, what version number does your dashboard show (in bottom left)?

Cheers.

#9

I am using 1.93 version.  I ran following command using SSH:   sudo coronium-tools update  (it shows no update available)

For issue#3) I have tried different usernames such as “admin”,   “bgadmin”, “bg” etc - it is giving the same error  i.e.

“:slight_smile: Oops an error has occured”

Thanks

#10

For issue#3: Is there any way I can change the admin password in some other way like using command line script using SSH? As we are trying to go live, I need to change the password :slight_smile:

#11

Please ignore issue#3. I have recreated another EC2 instance with 1.93.1 build and it is working. Thanks

#12

Hi Samir,

My apologies for the issues. I will take a look.

Are you running the 1.93 AWS image?

Cheers.

#13

Yes - the default image that is launched from coronium.io site - when you click on EC2 instance.

#14

Hi Develephant,

Any update on the above three issues - specifically issue 3 - as we are unable to change the password for admin user.

Regards,

Samir

#15

Hi Samir,

Been a lot going on. I updated the AWS stack last week (1.93.1), is that the one you are using?

I will double check the issues today, promise.

Cheers. 

#16

I though that too but it will allow you to change it if you change ‘admin’ to something else, it shows admin and coroniumserver but they are place holders you still have to type something in all fields. It just looks confusing because it has the default settings for the placeholders.

#17

I tried changing username from admin to something else. But still the same issue.

#18

Hi,

I think I’ve pin-pointed issue #1, so making some adjustments to the EC2 image to address that, which appears to be permission related. Amazons Ubuntu image is configured slightly different, so it causes all sorts of issues for building Coronium base images.

The admin update (#3) still not working is kind of baffling, as it worked when I tested it yesterday. For reference, User names are limited to 255 bytes and may not include the character :

Though, there is a possibility that the permission issue is hosing the admin update as well.

#2 Is being added. Makes perfect sense.

Also, what version number does your dashboard show (in bottom left)?

Cheers.

#19

I am using 1.93 version.  I ran following command using SSH:   sudo coronium-tools update  (it shows no update available)

For issue#3) I have tried different usernames such as “admin”,   “bgadmin”, “bg” etc - it is giving the same error  i.e.

“:slight_smile: Oops an error has occured”

Thanks

#20

For issue#3: Is there any way I can change the admin password in some other way like using command line script using SSH? As we are trying to go live, I need to change the password :slight_smile: