Re: Demo server required for future development in mobile
I don't think it matters if other projects have done it. If it's right
for the project, JFDI.
First, just ask Infra if they can provide what you need.
Second, if you need help making it happen, we can look at the targeted
sponsorship program as one avenue. See
Either way, if you get a box/credits/whatever, you'll likely want to put
together a team to administer said box. On the SpamAssassin project, we
have a group called the SpamAssassin SysAdmins group just for that purpose.
Food for thought,
On 9/15/2018 6:29 PM, James Dailey wrote:
> hi Maurya - I think this is a good point to raise and thank you for raising
> it on list.
> As I understand it, you want to have a demo server so that you can write a
> front end application against the back end APIs of Fineract-CN.
> First, I think you'll already know that this was the approach that the
> community at Mifos took with MifosX, which migrated to fineract1.x .
> As context, the strategy there was to have a demo server against which
> anyone could write a front end and test their dev against a "dev sandbox"
> for the backend.
> This worked well.
> Now, for fineract-CN, the basic difference as I understand it, is that
> instead of a single possible API, there could a set of APIs based on which
> microservices are included in the instance. It may still be sensible to
> have a demo server set up by *SOMEONE* (i.e. some outside group), or it may
> make sense for fineract.apache.org to have a demo server.
> I tried to find on the apache.org site any other project that has a similar
> demo backend server. I haven't found one. If someone knows of one, that is
> hosted by apache, rather than an outside group, please do point it out.
> What I found was that generally speaking, documentation about APIs are
> provided but that run time instances are not. For example, you can see the
> apidocs of twill. http://twill.apache.org/apidocs/index.html
> Setting aside the issue of choosing which microservices to run and how to
> keep the API versioning straight (something that is still under discussion
> on this liserv),
> , I think we need to figure out if this is something that fineract
> community *should* do as part of the project, or if we want the broader
> user-base should be asked / encouraged to do this. There may not be a
> single cannonical API document, which to me points to some strong
> divergence from the current fineract1.x approach, and therefore that this
> should be done outside of the project.
> @jimjag Jim Jagielski (The Apache-experienced one)
> This seems like a decision where your input would be much valued!
> - James
> On Sat, Sep 15, 2018 at 1:57 PM Rajan Maurya <rajanmaurya154@xxxxxxxxx>
>> Hi folks,
>> We really need fineract-cn demo server up and running for mobile
>> future development, without fineract-cn web-client and live demo server I
>> can't predict. what would be next feature and APIs I need to use for future
>> I don't think so If would take time to you.
>> Thanks in advance, please....... 🙂
>> Rajan Maurya
>> Contact Number : +91 9015090523 <+91%2090150%2090523>
>> Github : @Github/therajanmaurya <https://github.com/therajanmaurya>,
>> LinkedIn: @LinkedIn/therajanmaurya
>> Medium: @medium/therajanmaurya <https://medium.com/@therajanmaurya>
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171