Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jvitasek/nwsltr
📫 NWSLTR: a ready-made self-hosted mailing system on PHP 8, Vue.js, Doctrine ORM and Nette Framework
https://github.com/jvitasek/nwsltr
doctrine-orm mailing nette-framework newsletter vuejs vuex
Last synced: 26 days ago
JSON representation
📫 NWSLTR: a ready-made self-hosted mailing system on PHP 8, Vue.js, Doctrine ORM and Nette Framework
- Host: GitHub
- URL: https://github.com/jvitasek/nwsltr
- Owner: jvitasek
- License: other
- Created: 2021-05-03T10:43:19.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-04-22T15:10:46.000Z (over 1 year ago)
- Last Synced: 2024-09-30T14:01:37.005Z (about 1 month ago)
- Topics: doctrine-orm, mailing, nette-framework, newsletter, vuejs, vuex
- Language: PHP
- Homepage:
- Size: 802 KB
- Stars: 2
- Watchers: 3
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: license.md
Awesome Lists containing this project
README
# NWSLTR
[](https://travis-ci.org/jvitasek/nwsltr)
[](https://github.com/jvitasek/nwsltr/blob/main/license.md)
[](https://opensource.org/)
This project contains a ready-made self-hosted mailing system written in PHP8, Nette Framework, Doctrine 2 and Vue.js
## System Requirements
- \>= PHP 8.0
- \>= MySQL 8
- Redis Server
- Composer
- Yarn + Webpack
## Installation
The ideal way of installing this project is via Composer:
```bash
$ composer create-project jvitasek/nwsltr
```
Or directly clone this repository:
```bash
$ git clone https://github.com/jvitasek/nwsltr.git
```
Once you have the project files, do the following:
1. Create an empty MySQL database
2. Create a new file config/test.neon and copy the contents of config/test.sample.neon in there
Now you have two options:
### Automatic installation (recommended)
1. Set the right permissions to the init script: `$ chmod +x bin/init` (UNIX only)
2. Run `$ bin/init` which takes care of all the necessary configuration
### Manual Installation
1. Create directories log and temp in the root folder (`$ mkdir log temp && chmod +x log temp`)
2. `$ composer i`
3. `$ php bin/console orm:clear-cache:metadata`
4. `$ php bin/console o:s:u -f`
5. `$ chmod +x bin/*` (UNIX only)
6. `$ php bin/console doctrine:fixtures:load -n`
7. `$ cd www/FrontModule && yarn && yarn build`
## Self-hosted Use
During the installation steps you loaded fixtures into the newly created database. These fixtures contain a sample account and a user. Once you finish the installation, you can access the website and log in using these credentials:
E-mail: `[email protected]`
Password: `secret`
With these credentials, you can access the system as an administrator. It is recommended to remove this account after creating a new one with a strong password.
### Crontab setup
When you self-host this application, you need to set-up a cronjob to automatically send the planned mailings.
```bash
1-59 * * * * php bin/console mailing:send
```
Alternatively, you can run this command anytime you need to send the newsletter
```bash
# does a dry run not actually sending the e-mails
$ php bin/console mailing:send -t
# actually sends the e-mails
$ php bin/console mailing:send
```
## Tests
This package comes with some ready-made tests.
### Acceptance Tests
For acceptence tests, Codeception was used. You can run these tests like this:
```bash
$ php vendor/bin/codecept run --steps
```
### Unit Tests
Unit and feature tests are run with Nette Tester
```bash
$ vendor/bin/tester -c tests/tester/php.ini tests/tester
```
### Static Analysis
There are two static analysis tools to help with detecting and fixing errors in the code.
**PHPStan**
```bash
$ vendor/bin/phpstan analyse
```
**PHP_CodeSniffer with error detection**
```bash
$ vendor/bin/phpcs --standard=ruleset.xml --extensions=php --tab-width=4 -sp app
```
**PHP_CodeSniffer with error fixing**
```bash
$ vendor/bin/phpcbf --standard=ruleset.xml --extensions=php --tab-width=4 -sp app
```
## Web Application Usage
All use-cases require logging in first. Next sections will assume you are already logged in to the system.
### Creating recipient data
It is important to first create some recipient data, since you cannot send a mailing without a recipient group with at least one subscribed recipient.
1. Access the Groups section in the left sidebar
2. Create the Group you want to send the mailing to (e.g. Golf Players)
3. Now you have 2 choices:
1. Import recipients to the created group using an Excel file
2. Add recipients manually in the Recipients section and indicate the created group in their Recipient Groups field
### Creating mailings
Now that we have some recipient data in the system, we can go ahead and start building a new mailing campaign.
1. Go to the Mailings section in the left sidebar and click on the Create Mailing button in the top-right corner
2. In the editor, proceed as follows:
1. Click on the pencil icon in the top-left corner of the screen and fill out the title, subject and the date of the mailing. Then indicate which Recipient Groups should receive the mailing.
2. Click on the plus icon in the top-left corner of the screen and use the components to build your mailing template.
3. (Optional) You can view the preview of your progress by clicking the Preview button in the top-right corner of the screen.
4. Once you are finished building the template, you can click the Back button and return to the Mailing datagrid.
5. Now you are ready to set the status of your newly created mailing to Ready. Based on the date that was set in the mailing editor, the system will automatically send the mailing once the date is reached (the crontab should ideally run every minute)