Hello,
I would like to update an existing solution in the production environment and would appreciate your guidance on the correct process with nuBuilder.
There are two possible scenarios:
- I update only the design, with no changes to the database.
- I update both the design and the database, while ensuring that the current dataset is preserved.
Could you please advise me on the proper way to implement these updates in nuBuilder?
Thank you in advance for your support.
Best regards,
Yves
Welcome to the nuBuilder Forums!
Join our community by registering and logging in.
As a member, you'll get access to exclusive forums, resources, and content available only to registered users.
Join our community by registering and logging in.
As a member, you'll get access to exclusive forums, resources, and content available only to registered users.
Guidance on Updating a Solution in Production with nuBuilder
-
- Posts: 348
- Joined: Sun Mar 14, 2021 8:48 am
- Location: Geneva
- Has thanked: 94 times
- Been thanked: 12 times
Re: Guidance on Updating a Solution in Production with nuBuilder
Hello,
Does anyone know the best way to update multiple deployed nuBuilder solutions on-premise?
I’m looking for a practical approach or tool to simplify the process across several installations of the same nubuilder solution.
Many thanks in advance for any ideas!
Best regards,
Yves
Does anyone know the best way to update multiple deployed nuBuilder solutions on-premise?
I’m looking for a practical approach or tool to simplify the process across several installations of the same nubuilder solution.
Many thanks in advance for any ideas!
Best regards,
Yves
-
- nuBuilder Team
- Posts: 4581
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 76 times
- Been thanked: 536 times
- Contact:
Re: Guidance on Updating a Solution in Production with nuBuilder
Hi Yves,
As for DB/Table changes, you’ll need to add/modify columns in production the same way you did in your development environment—either manually or by writing a script. If you only need to copy the design (without affecting data), you can use the Cloner tool to transfer forms, objects, etc.
In the future, there will be a more powerful tool to clone or copy specific parts or data, and even to update an installation directly from GitHub.
Until then, please use the Cloner and/or ETL to ease the update process depending on your needs.
Sneak peak of "Application Cloner"
As for DB/Table changes, you’ll need to add/modify columns in production the same way you did in your development environment—either manually or by writing a script. If you only need to copy the design (without affecting data), you can use the Cloner tool to transfer forms, objects, etc.
In the future, there will be a more powerful tool to clone or copy specific parts or data, and even to update an installation directly from GitHub.
Until then, please use the Cloner and/or ETL to ease the update process depending on your needs.
Sneak peak of "Application Cloner"
You do not have the required permissions to view the files attached to this post.