On 7/7/14, 12:53 PM, Sytze de Boer wrote:
Over time, I have developed specific applications which are used to record
and monitor financial information for AID projects.
These aid projects are usually financed by the World Bank and the National
Government, such as Afghanistan and Papua New Guinea
I completed one such program for Afghanistan in 2006. This project was
extended in 2012 and the software was updated at that time.
In other words, it is a well established, bug free system.
It is a simple multi-user system. A dozen or so free standing dbf files.
About the only complexity is the reporting system where the reports are
very specific to both the National Government and strict WB standards.
I think you should split up the project into multiple roles. The web
front-end person need now know anything about SSL or databases, for example:
Now they have a a new IT manager and he has asked me to price an alteration
to the software.
He has asked for
1. Web based access based on web 2.0
Subcontract a UI person. Must know at recent CSS, HTML and at least how
to work with a JS framework such as node.js or jquery. Need not be too
artistic, but must know how to make a modern site using modern standards
of layout.
2. Central database system (SQL, MySQL, or Oracle backend systems).
Subcontract a DBA. I suggest PostgreSQL or MariaDB to stay in the SQL
world, or Cassandra to scale for handling lots of concurrent rights and
excellent read performance.
3. The software should have a user tracking system that each user
logs in all the activities should be logged.
This would be the business-layer person, presumably you.
4. Backup system inside the software to backup the database no the
whole software.
Same as 3.
5. The software should support email services to send and receive
emails automatically
Subcontract this out to one of the many emailing services that exist
now, like Mailgun.
6. The software should support SSL Certificates to secure end users
data access.
With the data centralized, the web server would access it, ideally from
hardware on the same rack, so SSL probably isn't required for the
traffic to and from the web server, but it's pretty standard in
databases these days so once you have a cert, it would work but adds
some overhead.
For end-user to the web server via the browser, you'll need a different
SSL certificate tied to the host name or names. I think the common
practice these days is if SSL is needed in some parts of the site, use
it everywhere to avoid unintentionally leaking stuff in plain http.
I do not know how to implement items 1, 2, and 6
Item 3 and 4 is simple. Item 5 is nonsense.
Is anyone interested in supporting me in this venture, and if so, how do
you propose we go about it.
If the backend is to still be a FoxPro application, then you'll need
someone experienced in putting FoxPro applications into the cloud as well.
I hope this helps. Even though I split this into 3-4 roles, it could be
that 1-2 people possess enough base experience to make it happen, or it
could be you'll need to work with 5-6.
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
