Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 3608 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

It seems like it would be possible, in the interests of maintaining a single code base, to configure EasyDeploy as a single database that could be renamed and the appropriate EasyDeploy layout container filled before deployment.

 

That is, there is a server and client EasyDeploy table, they are different but with no similarly named fields so they could be combined perhaps.  Likewise, with the EasyDeploy layout fields in both could be combined into a single layout.

 

Deployment would start with a database where the helper file is in the appropriate EasyDeploy layout container.  This is the client file. Copy the client file and call it the server file.  The client file is added to  the server file in the appropriate EasyDeploy layout container.  The helper file can be removed from the EasyDeploy layout container in the server file, but likely will not cause any problem other than making the server file larger if it is left in place.

 

Hopefully I have not missed an infinite regress in this merging process…
Any comments are most welcome.

 

Thank you,

This topic is 3608 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.