Re: [php-gtk-webmaster] PHP-GTK Site

--001a1134f262ac4d40051700f803
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, May 26, 2015 at 12:23 AM, Alexandre Pereira B=C3=BChler <
[email protected]> wrote:

>  Ben and Jace,
> I got access to phpinfo.
> From what I studied in the source code they used sqlite as database.
> It was used even in the documentation. They were not fools.
> In the directory "gtk\manual" in file browse.php.
>
> I quote:
> "$ db =3D sqlite_open ($ notesfile);
> $ query =3D sqlite_query ($ db, 'SELECT DISTINCT "' $ order.. '" FROM not=
es');
> "
>
> *Note: PHP 5.4 has ceased to be the driver for SQLite, now only work with
> sqlite3. For this reason the site stopped working **a few things.*
>
>  In this php.info released the PDO Sqlite driver and native sqlite3.
> If they over 10 years ago using sqlite to make life easier, why not do
> the same?
> I will see some guidelines to continue, the php core are on low incomes.
> This makes inefficient use of any framework.
> But surely we have to do everything from scratch with use of php + sqlite=
.
>

As I said earlier, if you need to use a database in redesigning the site,
then you'll need to use SQLite. However, using the repository, we cannot
separate anything from the web root, since the entire repository is in the
web root. So, it's not a good idea to put the SQLite database in the web
root, and if we need to use one, we'll need to pester one of the system
admins to put one in a secure location on the machine.

My recommendation is to not use a database. Instead, we can continue to use
similar approaches used in the past on web-gtk and web-php for news entries
and dynamic content. A simple directory containing a bunch of static files
could work well for news entries, or a single file containing a PHP array
of all the new entries would also work. This would allow others to easily
contribute by sending pull requests to the repository to add news items,
and we could manage all our content through version control.

Using a database would not allow for contributing in this way, since people
who want to add content would need access to the database. I think it's
better to manage content through version control for a site like this, so
that anyone is able to contribute through pull requests.

Let's also be careful not to jump into needing a big full-stack framework
for this website. All the deployment processes for deploying web-gtk are
already in process, and none of them include things like running `composer
install`, so we'll need to be mindful of that. Whatever third-party
packages we use will need to be committed to the repository.

My advice is to start small. If you have already been working on a
redesign, get an HTML/CSS/JS prototype for that ready and post a link to it
here so that people may review and comment on it. Then, we can start
deciding the best approach to fit it into web-gtk, which will involve
creating a new branch and getting rid of a bunch of the old stuff in it,
then adding your new design.

Cheers,
Ben

--001a1134f262ac4d40051700f803--