Skip to content
This repository was archived by the owner on Nov 8, 2020. It is now read-only.

Latest commit

 

History

History
204 lines (144 loc) · 7.34 KB

installation.md

File metadata and controls

204 lines (144 loc) · 7.34 KB

Installing mymedic

Prerequisites

If you don't want to use Docker, the best way to setup the project is to use the same configuration that Homestead uses. Basically, mymedic depends on the following:

Git: Git should come pre-installed with your server. If it doesn't - use the installation instructions in the link.

PHP 7.1+: Install php7.2 minimum, with these extensions:

  • json
  • iconv
  • intl
  • opcache
  • mbstring
  • xml
  • mysqli
  • pdo_mysql
  • bcmath
  • curl
  • gmp
  • zip
  • gd

Composer: After you're done installing PHP, you'll need the Composer dependency manager. It is not enough to just install Composer, you also need to make sure it is installed globally for mymedic's installation to run smoothly:

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php composer-setup.php --install-dir=/usr/local/bin/ --filename=composer
php -r "unlink('composer-setup.php');"

Mysql: Install Mysql 5.7+

Types of databases

The official mymedic installation uses mySQL as the database system and this is the only official system we support. While Laravel technically supports PostgreSQL and SQLite, we can't guarantee that it will work fine with mymedic as we've never tested it. Feel free to read Laravel's documentation on that topic if you feel adventurous.

Installation steps

Once the softwares above are installed:

1. Clone the repository

You may install mymedic by simply cloning the repository. In order for this to work with Apache, which is often pre-packaged with many common linux instances (DigitalOcean droplets are one example), you need to clone the repository in a specific folder:

cd /var/www
git clone https://github.com/StrixTech/mymedic.git

You should check out a tagged version of mymedic since master branch may not always be stable. Find the latest official version on the release page.

cd /var/www/mymedic
git checkout tags/v1.0.0

2. Setup the database

Log in with the root account to configure the database.

mysql -uroot -p

Create a database called 'mymedic'.

CREATE DATABASE mymedic;

Create a user called 'mymedic' and its password 'strongpassword'.

CREATE USER 'mymedic'@'localhost' IDENTIFIED BY 'strongpassword';

We have to authorize the new user on the mymedic db so that he is allowed to change the database.

GRANT ALL ON mymedic.* TO 'mymedic'@'localhost';

And finally we apply the changes and exit the database.

FLUSH PRIVILEGES;
exit

3. Configure mymedic

cd /var/www/mymedic then run these steps:

  1. cp .env.example .env to create your own version of all the environment variables needed for the project to work.
  2. Update .env to your specific needs. Don't forget to set DB_USERNAME and DB_PASSWORD with the settings used behind.
  3. Run composer install --no-interaction --no-suggest --no-dev to install all packages.
  4. Run php artisan key:generate to generate an application key. This will set APP_KEY with the right value automatically.
  5. Run php artisan setup:production -v to run the migrations, seed the database and symlink folders.

The setup:production command will run migrations scripts for database, and flush all cache for config, route, and view, as an optimization process. As the configuration of the application is cached, any update on the .env file will not be detected after that. You may have to run php artisan config:cache manually after every update of .env file.

4. Configure cron job

mymedic requires some background processes to continuously run. The list of things mymedic does in the background is described here. Basically those crons are needed to send reminder emails and check if a new version is available. To do this, setup a cron that runs every minute that triggers the following command php artisan schedule:run.

  1. Open crontab edit for the apache user:
crontab -u www-data -e
  1. Then, in the text editor window you just opened, copy the following:
* * * * *   /usr/bin/php /var/www/mymedic/artisan schedule:run

5. Configure Apache webserver

  1. Give proper permissions to the project directory by running:
chgrp -R www-data /var/www/mymedic
chmod -R 775 /var/www/mymedic/storage
  1. Enable the rewrite module of the Apache webserver:
a2enmod rewrite
  1. Configure a new mymedic site in apache by doing:
nano /etc/apache2/sites-available/mymedic.conf
  1. Then, in the nano text editor window you just opened, copy the following - swapping the YOUR IP ADDRESS/DOMAIN with your server's IP address/associated domain:
<VirtualHost *:80>
    ServerName YOUR IP ADDRESS/DOMAIN

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/mymedic/public

    <Directory /var/www/mymedic/public>
        Options Indexes FollowSymLinks
        AllowOverride All
        Require all granted
    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
  1. Apply the new .conf file and restart Apache. You can do that by running:
a2dissite 000-default.conf
a2ensite mymedic.conf
service apache2 restart

6. Optional: Setup the queues with Redis, Beanstalk or Amazon SQS

mymedic can work with a queue mechanism to handle different events, so we don't block the main thread while processing stuff that can be run asynchronously, like sending emails. By default, mymedic does not use a queue mechanism but can be setup to do so.

We recommend that you do not use a queue mechanism as it complexifies the overall system and can make debugging harder when things go wrong.

This is why we suggest to use QUEUE_DRIVER=sync in your .env file. This will bypass the queues entirely and will process requests as they come. In practice, unless you have thousands of users, you don't need to use an asynchronous queue.

That being said, if you still want to make your life more complicated, here is what you can do.

There are several choices for the queue mechanism:

  • Database (this will use the database used by the application to act as a queue)
  • Redis
  • Beanstalk
  • Amazon SQS

The simplest queue is the database driver. To set it up, simply change in your .env file the following QUEUE_DRIVER=sync by QUEUE_DRIVER=database.

To configure the other queues, refer to the official Laravel documentation on the topic.

After configuring the queue, you'll have to run the queue worker, as described in the Laravel documentation.

php artisan queue:work --sleep=3 --tries=3

Some process monitor such as Supervisor could be useful to monitor the queue worker.

Final step

The final step is to have fun with your newly created instance, which should be up and running to http://localhost.