On Monday, June 20, 2016 at 12:24:46 PM UTC-7, Dominic Mayers wrote: > > Anthony, I am going to reply to one specific part of your last post, the > one with "I don't think the concept of wrapper application is well > defined.": > > I don't think the concept of "wrapper application" is well defined. In any > case, we should probably drop that idea, as your ultimate goal is not to > have a "wrapper application" but instead to have some configuration data > made available to your application -- so let's focus on that. > > I should not be here to defend the usefulness of a wrapper application or > even rigorously define it. I believe that the notion of a wrapper is > sufficiently general that I should not need to define it. >
Dominic, I'm trying to avoid thinking that you're focused on a specific type of solution, rather than looking at what Anthony is suggesting as a range of solutions. But perhaps it is the the problem space you aren't describing well. I get the impression is that you plan on writing one application for use by many customers, and that this application will be installed in many environments. Your customers will do the installation and administration of the application *in their environment*, which includes installing updates that you provide. The customers may also be doing OS upgrades without coordinating with you. Is my understanding of the problem space correct? In the one example I have of a major upgrade to one of my systems, there was no problem ... this was W7 upgraded to W10, and the web2py deployment is a development environment. The web2py code, and my application, lives in my user directory, and was unaltered by the upgrade. The way I handle releases of web2py (most recently, 2.14.6) is to give each version its own subdirectory in the same "top of the tree" directory, and then to copy my application across. I compare the examples apps between the versions to see what new features I can take advantage of. On my linux installations, I use a similar process to upgrade web2py. The linux systems have been updated but not upgraded, but the web2py code lives in my /home directory (/home/me for the development versions, and /home/webuser for the production environment) so I don't anticipate that being a problem when I do a reinstall. My environment so far has included Fedora (as far back as 16) and Centos (6 and 7), and current AWS. Note that I help run a server that supplies subversion (svn) source control services, and also runs the trac project software (GUI for svn, ticket system, milestone tracking), and a buildbot installation. These each run webservices (not through web2py, they have their own servers; buildbot is on top of twistd). They each use conf files, and the location of the conf files is specified by the application, and the administrator makes sure that the local information is in the right place. On occasion a new release of these applications will, indeed, overwrite the conf files, but replacing them with an archived copy is not difficult for the system administrator. These apps use /var/lib for the home of their code. The OS for this server has been rather stable, so I haven't seen what an upgrade does. As to how you could do a wrapper application in web2py, my first thought is ... just another web2py application, that redirects to the main application, is certainly a possibility. This app could be configured for the local environment, and append that information onto the URL being sent to the main application. This would allow the main application to be updated without having to redo the local settings, and it's as independent of OS upgrades as web2py itself is. Web2py has a way of packing an application (it's a zip file wrapped in a .w2p file) that allows you to quickly to install an application without having to use a separate installer program (the admin controller can import these files). I hope this helps. Dave /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
