Developer Guide 13.1

Hi Olivia,

Unless something drastically changed, I don't think that page is worded very well...

I cannot find your words exactly in the link you sent but they do state "...Sugar's cloud service cannot directly access their database's file system but can work with a Certified Sugar Partner to customize their Sugar deployment."

The reality is that Cloud customers cannot access the database directly nor can you access the filesystem of your application, BUT you can have a local copy of your Sugar instance for development purposes and you can package your changes for deployment to your cloud instance via the Module Loader.

To create those packages you can work with a partner, or you can learn how to package and deploy changes yourself.

There are more limitations when working within the extension framework than if you had an OnSite deployment, but that is not a bad thing, in my opinion.

FrancescaS

Hi Olivia,

Unless something drastically changed, I don't think that page is worded very well...

I cannot find your words exactly in the link you sent but they do state "...Sugar's cloud service cannot directly access their database's file system but can work with a Certified Sugar Partner to customize their Sugar deployment."

The reality is that Cloud customers cannot access the database directly nor can you access the filesystem of your application, BUT you can have a local copy of your Sugar instance for development purposes and you can package your changes for deployment to your cloud instance via the Module Loader.

To create those packages you can work with a partner, or you can learn how to package and deploy changes yourself.

There are more limitations when working within the extension framework than if you had an OnSite deployment, but that is not a bad thing, in my opinion.

FrancescaS

 Hi Olivia Forde ,

Francesca Shiekh explained exactly how the process is.

I will update that guide to ensure it clarifies those points going forward.