duckypanel v0.0.5

NOTE: This project is still a work in progress. You can already check it out if you're curious, but I can't guarantee it will work out for you.

DuckyPanel

Duckypanel is a domain admin level control panel for the modern WildDuck email server. DuckyPanel is just an Angular frontend project. It uses the DuckyAPI REST API as the backend.

Current features

Things currently working in DuckyPanel and DuckyAPI.

• Authentication
• API keys allow you to easily call DuckyAPI
• Packages that allow you to set user quotas, currently only for show. Nothing happens when going over quota.
• Domain management, including domain aliases
• Deletes aliased domains, accounts, forwarders and DKIM when deleting a domain
• Manage DKIM for the domains
• Email account management
• Forwarder management
• Only allows seeing/editing of accounts/forwarders on a domain if that domain is added to the account
• Domains can not be added to multiple accounts
• Get expected DNS records for a domain, and check the currently published records
• Sorting and filtering

More to come!

Screenshots

Option 1: Serve DuckyPanel from DuckyApi

Very easy to get started with. See the instructions here.

Option 2: Serve DuckyPanel seperately from DuckyApi

Recommended if you want to scale and distribute the applications differently. As an example you could host DuckyPanel on a fast CDN.

Dependencies

• Node.js
• DuckyAPI
• A web server (if in production)

Installation

$ git clone https://github.com/louis-lau/DuckyPanel
$ npm install

Configuration

Copy src/config/example.json to src/config/production.json or src/config/development.json depending on your environment. Then edit apiUrl to be your publically accessible url of DuckyAPI, so DuckyPanel knows where to reach it.

Build

Run npm run build for a production build. The build artifacts will be stored in the dist/ directory.

After building you can serve the build artifacts with any webserver you're comfortable with. You will need to configure the server to fallback to index.html for the routing to work properly. Here are some configuration examples for the most popular web servers.

Development server

Follow the above instructions for installation and configuration, then run npm start for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files. Do not use this in production.