You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
Hey, I've been evaluating how to add a GUI on top of DocPad, and providing a REST api using VFS and then exposing it to agnostic GUIs seems like a great idea.
It seems that VFS is primarily used by Cloud9 right now to provide the different workspace options. Is there any plans inside Cloud9 to add a VFS REST workspace? So adding a VFS option to this screen where we can specify say the REST URL, and a username and password for authentication.
This would really be nifty, as it would allow us to use Cloud9 to edit live DocPad websites (or rather any vfs rest provider). The issue then becomes, how should committing and pushing changes be done - I'm gathering that would be handled on DocPad's (the provider's) side instead.
The text was updated successfully, but these errors were encountered:
We are planning on exposing the vfs over http using vfs-http-adapter (currently it uses some internal webdav api) for app preview. I'm not sure how much we're planning on making this a supported API with easy auth, but once you have the cookie the web client is using, it shouldn't be hard to make REST requests to the API.
Hey, I've been evaluating how to add a GUI on top of DocPad, and providing a REST api using VFS and then exposing it to agnostic GUIs seems like a great idea.
It seems that VFS is primarily used by Cloud9 right now to provide the different workspace options. Is there any plans inside Cloud9 to add a VFS REST workspace? So adding a VFS option to this screen where we can specify say the REST URL, and a username and password for authentication.
This would really be nifty, as it would allow us to use Cloud9 to edit live DocPad websites (or rather any vfs rest provider). The issue then becomes, how should committing and pushing changes be done - I'm gathering that would be handled on DocPad's (the provider's) side instead.
The text was updated successfully, but these errors were encountered: