Re: [Pyallegro] New Site Redux

[AKX <th...@gm...>]

Phew, now there was some text.
I understand the point about having a cronjob rewrite the site, but
many a project even on SF.net use a MySQL based news system or CMS
without bigger problems, and besides, our database would be really
tiny. And, for some odd reason, I can successfully login now using the
admin interface. But if I changed the current news script to use MySQL
in order to make it to conform to the SF policies, I think that'd be
great. (Obvious Office Space reference there.)

Now for the CVS thing -- I'll just get TortoiseCVS and hope I can get
it all set up right. I've toyed around with TortoiseSVN a bit and I
liked it (for a tiny game project me and a friend started a while ago,
and no, it's not finished).

So, if I'll work out the kinks from the login and make it MySQL, we'd
be cool? Making it MySQL would also make it possible to make the front
page show all news and the project pages would show the respective
projects' news (and we could get a fancy RSS feed outta it as well).
The downside would be -- perhaps, it's only news, really -- that
there'd be no change log.

AKX

On 9/15/05, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> On 2005-09-15, AKX <th...@gm...> wrote:
> > I'm not that familiar with version control, so could you elaborate
> > on that CVS thing?
>=20
> Hmmm... I thought you would be using CVS for your pyrexx
> module. Through SourceForge you can create modules, which are really
> individual directories in a remote server. Now there is pyallegro,
> which will stay that way. I did imagine you would create one named
> rexx or something like that for your work.
>=20
> In the same way, the Allegro homepage is stored in a separate
> www module. There are stored the html pages as templates and the
> language translations as text files, similar to GNU .po files. On
> the SF shell server a cron takes all that stuff from CVS, does the
> template conversion and outputs the files on the directory where
> the web is supposed to be.
>=20
> With Allegro using CVS is necessary because it is the only way for
> several translators to work together in parallel without actually
> modifying files directly on the server. Plus the scripts make
> sure that the group permissions are ok for the files and something
> written by one can be modified or deleted by somebody else.
>=20
> The disadvantage is that SF recomends crons to not run more than
> once a day, and they will disable CPU intensive ones. But in this
> case it would be a matter of running the cp program excluding
> CVS directories.  Another disadvantage is that you don't modify
> things directly, so if you are doing .php or other dynamic webs,
> you need a local server for testing or log into SF and run manually
> the update script.
>=20
> The big advantages is that you keep track of every single change
> (email notification), you can roll back to previous versions and
> don't have problems with more than one person modifying the same
> file (because CVS would generate a conflict to resolve if needed).
> Personally, it's been years since I don't use any version control
> software for anything I write. It's a really nice tool to have.
>=20
> On the other hand, I won't be doing radical changes to the web page.
> As far as my development goes, releases are sporadic and it is
> enough for me to update that news file manually.
>=20
> In fact, if manual changes to the news file and your news admin
> interface don't exclude each other, I would recommend you to
> substitute the main page with your .php one and not worry too much
> about that web interface you were planning on doing. I'm sure you
> prefer to spend your time coding pyallegro than doing webmastery
> thingies (at least I do).
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your ver=
y
> own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>