-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the open-xamoom wiki!
If you are looking for information about howto develop stuff on the commercial xamoom CMS please go to xamoom.github.io.
open xamoom consists of an open source Google AppEngine API backend, which you cna deploy to Google AppEngine and use as the backend for the Wordpress plugin and Apps included in this repository. The backend included here uses simple CSV files to manage spots, markers, content and all other informations. It is designed to be used on any CMS you would to use to manage your content, spots and the relations by them. It is also designed to be multilingual.
All files of the backend are found in the AppEngineApp folder.
- Just setup a Google AppEngine Project following the instructions by Google.
- Enter your app Id to app.yaml (replace <YOUR-APP-ID>).
- Change the the base_url path in config.py to match your app Id (replace <YOUR-APP-ID>).
- Deploy that to Google AppEngine following the instructions by Google.
All files of the backend are found in the WordpressPlugin folder.
- Change the the api_endpoint path in includes/class-xamoom.php to match your app Id (replace <YOUR-APP-ID>).
- Deploy to a Wordpress installation of your choice.
- In
XamoomEndUserApi.java
insert your URL atprivate static final String apiUrl = "your-url-here";
- In pingeb.org
secret.xml
insert your APIKey - In pingeb.org
Global.java
update the aboutPage contentID - In pingeb.org
XamoomPingeborgApp.java
insert your beacon major
- In
XMMEnduserApi.m
insert your URL atNSString * const kApiBaseURLString = @"https://your-url-here/";
- Update your API-Key in pingeb.org
AppDelegate.m
at[[XMMEnduserApi sharedInstance] setApiKey:@"your-api-key-here"];
- Update the aboutPage contentID in pingeb.org
Globals.m
atglobals.aboutPageId = @"1";
The integration API can be used to develop integrations into any CMS or website. If you want to develop your own integrations just follow this guide.
This version is using plain CSV files to store and manage data, so you might want to change this and make it work on your CMS of choice. Todo this you just have to replace the CSVDataProvider.py by an data provider for your CMS. Just keep the method names, return values and paramters and develop your data access that works like this on whatever CMS you want.