AmigaOS4: AAMP 1.0 for AmiCygnix released. - Software News - News

Software News : AmigaOS4: AAMP 1.0 for AmiCygnix released.

Posted by cygnusEd on 2010/2/22 19:32:24 (2302 reads) News by the same author

A first version of the server package AAMP for AmiCygnix is now available on
OS4 depot.

This package provides a developer environment to create your web projects
on your Amiga. Just like the well known LAMP package for Linux, it includes
the HTTP (web) server "Apache" with compiled in support for the scripting
language "PHP" and the database server "MySQL".

But it is not only interesting for web developers. Now you can run web app-
lications locally on your Amiga, for example the database administration tool
"phpMyAdmin" (http://www.phpmyadmin.net/home_page/index.php) or the picture
database "Coppermine" (http://coppermine-gallery.net) - just to mention a few.

With the included interpreter for "PHP" you can also create your own tools.
"PHP" is easy to understand and with it's extensions it is very powerful.

Finally the database server "MySQL" gives you the oportunity to manage your
data and share it with other users. External applications (e.g. iodbc) can use
it as a database backend.

Because some problems are still unsolved, this is not the final version. The
main problem is, that the Apache CGI module is not working. Read more on the
README page on OS4-depot.

Download: http://os4depot.net/?function=showfil ... r/misc/aamp-amicygnix.lha

Snapshots:
AAMP, OWB, phpMyAdmin:

AAMP, OWB, XOOPS:

AAMP, OWB, Coppermine:

Homepages:
Apache: http://httpd.apache.org
MySQL: http://www.mysql.com
PHP: http://php.net

The comments are owned by the author. We aren't responsible for their content.

Author	Thread
Antique	Published: 2010/2/22 19:41 Updated: 2010/2/22 19:41
Home away from home Joined: 11/30/2006 From: Norway Comments: 2628	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Nice work. This is part 1 of the bounty?

kas1e	Published: 2010/2/22 19:55 Updated: 2010/2/22 19:55
Home away from home Joined: 09/11/2007 From: Russia Comments: 9109	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. In last time some really nice apps are out. Agfgroup#s sql manager/etc, yam , and now, that pretty important pice of software. Thanks. Hope soon it will be native (bounty #2) @CygnixED What about speed ? Its works fine/fast ?

virgola	Published: 2010/2/22 20:52 Updated: 2010/2/22 20:52
Just popping in Joined: 02/01/2007 From: Bergamo, Italy Comments: 122	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Great move Edgar! Looking forward to use it when I'll get back home to my Sam!

328gts	Published: 2010/2/22 21:11 Updated: 2010/2/22 21:11
Home away from home Joined: 07/07/2009 From: Man Cave, Canada Comments: 3127	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. thanks Ed ....donation coming your way...looking forward to using MySQL on my Miggy for some small webpage projects I got going

Elwood	Published: 2010/2/22 22:28 Updated: 2010/2/22 22:28
Just can't stay away Joined: 12/09/2006 From: Lyon, France Comments: 1370	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. @Antique This is not yet the first phase of the bounty because: Quote: The CGI module - which is required to complete the bounty - is not working But I'm sure we'll see it soon Go Edgar, go

Bender	Published: 2010/2/22 23:09 Updated: 2010/2/22 23:09
Just popping in Joined: 01/12/2010 From: Mexico City Comments: 7	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Great news! Thanks!! Regards, Efren

Paul	Published: 2010/2/23 3:11 Updated: 2010/2/23 3:11
Quite a regular Joined: 12/01/2006 From: Michigan, USA Comments: 583	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Edgar, The text message that pops up telling what to add in devs/internet got away from me before I could cut and paste. Is there a place in the files I can find that? If it's in the install script, I missed it. Nor did I find it in any of the read-me's I looked at. Thanks. Paul

cygnusEd	Published: 2010/2/23 20:50 Updated: 2010/2/23 20:50
Quite a regular Joined: 12/24/2006 From: Germany Comments: 566	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. @ Antique Quote: This is part 1 of the bounty? Yes, but it is not complete. CGI is missing. @ kas1e Quote: What about speed ? Its works fine/fast ? I think speed is good, but it is not fast enough for hosting websites. The package is for development and to run local web projects. Works fine in my tests so far. But I'm sure, that not all web packages will work. Although I wanted to have maximum Unix compatibility, not everything could be implemented. @ virgola Quote: Looking forward to use it when I'll get back home to my Sam! Please install this version. A lot of things were fixed including the OWB problem @ 328gts Thanx for the donation @ Elwood Will continue with CGI asap, but first I need a break @ Paul Have a look at the file "install-data/AfterInstall.txt" in the installation package!

nbache	Published: 2010/2/27 15:03 Updated: 2010/2/27 15:03
Just can't stay away Joined: 12/01/2006 From: Copenhagen, Denmark Comments: 1532	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Congratulations on getting this far, Edgar! This is important in so many ways. I look forward to checking it out, even if I can't/won't use it as replacement for my current 1.3.33 Apache server just yet (non-working CGI, AmiCygnix dependance). But I am surprised to hear all the statements about it not being useful for "real" sites. Is this not intended eventually? E.g. the readme states: Quote: Minor problems: * The web server does not support subprocesses. As this package is not meant for productive use, this is not really a problem. Development and using local web applications is no problem. * The MySQL server cannot be stopped, when InnoDB tables are enabled. This type of table is only useful, if you want to use the server for productive jobs - same as above. You can work with InnoDB tables, I did not have any problem. But they are always checked on server startup, because of the unfinished shutdown. On the other hand, I don't see any reason to use this kind of tables. I can see why subprocesses in Apache are a problem under AmigaOS, or at least more difficult. Which (I assume) means that only one visitor at a time can be served. But I'm using the current Apache with this limitation just fine on a public site (well, not "public" public, only visited by family and friends, but still). But about InnoDB tables in MySQL, I fail to see why we wouldn't want to use those? Now, granted, I'm an Oracle guy in daily life myself, but I assume transactions in MySQL/InnoDB are basically equivalent to transactions in other databases, e.g. Oracle? I wouldn't want to develop any kind of database application without having transaction support in the database, even during development. So can you elaborate a bit on what the current problems are, and whether they can be solved? Best regards, Niels

cygnusEd	Published: 2010/2/28 7:11 Updated: 2010/2/28 7:11
Quite a regular Joined: 12/24/2006 From: Germany Comments: 566	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Quote: I look forward to checking it out, even if I can't/won't use it as replacement for my current 1.3.33 Apache server just yet (non-working CGI, AmiCygnix dependance). Some words about the native version I like to say: Although I know, that a lot of people are waiting for a native version, I cannot understand it. The AmiCygnix libraries do offer best Unix compatibility, which is not guaranteed in the following native version. And: This current package includes a minimalistic AmiCygnix package, that only needs 11 MB. The important question for me is, how much native should the native version be?? When I use the native locale libs, functions like setlocale(), localeconv() and also changing the locale with putenv("TZ", "...") will not work. When I use amiga style paths, most of the available web packages will refuse to work. I could add a lot more examples here. I think I have to create a poll to find out, what is expected from a native version. Quote: But I am surprised to hear all the statements about it not being useful for "real" sites. Is this not intended eventually? I can see why subprocesses in Apache are a problem under AmigaOS, or at least more difficult. Which (I assume) means that only one visitor at a time can be served. But I'm using the current Apache with this limitation just fine on a public site (well, not "public" public, only visited by family and friends, but still). Yes, you're right. Without subprocesses, Apache can only handle one request after the other. When I say "real sites", I mean to host pages for a wide audience like other pages on the web. If only a few users do access the hosted pages, I think it is o.k. to use this AAMP package. It works fine in my local network. But: Because of several reasons I cannot recommend this AAMP package for hosting webpages. This starts with the low end hardware and continues with security problems on the Amiga. Even with implemented subprocesses I can't do that. Quote: But about InnoDB tables in MySQL, I fail to see why we wouldn't want to use those? Now, granted, I'm an Oracle guy in daily life myself, but I assume transactions in MySQL/InnoDB are basically equivalent to transactions in other databases, e.g. Oracle? I wouldn't want to develop any kind of database application without having transaction support in the database, even during development. So can you elaborate a bit on what the current problems are, and whether they can be solved? I'm not a database specialist, but in my opinion, if you use AAMP only for development, you don't need things like transactions or row-level locking. I've made some stress tests with MyISAM tables - I never had any problems. And: InnoDB tables on Amiga are not the same than InnoDB tables on Unix systems. For example AmigaOS does not support partially file locking, which is a important requirement for InnoDB. The problem with InnoDB in AAMP is, that this storage driver launches about 10 subprocesses and they cannot be stopped. One reason: PThreads does not support pthread_kill(). I have to implement a special solution for this and I don't know, if I can do that. On the other hand, InnoDB seems to work good. Only on server startup the tables have to be checked. If you like, you could do some tests with InnoDB tables. I'm sure, you're knowledge is better than mine here.

pvanni	Published: 2010/2/28 10:09 Updated: 2010/2/28 10:09
Not too shy to talk Joined: 12/05/2006 From: Lecco, Italy Comments: 319	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. @cygnusEd, About native version, my opinion is: this AAMP version need some AmiCygnix library, but it run without an active AmiCygnix so for me this very version is native. Otherwise for me it's like to say a MUI program it's not native. P.S. thanks for your great work

nbache	Published: 2010/2/28 18:39 Updated: 2010/2/28 18:39
Just can't stay away Joined: 12/01/2006 From: Copenhagen, Denmark Comments: 1532	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Native <> AmiCygnix: I am personally mainly interested in Apache (although I will of course also look forward to having MySQL available - PHP is completely outside my field of interest). The current Apache 1.3.33 port is what I consider native, i.e. it does not depend on AmiCygnix, so I don't have to spend time and effort finding out how AmiCygnix should be installed, set up and maintained, and what influences it has on my system. This sort of situation is what I'm hoping to see with the native version of Apache 2.x. Transaction support: To make a very crude analogy, saying that you don't need transaction support if you only want to develop is a bit like saying you don't need an oven while you're inventing your new bread recipe. Transactions are something you want to use whenever your application needs to update (insert, delete) more than one item as one logical change, where you want everything either committed or rolled back (in case of errors). This is something you want to code into your application from the start, so it needs to be available also in your development system. Row level locking, on the other hand, is not as important, since we won't normally have more than one session at a time anyway, so it's no problem to lock a whole table while updating. I assume the requirement for partial file locking is related to row level locking? If so, I'd say that is also less important. About pthread_kill(): Have you tried asking whether support for this is planned/in the works? Best regards, Niels

cygnusEd	Published: 2010/2/28 22:22 Updated: 2010/2/28 22:22
Quite a regular Joined: 12/24/2006 From: Germany Comments: 566	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. @ nbache To transactions: I think I misunderstood this feature completely . Had a look at the wikipedia pages and now I have a better understanding. BTW: Transactions should work in the current AAMP package. Quote: About pthread_kill(): Have you tried asking whether support for this is planned/in the works? No, I didn't. But as far as I know, it is not planned. Killing tasks is not possible on AmigaOS like on Unix systems. I'm afraid, I have to go an other way.

nbache	Published: 2010/3/1 20:32 Updated: 2010/3/1 20:32
Just can't stay away Joined: 12/01/2006 From: Copenhagen, Denmark Comments: 1532	Re: AmigaOS4: AAMP 1.0 for AmiCygnix released. Quote: To transactions: I think I misunderstood this feature completely Ah, no wonder then Quote: Transactions should work in the current AAMP package. Good news! Quote: But as far as I know, it is not planned. Killing tasks is not possible on AmigaOS like on Unix systems. I'm afraid, I have to go an other way. Hmm, that's too bad. I'm not familiar with pthreads, but it sounds strange that there wouldn't be a way to provide such functionality. Hope you find a good solution without having to do too much re-inventing of wheels. Best regards, Niels