3 Replies Latest reply on Sep 8, 2016 6:26 AM by Mike_Mitchell

    Container handling vertical solution

    iconomydk

      I am running a vertical solution in a hosting center on VM. I have full access to this setup via Microsoft Remote Desktop. This is a single file solution ( no interface/data structure – no plans of that)

       

      I would like to give the customers the ability to save their receipts and invoices etc. in the solution, and with this comes extra responsibility.

      I am thinking of doing this with containers using external storage.

       

      But what about updates?

      I have a master edition of the solution, where bugs are fixed and new functions are developed. Today when a client gets an upgrade, I close his file on the server, downloads it to my Mac, trashes the file on the server, do my update routine and uploads the new version to the server again ( 5-10 mins. job )

       

      But in the future where a customer could have thousands of container documents, this seems to make this upgrade procedure a no go.

       

      In stead I am thinking of creating a separate file for all the container data (either one per client or one for all clients ), so that I can leave this on the server when doing my update.

       

      Would very much like to hear what others do?

      Are there any best practices?

      One “container file” per client, or one per server (all clients on the server)?

      Security?

      Backup strategy?

       

      Best Regards

      Lars

        • 1. Re: Container handling vertical solution
          Mike_Mitchell

          Lars Heise Korsgaard wrote:

           

          In stead I am thinking of creating a separate file for all the container data (either one per client or one for all clients ), so that I can leave this on the server when doing my update.

           

          This is considered a best practice. Keep the container file simple, and you will rarely if ever have to mess with it.

           

          I don't really think you would need a separate container file for each customer. Just the one should suffice.

          • 2. Re: Container handling vertical solution
            iconomydk

            Thanks Mike

            .... I rarely write questions - you always seem to answer mine :-)

             

            So if I continue this way

             

            I would have one file with at least 3 fields.

            The container

            a serial no. of the solution

            a uuid

            ( the last two for the relation)

             

            I would then go for open storage - with a relative path of the clients serial no.

            ( each client has its own folder )

             

            The file opens hidden with a user whose credentials can only add records (no admin of course)

             

            Does this sound OK ?

            • 3. Re: Container handling vertical solution
              Mike_Mitchell

              I generally like secure storage, but yes, that's how I do it.