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
Currently, the recommended way to create resources is by writing the XML and then loading it into the server using the defaults mechanism. This is fine when the server is being run locally, but when the server is run on a remote system (or platform like Heroku), loading XML from the remote filesystem is not viable.
What is needed is a client that reads the XML files and sends them to the server via the REST API. This can crib most of the code from Server defaults mechanism, including the directory structure.
The text was updated successfully, but these errors were encountered:
Reported by rbrewer, Aug 10, 2012
Currently, the recommended way to create resources is by writing the XML and then loading it into the server using the defaults mechanism. This is fine when the server is being run locally, but when the server is run on a remote system (or platform like Heroku), loading XML from the remote filesystem is not viable.
What is needed is a client that reads the XML files and sends them to the server via the REST API. This can crib most of the code from Server defaults mechanism, including the directory structure.
The text was updated successfully, but these errors were encountered: