Deploy Lucee in six steps
- 01
Push your Lucee project to a GitHub repository.
- 02
Sign in to Rimbra, choose New project and import the repository. Rimbra asks GitHub for access to the repositories you pick.
- 03
Rimbra sees an Application.cfc, Application.cfm or index.cfm and runs your .cfm and .cfc files on Lucee 6.2 behind Tomcat. Change the root directory or the commands in Settings if your project needs it.
- 04
Paste your .env into Variables. Every line becomes a variable, available on the next deploy.
- 05
Deploy. The build log streams line by line, and your app goes live at your-project.rimbra.live (or .xyz or .click, your choice) over HTTPS.
- 06
Optional: buy or connect a domain, and Rimbra points it at your app with HTTPS issued automatically.
What your app needs
One rule for servers: listen on the port in the PORT environment variable. Rimbra sets it and routes your address to it.
<cfoutput>
Hello from Lucee #server.lucee.version#
</cfoutput>Lucee on Rimbra
- Pick another Lucee version, such as 7.0, with the runtime version in Build settings.
- Project variables reach your app through server.system.environment, for example server.system.environment.DATABASE_URL.
- The Lucee admin is switched off. Configure datasources and settings in Application.cfc instead.
- ColdBox and other CommandBox packages in box.json are installed with box install during the build.
Read the full list of detected frameworks and default commands in the frameworks docs.
Questions
Can I host a Lucee app for free?
Yes. Rimbra’s Free plan needs no card and includes 4 projects, 1 database, 200 build minutes and 50 GB of bandwidth a month, with a free HTTPS address for each project.
Does every push redeploy my Lucee app?
Yes. Every push to your production branch builds a new version. It goes live only when it answers, so visitors never see a broken release, and you can roll back to an earlier build instantly.
