#1501·revel

Revel 1.0.0 Upgrade Guide and Guidance for Existing apps

Author: eparzialeCreated Jul 13, 2020Updated Apr 13, 2022
Labelspriority-must

Hi Revel Team,

My team has used revel for the past 2 years and been very happy with the framework.

We have a website built on revel that attracts more than 20k users per month, and we're very pleased with performance, maintainability, ease of development, etc.

Last year we adjusted our app to use dep for dependency management, per the recommendations in the following two revel discussions: https://github.com/revel/cmd/issues/177 https://github.com/revel/revel/issues/1326

We were happily chugging along with development until this past weekend when Revel v1.0.0 was released. Our dep build process is no longer compatible with the latest version of revel, we need to adjust our builds to work again. We're seeking guidance in how to proceed (Either to upgrade our build process to use go mods and latest revel version, or how to use legacy revel cmd and framework to maintain existing functionality)

It seems there were some major changes in the 1.0.0 release that fundamentally changed the way that Revel can be included as a dependency, and how the revel cmd is used to start apps.

i.e. the revel run command now requires a -a flag for application path, and a -m flag for run mode.

In the past, we just ran our app by invoking revel run <appname> prod.

We're really excited about the update, and we're glad that Revel officially supports go modules now.

However, for teams with existing prod applications, do you have an official upgrade guide for the new revel version? i.e. a doc with general upgrade steps and common issues? We would love to get our application builds fixed so that we can continue development.

Also, is it possible for teams to use the legacy version of revel and revel cmd in the interim? If so, can you please share steps to do that?

Thanks very much.