Server requirements / preferences

igor

Hi!

I have been testing a first setup of TastyIgniter for a little while now. Quite happy I have to say.

Currently, hosting in the cloud with 1 CPU, 2GB Ram, 20GB HDD and based on a Debian 10 with NGINX and MariaDB. I followed closely the installation steps as outlined in the TastyIgniter doumentation.

Since there are no indications about server requirements, I wonder if there would be a preference for any distro? (I myself usually grab CentOS 7 or 8) I’m not expecting a massive user-load, if we would receive some hundreds of visitors and about 50 or so actual orders, we’d be happy already.

I wonder about some tips from the community? (especially regarding the linux distro of preference?) 😉

Thanks, cheers,
Igor

mlattke

igor 2 Cores / 30 GB SSD/HDD Storage / 2 GB RAM. I’ve installed TastyIgniter in Ubuntu Server 18.04/20.04. Worked without any problem. However keep in mind the recommendation about docker @breaksecurity just posted.

breaksecurity

I can advise you to built up docker with any light server distro.

Also I can advise you to read about laravel queue to improve tasty performance on heavy job (mail sending, push notification)

@sampoyigi I do not know if changing app preference to production will have any real benefits

Plus you should disable debug from app.php in config folder

Just some random hints

igor

Thank you breaksecurity ! I have read up a lot on docker setup, but I have no experience with docker at all.. This makes me hesitant to choose that direction..

Disabling debug was on my to-do list indeed, but laravel queue performance was something I didn’t consider, so thanks for that hint!

also mlattke : great to know and thanks!

sampoyigi

breaksecurity @sampoyigi I do not know if changing app preference to production will have any real benefits

It does have some benefits (‘disables’ some risky artisan commands) and is recommended before going live.

breaksecurity

mlattke Do you run only one instance of tasty on this setup?

@sampoyigi Which VPS requirements would you suggest for 5 to 10 instance of tasty?

breaksecurity

Also shared webhosting is a good solution too if you wanna save some money

igor

sampoyigi breaksecurity @sampoyigi I do not know if changing app preference to production will have any real benefits

It does have some benefits (‘disables’ some risky artisan commands) and is recommended before going live.

Not sure what is meant with; ‘changing app preference to production’? Is this something that I should configure and how? (I would run some more tests to see how/if this behaves different from my current verification-setup)

breaksecurity

Is a bit off-topic, but anyway since key:generate is flagged as a risky command I will ask here. What does tasty do with generated key? Is a good practice to have the same key across different tasty server (I suppose not but why)? Which problem will rise if I’ll execute anyway the command?

breaksecurity

In config folder app.php env dev should became production

breaksecurity

I am trying a new setup with docker and I wanna share with you all my thoughts.

Actually I want to try LaraDock: https://github.com/laradock/laradock