I see tremendous potential in Retool, and I'm currently developing apps and acquiring clients using this platform. As I work on deploying services through Retool, I've encountered some challenges that I'd greatly appreciate your expertise in addressing.
I have created an original app, App A, and have cloned it into Apps B and C, intending to roll them out to different companies. I want to ensure a smooth process for cloning environments, apps, and modules. Ideally, every time I update App A, I’d like to easily update Apps B and C, as well as clone new apps like D and E. I’ve tried using Export to JSON and toolscript ZIP, but due to issues with database links and page linking, I haven’t been able to duplicate them easily. Could you advise on a better approach?
These are my current questions. I look forward to your response. Retool is fantastic!
Hello @takahiro. There are a few different ways in Retool to export and import and create and what works in one direction doesn't always work as well in the other direction, especially for this kind of cross-organization work you're doing.
I would like to understand more about what you're trying now and how it's not working for you, both to better support you and understand how Retool could be better for your use case.
are you losing minutes or hours (or more!) trying to resolve import issues with DBs and page linking?
are you maintaining any kind of library of code and exports you're wanting to re-use? How do you organize it and/or wish it would all work?
Many of the convenience features we have for porting projects around Retool benefit someone working within the same organization for sure. Have you explored using the Retool CLI and/or the Retool REST API directly to setup resources and apps in a more controlled way? While you can definitely run into some of the same issues, you might also find some ways around them.