Skip to content

Latest commit

 

History

History
286 lines (220 loc) · 16.5 KB

CHANGELOG.md

File metadata and controls

286 lines (220 loc) · 16.5 KB
Raw

[Next Version - available as edge]

  • Improved renaming process. We now automatically generate new webhook when the app is renamed. (caprover#499)
  • Improved renaming process - now checking for name clash before renaming. (caprover#498)
  • Improved validation logic for the webhook build trigger. (caprover#496)
  • Fixed bug with pulling from private registries running on custom ports, (caprover#500)
  • Automatically focusing on password field upong admin page load.
  • Fixing Progressive Web App prsentation of the admin page (caprover/caprover-frontend#24)
  • Keeping tabs on Apps Details page when the page reloads.
  • Allowing user to remove the webhook git repo info

[1.5.2] - 2019-08-15

  • Fixed a problem with one-click app deployment on new installations. caprover#481

[1.5.1] - 2019-08-14

New features & Improvements:

  • Ablity to use websockets without having to manually edit nginx config (caprover#439)
  • Double hyphen in "image name" is now changed to single hyphen, img-captain--myapp is now changed to img-captain-myapp. This is to address the problem with 3rd party docker registries. See (caprover#454). Note that this is only applied to the newly built images. All existing images will stay intact. Also keep in mind that service names and volume names remain the same with double hyphens for now.
  • Builds are now being queued instead of dropping the build if another one is in progress. See (caprover#266)
  • Ability to rename apps (caprover#402)
  • Limiting login failures to avoid brute-forcing the password (caprover#419)
  • Switched to fake certs for https catch all to avoid disclosing dashboard address.
  • Pulling nginx and certbot images to ensure smooth install even on buggy docker installations. See this: caprover#450
  • Make the root domain available as a variable in one-click apps. See caprover#435

Bug fixes:

  • Backup creation was fixed for instances that were migrated from CaptainDuckDuck
  • Python and Ruby templates were patched to allow using latest version of Linux automatically
  • updated npm packages to address potential vulnerabilities

[1.4.0] - 2019-04-07

New Features:

  • Added SSH key support for git webhook automatic deploy (caprover#342)
  • Added built-in support for HTTP basic auth (caprover#336)
  • Added option to add some app notes (description) to your apps (caprover#403)
  • Changed One-Click app selector to allow search (caprover#394)
  • Setting maximum version history to last 50 versions to keep the config file small
  • Added Remember Me to web dashboard
  • Added option to delete volumes when persistent app is being deleted

Bug fixes:

  • Auto redirect after Force SSL was broken on frontend (caprover#399)

[1.3.0] - 2019-03-04

Added:

  • Backup capability added (for configs and SSL certs). See docs for more details.
  • Health checks are now excluded from CapRover and nginx logs
  • Front-end is now almost mobile friendly.
  • Improved default SSL (caprover#371)
  • Ability to change the root domain post installation

Fixed:

  • Web UI now waits for logs to get retrieved before sending another refresh. This fixes the rare case where the entire UI hangs because of Docker being unresponsive.
  • Fixed non English characters in the logs
  • Logs are now correctly sorted on the front-end

[1.2.1] - 2019-02-11

Fixed

  • Pulling images from third party remote private repositories (caprover#370)

[1.2.0] - 2019-02-05

Awesome news for legacy CaptainDuckDuck users! You can now migrate to CapRover! See this: https://caprover.com/docs/cdd-migration.html

Added:

  • Monorepos are now first class citizens, thanks to this suggestion caprover#356 (comment) by @robgraeber
  • Custom One-Click apps. Now everyone can create a one click app as the templates are now easily testable. Use the last option in One-Click apps list (Template) and create a Pull Request here: https://github.com/caprover/one-click-apps
  • Force git build button
  • Hide/Show password clear text password fields
  • Fall back to Dockerfile if captain-definition file does not exist

Fixed:

  • Removal of Ports and Volumes (caprover#355)
  • Not saving SMTP if username is not provided (some password managers autofill password field!)
  • Fixed deploy when some version are manually removed from config-captain.json file.

Donation campaign launched ❤ https://opencollective.com/caprover#backer

[1.1.0] - 2019-01-27

Features:

Fixed:

Added:

Dev:

  • Backend and frontend dependencies updated

[1.0.0] - 2019-01-19

Major Update. Renamed from CaptainDuckDuck to CapRover

Script for upgrading from CaptainDuckDuck to CapRover will be ready in a few weeks, here.

Breaking Changes:

  • schemaVersion in captain-definition file is now upgraded to 2
  • The extra ./src prefix is no longer needed for captain-definition dockerfiles. You need to remove ./src from the first argument in your COPY and ADD statements in your dockerfileLines

Features:

  • One Click Rollback
  • Improved build logs on webview.
  • Improved downtime between deploys
  • Allowing Dockerfile to be referenced in captain-definition (caprover#113)
  • Ability to reference imageName inside captain-definition directly when you want o deploy an already built image from DockerHub.
  • Easy to copy and paste environmental variables UI: (caprover#256)
  • Added a separate one-click repository which can be updated continuously - built based on docker compose (https://github.com/caprover/one-click-apps)
  • Ability to simply copy and paste a Dockerfile and captain-definition files on web dashboard.
  • Improved cluster support by adding ability to turn on/off the registry, have multiple private registries, change default registry.
  • Web dashboard UI improvements.

Dev work:

  • Backend rewrite in TypeScript.
  • Frontend rewrite in TypeScript via React + ant.design
  • CLI rewrite in TypeScript
  • Updated Certbot (Let's Encrypt)

[V0.7.3] - 2018-11-28

  • npm package updates for major security vulnerabilities
  • Updated default tags for MySQL in WordPress
  • Updated links in the front end app
  • Fixed the issue with HTTPS repos caprover#283
  • Fixed port mapping disabled on app push
  • Added VSTS Agent as one-click app

[V0.7.2] - 2018-05-16

Starting V0.7.0, nginx was no longer using the Docker routing mesh, this was done to support showing real IPs behind requests. However, this caused issues on servers that have their ports blocked by firewall, see caprover#237

Although it's not a bug in CaptainDuckDuck, it might cause confusion for new users, hence, a precheck for firewall test is added to the installation phase. If a firewall on important ports is detected, the user will be warned with a proper message and an instruction on how to disable firewall.

[V0.7.1] - 2018-05-14

Added:

  • Ability to override default values. This includes overriding default Captain dashboard subdomain and etc.
  • Allowing precheck for wildcard domain to be skipped if the provider doesn't support wildcard
  • One-click apps can now be deployed with specific tags (versions)
  • The user can now optionally change the instance count of persistent apps.
  • Unused images clean up added to settings

Improved:

  • Back button works as expected in apps settings page
  • Sticky footer for Save and Delete buttons on the app page
  • Move Docker registry settings to Nodes page from the main dashboard page
  • Revealing real IP by using mode=host for nginx

[V0.6.0] - 2018-02-10

Added:

  • Build logs are now available on web dashboard, you can view build logs initiated with Github webhooks as well.
  • Added Redis as a one-click app
  • Added prechecks on OS and Docker version when installing CaptainDuckDuck to ensure maximum compatibility

Fixed:

  • NetData container removal is retrofitted to avoid some Docker deadlocks
  • Flashing issue for logged out state on Dashboard
  • Login issue on small phone screen
  • Fixed issue with very long domain names

Improved:

  • Default client max size for Captain is changed to 500mb
  • Message for self-hosted registry is changed to be more clear so user won't be surprised with an expected error
  • More details on error messages related to custom domains

[0.5.3] - 2018-01-11

Fixed:

Improved:

  • Push error are now throwing proper error rather than confusing 500 error
  • If something fails when app is getting created, the premature entry is now automatically deleted from the app database

[V0.5.1] - 2018-01-09

BREAKING CHANGES::

  • Make sure that your CLI version is at least 1.0.11 -- To check your current version: captainduckduck -V -- To update: sudo npm install -g captainduckduck
  • Breaking change in your captain-definition files: -- if you have python as your template, you should change it to python-django
  • Setting a max on log size files does not apply to existing containers. To use the same log size cap for current services, run:
docker service update  --log-driver json-file --log-opt max-size=512m  captain-nginx 
docker service update  --log-driver json-file --log-opt max-size=512m  captain-captain 
docker service update  --log-driver json-file --log-opt max-size=512m  captain-certbot 
docker service update  --log-driver json-file --log-opt max-size=512m  captain-registry 
docker service update  --log-driver json-file --log-opt max-size=512m  captain-app1   # replace app 1 and app 2 with your app names
docker service update  --log-driver json-file --log-opt max-size=512m  captain-app2    # replace app 1 and app 2 with your app names

Features added:

Improved:

  • Added UDP protocol to Port Forwarding (previously it was only TCP)
  • Container log files are now maxed at 512MB per container by default in order to avoid high unnecessary disk usage. It can be changed by updating service manually, e.g., docker service update srv-captain--app-name --log-driver json-file --log-opt max-size=2048m
  • Captain now runs a docker container prune to clean up stopped containers
  • NetData startup script improved and auto restart is now enabled by default
  • Wrong app name during deploy now returns a more specific message to hint the user instead of plain 500

[0.4.0] - 2017-12-31

New:

  • Added ability to Enorce HTTPS for apps! (caprover#2)
  • Advanced users are now able to customize their nginx configurations (allowing http2, process counts, cache config, custom redirects and etc). caprover#44
  • Added a custom nginx-shared directory for using custom files in nginx container (caprover#71). Using this combined with customized nginx config, you can use custom SSL certificates, custom static assets and etc.
  • Persistent directories (volumes) can now be specified as path on host machine.

Improved:

  • Health-check calls are now more reliable with the newly added timeout.

Fixed:

CLI (1.0.9):

  • Added a --default flag to captainduckduck deploy to avoid re-entering server address and other information.

[0.3.1] - 2017-12-27

Fixed:

Improved:

  • Deploy now reports all kinds of errors. No more ambiguous status 500 error.
  • Changed healthcheck interval to 20sec from 5sec to make the logs less verbose

CLI improvements (1.0.8)

  • Fixed logout causing all other instances to get logged out
  • Improved deploy process by pre-checking captain-definition file.
  • Improved saving app name if it's getting re-deployed.

[0.3.0] - 2017-12-19

Features:

  • :octocat: automatic branch tracking and deployment through Github and Bitbucket 🎊
  • Added ability to expose container ports and map them to host ports
  • Adding ability to change nodeId of apps with persistent data
  • Added ability to set a custom initial password instead of captain42
  • Allow customDomain === rootDomain, see caprover#24
  • Improve build error messages by including last 20 lines of logs that led to build error.
  • Changed max request size to 500mb for apps (temporary solution until fully customizable nginx config is ready)

Bugfixes:

Breaking Change:

  • If you were manually setting port mapping on your containers before this release, make sure to re-map them through Captain interface. Since port mapping is added to the interface, Captain would override the current port mapping that you might have on your containers. If you didn't manually modified your containers --publish-add flag, you don't need to worry about this.

[ v0.2.2] - 2017-12-05

Hotfix:

  • Fix a bug in web UI that was introduced in v0.2.1. Save configuration button was not functioning.

[0.2.1] - 2017-12-04

A major release!! 🎉🎉

New Features:

  • Support for Persistent Data: Previously, Captain only had support for apps with no persistent. The main drawback was that one could not deploy a database using Captain. Now the feature is fully supported.
  • One-click apps: This is perhaps the most interesting feature of new release. Although adding support for persistent data, technically speaking, was enough for the developers to deploy databases. But wouldn't it be nicer if installing MySql, MongoDB and etc becomes as easy as selecting a name from a list? 😉 Done! Not only that, off-the-shelf apps are being slowly added to this list. Installing WordPress, Parse-Server, Tumbor is now as easy as installing apps on your phone!

Improvements:

  • New tabular design for the apps page enables you to have tens of apps and be able to navigate easily from one to another.
  • Deployment from the web interface now accepts tar archive files of the source directory, not necessarity content. See caprover#22

[0.1.2] - 2017-11-17

Bugfixes:

  • Added support for build errors: now build errors get reported as build failure and the image is not created. Previously, build errors were being ignored.

Improvements:

  • Fixed multiple typos
  • Added more details on how apps internally can talk to each other
  • Added functionality to disable "Expose As Web App". Now if you are deploying an app that's only being used as an internal service, you have the option not to expose it via a public URL. This is also useful when in the next release Captain starts supporting databases as they are web-apps at all.
  • Added underlying structure for supporting databases. Since it's not thoroughly tested, the UI is still hidden.