Hi Tanmay, Is there an example of enabling the API endpoints when building a stand-alone juliabox instance?
Thanks, Michael On Sunday, September 27, 2015 at 9:25:44 PM UTC-4, tanmaykm wrote: > > Hi Miguel, > > Server instances are created per API. Server instances are stateless, and > are reused across API calls and across users. Based on load, an API can > also have more than one server instances. > > Server instances are brought up on a clean Julia container. They do not > have any files from the user's account. So listing the files will show a > folder that is mostly empty. > > While registering an API endpoint, you are required to submit a short > bootstrap code. When a new instance of the API server needs is brought up, > the bootstrap code is executed on a clean Julia container on startup. The > bootstrap code should then pull the remaining code/data to handle API calls. > > It is possible to pull from non public repos or private S3 URLs too, by > embedding the access keys in the bootstrap code. The bootstrap code is > visible only to the publisher (that is you for all of your APIs). We have > thought about having better support for non-public repos and pre-build > docker images with binary code as well in the future. > > Also, JuliaBox does not currently provide any permanent storage for the > APIs. But it is possible to access storage/databases like (e.g. S3, > DynamoDB) over the internet. > > Best, > Tanmay > > On Sunday, September 27, 2015 at 11:44:32 PM UTC+5:30, Miguel Belbut > Gaspar wrote: >> >> Hi, >> >> Thanks for this, it is a very interesting feature. >> >> I think I have the same question as the previous post, which I think >> wasn't addressed by tanmaykm's answer: >> >> Is the server created per-user? If I expose a ls() command, will it list >> my own account home files? >> I tried using require(Juliaset.jl/src/Juliaset.jl) instead of >> Pkg.clone(...) as the API command, after having sync'ed the Juliaset.jl git >> to my Juliabox account, but that doesn't seem to work. >> >> Is that by design, i.e., the APIs must have publicly-available source? >> Or is it just a current limitation and if so, are there any plans to >> allow using non-public repos or source files in some way? >> >> Cheers, >> >> Miguel >> >> On Tuesday, September 15, 2015 at 11:44:55 AM UTC+1, tanmaykm wrote: >>> >>> Hi, >>> >>> yes, that's right. The APIs will let you share useful functionalities as >>> REST APIs to other users. >>> >>> The API published with name "list_it" can be accessed at >>> https://api.juliabox.org/list_it/... >>> The "..." above refer to the exact method being called and the >>> parameters it expects. >>> From anywhere (including from within the JuliaBox container), any >>> mechanism to invoke HTTP can be used. >>> All APIs are accessible to everyone, unless the API implementation >>> imposes some authorization. >>> >>> a couple of examples of JuliaBox APIs can be found at: >>> - https://github.com/tanmaykm/Juliaset.jl >>> - https://github.com/tanmaykm/JuliaWebAPI.jl >>> >>> Best, >>> Tanmay >>> >>>> >>>>
