I would have separate databases for Development & Production (with a
potential QA environment as well). But none of that has been decided by
yet - I'm wanting to see what other people are doing before I decide what I
need (or if I'm overthinking any of this).
Chris
On Tue, Jul 26, 2016 at 10:58 AM, Øyvind Isene <oyvind.isene@xxxxxxxxx>
wrote:
I'm assuming you have separate databases for the different environments.
We release APEX applications to QA and PROD by exporting the applications
to one script per application and then install it from SQL*Plus in the
other environments. You only need the run-time version of APEX in
production to do this.
In 4.2 we had to add an extra block of code to the exported script because
of a bug for this to work. Email me if you run into problems.
2016-07-26 17:25 GMT+02:00 Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
:
For you guys/gals that are Administering APEX environments, how do you
manage Development/Test/Production copies of APEX projects/workspaces etc?
I'm trying to figure out how I want to architect this setup and I'm just
getting started so I'm looking for suggestions.
I "think" I want a separate environment for Developers to "play in" and
an actual production APEX environment to prevent a muddy environment.
I understand (I think) that I could have both in the same environment - I
could have developers "playing" with new projects in the same APEX
environment where there are live applications but that doesn't seem to make
sense logically. (I understand that the nature of APEX can keep them
separate by utilizing specific workspaces but it seems like I could end up
with a lot of projects that aren't doing anything with only a few "live"
applications.
What are you guys doing with APEX environments in relation to
development/production setups?
Thanks,
Chris
--
Øyvind Isene
+47 90864882
