LEPP stack (Linux, (e)nginx, PostgreSQL, PHP)

[deutrino]

Please see https://github.com/deutrino/lepp and note that there is a php7.2 branch in addition to master which uses the default PHP like most other TKL 15 apps.

This is my first build and my first time touching TKL as anything other than a user, so I'm hoping someone can check my work.

[deutrino]

Also, the commit history is still a mess, but I imagine if this is good and you want to use it officially, you'd just take a snapshot of the files, no? I'm planning to develop a couple other TKL apps on top of this, FWIW - a CalDAV server + web app to get more familiar with the process, and then an app built on Erlang / Elixir which will be significantly more complex.

[JedMeister]

As noted in the forums, it might be useful to move some of the shared code into common?! As I hinted in the forums, a lot of the LAMP and LAPP code (plans, conf scripts and overlay files) is (are) contained within common. So doing something similar with LEMP/LEPP code might be a worthwhile endeavour?!

No pressure of course, but it may make your development easier (i.e. following the DRY principle). Just make sure that you also open a pull request against common and note that your appliance code depends on it (the code will likely make it obvious, but worth explicitly noting here within this "new appliance" issue).

I'm pretty tied up with v16.0 development at the moment, but I'd really love to have a closer look at this ASAP. From a glance it looks like you've done a fantastic job! 😄

a CalDAV server + web app

That sounds awesome! :)

[deutrino]

Oh that sounds fine, maybe it will translate to v16 :)

It will take me a few days, but I'll see about breaking it up like you suggest. Thanks!

[JedMeister]

You're most welcome. Thanks for your work on this! 😄

Also:

Also, the commit history is still a mess, but I imagine if this is good and you want to use it officially, you'd just take a snapshot of the files, no?

Generally we just fork the new appliance repo code into the relevant TurnKey organisation (in the case of appliance buildcode, that's turnkeylinux-apps). TBH, looking at your commit history it doesn't look too bad to me! 😄 You obviously haven't looked closely at some of the other appliance's commit history! 😆

[deutrino]

I'm restarting this effort now that version 16 is out, and intending to merge the lapp and nginx-php-fastcgi appliances, leaving something close to nginx + php-fastcgi + postgresql, and maybe the python bells & whistles from the lapp appliance.

The repo now at https://github.com/deutrino/lepp is forked from lapp, I'm starting with that.

[deutrino]

Back attempting to get this going again.

[JedMeister]

Looking a bit closer at this, I have some suggestions for you:

Firstly, I think that the Nginx appliance (i.e. nginx-php-fastcgi aka LEMP) is probably a closer start than the LAPP appliance IMO.

Then you'd just need to update the Makefile. Replace line 4:

include $(FAB_PATH)/common/mk/turnkey/nginx-php-mysql.mk

with these 3 lines:

include $(FAB_PATH)/common/mk/turnkey/nginx.mk
include $(FAB_PATH)/common/mk/turnkey/php-fpm.mk
include $(FAB_PATH)/common/mk/turnkey/pgsql.mk

We don't have an existing plan that will install exactly what you want, but manually constructing one shouldn't be too hard. I'd recommend just using the common nginx-php-fpm-mysql and LAPP plans as reference, but (obviously) exclude all references to mysql or apache related packages.

There's probably details I'm overlooking, but that should get you a good 70-80% of the way there I reckon.

[l-arnold]

The original TKL Odoo Appliance was essentially like this. I recall it running on Nginx with PostgreSQL and Odoo. At least my recollection. Apache took over soon after. Landis From: "Jeremy Davis" ***@***.***> To: "turnkeylinux/tracker" ***@***.***> Cc: "Subscribed" ***@***.***> Sent: Thursday, January 5, 2023 8:37:50 PM Subject: Re: [turnkeylinux/tracker] LEPP stack (Linux, (e)nginx, PostgreSQL, PHP) (#1345) Looking a bit closer at this, I have some suggestions for you: Firstly, I think that the Nginx appliance (i.e. [ https://github.com/turnkeylinux-apps/nginx-php-fastcgi | nginx-php-fastcgi ] aka LEMP) is probably a closer start than the LAPP appliance IMO. Then you'd just need to update the [ https://github.com/turnkeylinux-apps/nginx-php-fastcgi/blob/master/Makefile | Makefile ] . Replace line 4: include $(FAB_PATH)/common/mk/turnkey/nginx-php-mysql.mk with these 3 lines: include $(FAB_PATH)/common/mk/turnkey/nginx.mk include $(FAB_PATH)/common/mk/turnkey/php-fpm.mk include $(FAB_PATH)/common/mk/turnkey/pgsql.mk We don't have an existing plan that will install exactly what you want, but manually constructing one shouldn't be too hard. I'd recommend just using the common [ https://github.com/turnkeylinux/common/blob/master/plans/turnkey/nginx-php-fpm-mysql | nginx-php-fpm-mysql ] and [ https://github.com/turnkeylinux/common/blob/master/plans/turnkey/lapp | LAPP ] plans as reference, but (obviously) exclude all references to mysql or apache related packages. There's probably details I'm overlooking, but that should get you a good 70-80% of the way there I reckon. — Reply to this email directly, [ #1345 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABLJD2HYA3TNEFBROPRR2R3WQ6HQ5ANCNFSM4IDSCJ7A | unsubscribe ] . You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>