{ Re-post from my Medium Post }
My project has pivoted from a standalone android app to a Web page that will generate a custom app for an event organizer’s use.
Read up here on what my project actually is.
So obviously some changes at the server are to be made to make this possible.
How are you planning to do it?
First of we started by providing a Web page that the organizers can use to submit information about the app they need to be built like the App’s name, the link to the API (for fetching the json files) and their email address (for mailing them the apk once it’s generated).
The HTML file for the same can be found here.
Some changes to the Travis build should also be made so that it can use this data for building.
From there on, the details submitted by them will be converted by a json object (using javascript) and further send to the open event server via a POST request where it will be written to a database.
We will be able to fetch this file from the database by the following link
openevent.com/api/v2/customapps/id.
Simultaneously one Travis build will also be trigger using the API that will auto build the latest commit, taking the modified json file data provided by the orga-server.
This configuration will be provided to Travis while the build time.
Cool, any difficulties yet!
One of the main challenges that we are facing is manually triggering the Travis build.
We can do this via the Travis API but that’s still in beta and also we are getting our head around on how to implement it.
I also had a tough time learning javascript and HTML for making the Web page and then I also have to read up on sending a POST request to the server via Ajax.
It’s a bit tough, but should be fun.
So, that was all for now, see you next week and all the best for your projects.✌