GibsonPlumbing / SageApi
Gibson Plumbing's legacy ASP.NET Web API that interfaces with Sage100 via BOIs.
GibsonPlumbing / SageApiGetting started
We use ASP.NET Web API, not ASP.NET Core. Make sure you include that in your search queries when you're looking for help. You need visual studio community to run this project. You can download it here. We would like you to make new routes RESTful, but admittedly, we have not been consistent with that in the past - do as I say, not as I do. Please avoid using this for frontend work - we have a different repo for that. In order to run the frontend, you will need to go to the Gibson Plumbing web app github. It gets deployed on the Gibson Plumbing web app website. The API gets deployed to https://proxy.gibsonplumbing.com/sdata/sageapi/sageapi/api.
Please refer to your seniors for information on how deployments are done, since that is above my paygrade. Plus, compartmentalization is good for security, so if one of us is captured by another plumbing company, vital information is not exposed in the event you are tortured. You can't expose company secrets if you don't know them.
Future plans
I hate the antichrist C#/ASP.NET Web API. I would like to replace it
with something else - and I am leaning towards Node.js. I would like to use a
framework like Express.js and Sequeluze to build the API, but work needs to
be done to interface with the Sage100 BOIs. I am thinking we can use an ABI
or ffi to interface with the BOIs from NodeJS, but there are probably better
ways. If you have an idea of what you would like to use, please make yourself
heard - unless you want to use PHP.
Or, we could use TRPC and monorep our frontend and new backend together. Then our frontend could hook right into our backend and there would be no need to double check all of our API types. They would even integrate with eachother which is a great selling point imho.
edge-js Native module node-ffi-napi node.net