# Make my Application Production Ready

**URL:** <https://www.five.org/t/make-my-application-production-ready/728>\
**Category:** How do I?\
**Created:** [September 30, 2026, 6:50pm UTC](https://www.five.org/t/make-my-application-production-ready/728 "2026-09-30T18:50:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![RMittelman](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/rmittelman/32/447_2.png) [@RMittelman](https://www.five.org/u/RMittelman)\
**Post date:** [September 30, 2026, 6:50pm UTC](https://www.five.org/t/make-my-application-production-ready/728/1 "2026-09-30T18:50:17Z")

</div>

My understanding of the **Production** switch of my application is that if switched on, the application will be guaranteed to stay “live” so it will be available to me and my users, without timing out. I believe this works even if I only have a development version, as when I’m on the basic plan. **Please verify my understanding is correct**.

Currently, I log onto Five as control, then deploy it by clicking the cloud button, then it opens up in another browser tab. For quite some time, it is available to use by opening a tab and navigating to the URL where my **admin** user application is. After some time, neither the development window or the live application window is available. This is usually after 2 hours.

I marked my application as production by flipping the switch. However, if I deploy it, then later (after 2 hours) try to log in to the live application, it gives me an error saying " 503 Service Temporarily Unavailable" or some other message. If I then open the application in development environment and deploy it, it works again for a while.

So the question is: Why doesn’t the application stay alive more than 2 hours if I’ve marked it as “Production”?

thanks…

---

<div class="post-metadata">

**Author:** ![Jo-Anne](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/jo-anne/32/45_2.png) [@Jo-Anne](https://www.five.org/u/Jo-Anne)\
**Post date:** [September 30, 2026, 9:53pm UTC](https://www.five.org/t/make-my-application-production-ready/728/2 "2026-09-30T21:53:19Z")

</div>

Hi Ron,

You need to have it flagged for production on the application record and then use the cluster management page on the instances form to deploy it to production.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/five/original/2X/9/99c4f538431cd3af495fa16d55df3380f5e99d8c.png)

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/five/original/2X/4/424ccab6c89ef5a3f1456333fcc7707c0cae72c4.png)

---

<div class="post-metadata">

**Author:** ![RMittelman](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/rmittelman/32/447_2.png) [@RMittelman](https://www.five.org/u/RMittelman)\
**Post date:** [October 1, 2026, 5:28pm UTC](https://www.five.org/t/make-my-application-production-ready/728/3 "2026-10-01T17:28:42Z")

</div>

I don’t see how to find the Instances form. When I click on the application, none of the menu items say Instances.

---

<div class="post-metadata">

**Author:** ![RMittelman](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/rmittelman/32/447_2.png) [@RMittelman](https://www.five.org/u/RMittelman)\
**Post date:** [October 11, 2026, 5:34pm UTC](https://www.five.org/t/make-my-application-production-ready/728/4 "2026-10-11T17:34:48Z")

</div>

Any idea how I can use this technique if I can’t even see the option in my plan?

---

<div class="post-metadata">

**Author:** ![Jo-Anne](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/jo-anne/32/45_2.png) [@Jo-Anne](https://www.five.org/u/Jo-Anne)\
**Post date:** [October 12, 2026, 1:58am UTC](https://www.five.org/t/make-my-application-production-ready/728/5 "2026-10-12T01:58:57Z")

</div>

Hi Ron,

Click the Manage button on your application record, select Setup in the top menu, followed by Instances in the sub-menu, select your instance record and then follow the previous instructions.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/five/original/2X/5/52dc1ea495f18ed00b1f6c779b076a7a78d931f5.png)

---

<div class="post-metadata">

**Author:** ![RMittelman](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/rmittelman/32/447_2.png) [@RMittelman](https://www.five.org/u/RMittelman)\
**Post date:** [October 12, 2026, 7:03pm UTC](https://www.five.org/t/make-my-application-production-ready/728/6 "2026-10-12T19:03:17Z")

</div>

Thanks Jo.

I was able to perform the steps you outlined.

However, it does not accept my admin credential the way the development version normally does. Can you help with this?

Also, once this is permanently deployed, if I make changes to the application, do I still click the cloud or the run image to deploy the changes, or do I need to do this differently now?

---

<div class="post-metadata">

**Author:** ![Jo-Anne](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/jo-anne/32/45_2.png) [@Jo-Anne](https://www.five.org/u/Jo-Anne)\
**Post date:** [October 12, 2026, 9:16pm UTC](https://www.five.org/t/make-my-application-production-ready/728/7 "2026-10-12T21:16:58Z")

</div>

Hi Ron,

Initial deployment, signin with username: admin, password: admin, you will then be forced to change it.

This is how deployment works for you:

[https://help.five.org/3.0/docs/deployment/how-to-deploy-and-upgrade/team](https://help.five.org/3.0/docs/deployment/how-to-deploy-and-upgrade/team)

---

<div class="post-metadata">

**Author:** ![RMittelman](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/rmittelman/32/447_2.png) [@RMittelman](https://www.five.org/u/RMittelman)\
**Post date:** [October 13, 2026, 12:08am UTC](https://www.five.org/t/make-my-application-production-ready/728/8 "2026-10-13T00:08:16Z")

</div>

Thanks Jo, the article helped, but I am having trouble logging on to production.

I went into cluster management and deployed the application there to DEV. I presume this is the same result as clicking the cloud icon in the title bar, right?

I also deployed the application to production using the lower set of controls in cluster management. This time, the application ran and I can log in using admin, admin. But during initial setup function (which runs at login-time), I got an error saying “InitialSetup failed: Invalid FiscalYearStartMonth: 0”. This indicates a problem in the **Initial Setup** function, reading the **Settings** table. Am I misunderstanding how this works? I expected the database in the Control application would get pushed into the new production instance, the same way as it does when deploying and running the development version. If I deploy normal development then run it, I can login as admin just fine, and it executes the _InitialSetup_\* server function properly.

Can you please explain why I can’t login as admin in production?  
Thanks…

---

<div class="post-metadata">

**Author:** ![Jo-Anne](https://yyz2.discourse-cdn.com/flex030/user_avatar/www.five.org/jo-anne/32/45_2.png) [@Jo-Anne](https://www.five.org/u/Jo-Anne)\
**Post date:** [October 13, 2026, 12:49am UTC](https://www.five.org/t/make-my-application-production-ready/728/9 "2026-10-13T00:49:59Z")

</div>

Hi Ron,

The database in Production will be a clean database with an admin user preconfigured and ready to go. The database will be empty, you will need to populate this, and this is possible by exporting the database from development, and importing it into the production database, you will need to change the sql dump to target the production database, which should be your database name + ‘\_’ + Instance ID all in lower case.

Example : ‘myappdb\_default’ (database name id _myappdb_, and the instance ID is default)

If unsure you can always dump your production empty database and verify its database name in the script to ensure you are using the correct database name.

The reason for this segregation is for quality control, production database should not be corrupted from something that happens in development or testing. The 3 deployment strategies used in five is development, then for your account you have development and production, and in the case of enterprise, there is an additional testing database, and this should be a copy of production to verify all changes work in testing prior to production being upgraded.

If you are have having issues moving the development database to production, let us know, and we can do this heavy lifting for you.

WARNING: after production and development are in sync, never perform the above again, Five will synchronize these environments from this point onwards, if you perform any of these operations after the initial push, you risk loosing your production data as Five does not know what you have done behind the scenes.
