Is there a list of best practices or a good resource for doing this? Both in general, and language specific?
Here are somethings I'd expect to see in such a resource: - How to handle instantiation of the library (static functions with static API credentials vs new instances of the library with instance variables for API credentials) - How to pass binary files - Using required arguments for required parameters of an API operation vs a hash or dictionary - How to name function calls - How to structure code/classes in relation to the API's design - What good client libraries should return or throw as an exception ... and so on
This made me wonder: How does the world host static marketing sites (or company blogs and docs) that are cost effective, reliable, and secure?
- iCracked (http://www.themuse.com/jobs/icracked/full-stack-backend-developer)
- interstateapp (http://blog.interstateapp.com/post/10699086100/the-fuel-of-interstate-one-year-later)
- Should be easy to secure
- Files should be encrypted at rest
- Relatively easy to install
Bonus:
- Failover and replication for HA
Currently we have an NFS mount on an EBS volume that is encrypted using cryptsetup
What are the best ways to go about doing this without having to worry about people ripping off your code?
I assume answers will fall into some of the following categories:
- compile/obfuscate code (i.e. cpython)
- submit product as a virtual image (like github enterprise)
- just don't care and rely on your bundled licenses
Each has their own up/down sides. Discuss. :)