Open sanand0 opened 3 years ago
@bhatsandeep Let's discuss this on Wed 13 Jan and take a call. But could you please share any thoughts on this?
@Anand S s.anand@gramener.com right no I do not have any preference for data storage, so JSON works. However, I'd suggest that the 'reading' part should be done by a Gramex itself and exposed to the external world (other apps) through an REST API. We can discuss details on Wednesday as suggested.
Also, from a licensing scenario perspective, I have one addition, making it four now as below:
Regards Sandeep
On Mon, Jan 11, 2021 at 1:59 PM S Anand notifications@github.com wrote:
@bhatsandeep https://github.com/bhatsandeep Let's discuss this on Wed 13 Jan and take a call. But could you please share any thoughts on this?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gramener/gramex/issues/359#issuecomment-757711948, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQC65A3T6WI44WFVRN6B5M3SZKZIPANCNFSM4V5GZJIA .
Noted @bhatsandeep -- will factor these scenarios in.
Gramex enterprise should allow restricting instances based on a
license.json
. It's a signed JSON file that has this structure: