How it works - short version
Sites:
- API: The public API (api.{domain})
- app: Reversed proxy that lets the site and devices talk to the main API (NodeJS server).
- dpcpacker: A service that are packing Deployment Client to an MSI file.
- feed: Slightly modified Nuget server to host all nuget feeds (Only Windows).
- package: Simple nuget package generator (from EXE and MSI files) (Only Windows).
- socket.io: Same as app, but for /socket.io. It points to the same NodeJS server.
- app: This is the public site (app.{domain}).
- mdcfeeddeploy: A service that deploys a new nuget feed (the MDC feed in Deployify) when a user is signing up (Only Windows).
Neo4j
Database. Accessible via http://localhost:7474.
Vault
A vault to store hashed user passwords. Encrypted storage that needs to be unsealed to be accessible.
Your server is configured to unseal your vault automatically on startup, which is not the way it should be done. It should not be automated, that's the whole point with Vault. But at least, you have the option to make it safer. We unseal our vault manually, so if the storage is stolen, it will not be accessible.
Deployment client
You are in control of Deployment client updates. Just put the new version, or old, in this folder:
Windows: %programdata%\MDC\api\dpc_packer\pkg
Ubuntu: {installdir}/api/dpc_packer/pkg
All clients will update to that version. We will post updates somewhere on this site for you to decide for yourself if you want to use them in your Deployify.
Plugins - How to install
Instructions on how to install plugins for Deployify server.
Installation:
- Download plugin (zip).
- Extract zip.
- Move the folder to (win) %programdata%\MDC\api\plugins\, or (Linux) {installdir}/api/plugins/.
- Restart server or restart node.
Note:
A plugin is a folder, and in that folder it should be at least one file named app.js (and possible other files and folders) directly in the plugin folder. For example: api\plugins\disable_signup\app.js.