Skip to content

Commit

Permalink
minor syntax changes
Browse files Browse the repository at this point in the history
mjoycemilburn committed Nov 1, 2020
1 parent 8314996 commit 91e0590
Showing 2 changed files with 8 additions and 8 deletions.
8 changes: 4 additions & 4 deletions INSTALLATION_GUIDE.md
Original file line number Diff line number Diff line change
@@ -4,12 +4,12 @@ In order to install the software from this repository and create a demo website

1. Having opened the ISP account with a master url, create an "addon url" for council_a

2. Copy the council_a and council_shared_code folders into public_html for the master url
2. Copy the council_a and council_shared_code folders from the repository into public_html for the master url

3. Create a database called parishcouncildsb and initialise this with the script contained in demo_database_script.sql
3. Create a database called parishcouncilsdb and initialise this with the script contained in demo_database_script.sql

4. Copy the connect and disconnect.php files from the repository into the root folder for the url and initialise these with the keys for the database you have just created

5. You should now be able to able to view the demo website for council_a by running url http://council_a and you should be able to run the maintenance system for its entries in the shared database by running url http://council_a/manager.php
5. You should now be able to able to view the demo website for council_a by running url http://council_a and you should be able to enter the maintenance system for its entries in the shared database by running url http://council_a/manager.php

It is assumed that the addition of further councils to the system will be handled in a similar adhoc way - the exact nature of the coordinating arrangement will vary. At present, for example, the only way in which new access rights can be added and old ones changed is by direct manipulation of the users table in the database by means of the phpMyAdmin package. It shouldn't be too difficult to add further facilities in this area if it was felt that this were worthwhile
It is assumed that the addition of further councils to the system will be handled in a similar ad-hoc way - the exact nature of arrangements in this area are likely to vary considerably. At present, for example, the only way in which new access rights can be added and old ones changed is by direct manipulation of the users table in the database using the phpMyAdmin package (or similar). For the present this aspect of the application is not addressed. It shouldn't be too difficult to provide more advanced facilities if this is felt worthwhile.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
The ***parishcouncils*** system provides a mechanism whereby a group of Parish Councils (or an umbrella organisation providing Councils with common service) may join forces to deliver website facilities to meet their statutory obligations.
The ***parishcouncils*** system provides a mechanism whereby a group of Parish Councils (or an umbrella organisation providing Councils with common services) may join forces to deliver website facilities to meet their statutory obligations.

The motivation for the development is described in ***parishcouncil***, an earlier iteration of the concept. The parishcoucil*** system was aimed at individual councils who wanted a lightweight design that minimised the tasks of system implementation. The new ***parishcouncils*** system, by contrast:
The motives for the development are described in ***parishcouncil***, an earlier iteration of the concept. The parishcoucil*** system was aimed at individual councils who wanted a lightweight design that minimised the tasks of system-implementation. The new ***parishcouncils*** system, by contrast:
1. operates on a more substantial technical platform (it uses a mySQL database) and
2. enables participating councils to take advantage of the economic and administrative benefits of working cooperatively.

@@ -10,8 +10,8 @@ The organising body has the following responsibilities:

1. Opening an ISP account and acquiring the initial master url
2. Installing the ***parishcoucils** system (see INSTALLATION_GUIDE)
3. Acquiring an "additional url" to the master url for each participating council and configuring a corresponding sub-folder on the ISP
4. Creating and maintaining user_id/password rights to protect the council's use of the maintenance system.
3. Acquiring an "additional url" for each participating council and adding a corresponding sub-folder to the initial master url on the ISP
4. Creating and maintaining user_id/password rights to protect each council's use of the maintenance system.

Each council will now have its own version of the master council website and will be able to personalise this and maintain it into the future.

0 comments on commit 91e0590

Please sign in to comment.