[feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express

Fri Nov 11 10:55:31 UTC 2016

I think we're all in agreement here. My question was more of a mid/long
term one, not a short term rip and replace. If we were to invest effort
into mongo-express, I'd see both existing in parallel for quite a while.

On 11 November 2016 at 10:52, David Martin <davmarti at redhat.com> wrote:

> > Let's make sure that we are in agreement on the way forward here. I'm
> not sure a knee-jerk rip and replace of Data Browser is the right answer -
> especially if mongo-express is only implemented as an MBaaS Service and is
> not a first class citizen of the Studio.
>
> Yes, agreed on this 100%.
> I think there is much more to gain from improving the robustness of
> databrowser as is than changing to mongo-express.
> But I'd like to get consensus on how to move forward.
>
> I think this should be viewed as a mongo-express POC that shows how easy
> it is for someone to use it themselves in their cloud app. (There's a big
> problem to solve if we want to have it as a supported service i.e. allowing
> a service to talk to a cloud app's db without hardcoding mong creds)
> We shouldn't dismiss the findings from the initial report.
>
>
>
>
> On 11 November 2016 at 10:43, John Frizelle <jfrizell at redhat.com> wrote:
>
>> The conclusion from the document [1] that compared Data Browser with
>> Mongo Express did not seem to indicate that we should replace Data Browser:
>>
>> *Mongo Express is more complete in number of features but lacks of some
>> critical ones like multiple deletions or inline editing. Besides, its user
>> interface is less intuitive than the one from Data Browser.*
>>
>> *If the stability of Data Browser is improved and some key features as
>> complex querying are implemented, Data Browser could be a better
>> alternative for most of the users. There are other features Mongo Express
>> include which are targeted for more advanced users (like multiple database
>> management) which could not be that important.*
>>
>> Let's make sure that we are in agreement on the way forward here. I'm not
>> sure a knee-jerk rip and replace of Data Browser is the right answer -
>> especially if mongo-express is only implemented as an MBaaS Service and is
>> not a first class citizen of the Studio.
>>
>> I think we need to have a call to discuss this and make sure we are in
>> agreement on the path forward.
>>
>> [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe
>> 1N9KyP3Ijjpmvc3GiJNrhmw/edit
>>
>> --
>> John Frizelle
>> Platform Architect, Red Hat Mobile
>> Consulting Engineering
>>
>> mobile: *+353 87 290 1644 <//+353872901644>*
>> twitter:* @johnfriz*
>> skype: *john_frizelle*
>> mail: *jfrizell at redhat.com <jfrizell at redhat.com>*
>>
>>
>>
>>
>> On 11 November 2016 at 10:34, Wei Li <weil at redhat.com> wrote:
>>
>>> It does. But it is using the same approach we are using at the moment
>>> with data browser, and it probably works fine with smaller dataset. It will
>>> not work very well with large dataset like we have in production
>>> environment.
>>>
>>> We are actually going to look at improving data browser start from the
>>> next sprint. But now it looks like we may have a better alternative.
>>> @Conor, do you think this can replace data browser in the studio?
>>>
>>> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill <coneill at redhat.com>
>>> wrote:
>>>
>>>> Great work on this. We've been seeing a lot of requests for Data
>>>> Browser upgrades and this may be a better approach. Does it have bulk
>>>> import/export?
>>>>
>>>> Conor
>>>>
>>>>
>>>> On 10 November 2016 at 16:02, Craig Brookes <cbrookes at redhat.com>
>>>> wrote:
>>>>
>>>>> This is pretty cool. I actually think having the data browser as an
>>>>> MBaaS service makes a lot of sense.
>>>>> For auth it seems you could create a piece of middleware that calls
>>>>> back to the platform to check a cookie or header value, if not there
>>>>> redirect to a login screen and proxy the credentials through to the
>>>>> platform.
>>>>>
>>>>> Craig
>>>>>
>>>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez <
>>>>> emrodrig at redhat.com> wrote:
>>>>>
>>>>>> Hey guys,
>>>>>>
>>>>>> based on consulting's feedback, we've been working to integrate Mongo
>>>>>> Express in RHMAP. The first step was integrate it as a platform service and
>>>>>> here you can find our findings:
>>>>>>
>>>>>> *Description*
>>>>>> Mongo Express Service is a RHMAP service which allows users to manage
>>>>>> their Mongo databases through a robust GUI. This interface includes several
>>>>>> pieces of functionality missing in the current Data Browser such as a
>>>>>> complex query runner or a database and collections statistics.
>>>>>>
>>>>>> Besides, Mongo Express is an ongoing Open Source project so we can
>>>>>> benefit from the community contribution.
>>>>>>
>>>>>> Here you can find a quick demo of Mongo Express working in RHMAP:
>>>>>> https://bluejeans.com/s/zTlgS/
>>>>>>
>>>>>> *Current limitations*
>>>>>> - At the moment only the service's database is accessible
>>>>>> automatically. This means that the Cloud App's databases need to be
>>>>>> manually configured to be managed through this service.
>>>>>>
>>>>>> - This service needs to be public and therefore the database will be
>>>>>> exposed: anybody knowing the url would have access to the data.
>>>>>>
>>>>>> Note: both limitations can be workarounded. Depending on the feedback
>>>>>> from this service we will put more effort on this.
>>>>>>
>>>>>> *Installation and usage*
>>>>>> To use Mongo Express Service in RHMAP follow these steps:
>>>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs >
>>>>>> + Provision MBaaS service > New MBaaS service)
>>>>>> 2. Make the new service public (Details > Make this Service Public to
>>>>>> all Projects and Services)
>>>>>> 3. Upgrade database (Data Browser > Upgrade Database)
>>>>>> 4. Replace code from the test service with the forked Mongo Express
>>>>>> Service fork:
>>>>>>      - clone Mongo Express fork (git at github.com:emilioicai/mon
>>>>>> go-express-service.git)
>>>>>>      - git remote add your services git url (Details > Git Url)
>>>>>>      - git push --force origin master
>>>>>> 5. Deploy (using Node 4 as runtime)
>>>>>> 6. Mongo Express should be available through the Preview section in
>>>>>> the service view
>>>>>>
>>>>>> *Troubleshooting*
>>>>>> Most of the issues arise because of one of these settings:
>>>>>>      - Service is not public
>>>>>>      - Database was not upgraded before deploying
>>>>>>      - Node 0.10 or Node 0.11 was used as runtime instead of Node 4
>>>>>> In case of a problem re-provisioning and making sure those three
>>>>>> settings are properly configured.
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> feedhenry-dev mailing list
>>>>> feedhenry-dev at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk:
>>>> +353-21-2303419
>>>>  | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST
>>>>
>>>
>>>
>>>
>>> --
>>> Wei Li
>>> Red Hat email address: wei.li at redhat.com
>>> Senior Software Engineer
>>>
>>> _______________________________________________
>>> feedhenry-dev mailing list
>>> feedhenry-dev at redhat.com
>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>>
>>>
>>
>
>
> --
> David Martin
> Red Hat Mobile
> Twitter: @irldavem
> IRC: @irldavem (feedhenry, mobile-internal)
>

-- 
Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk:
 +353-21-2303419
 | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20161111/7bd78de2/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 11472 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20161111/7bd78de2/attachment.png>